Proposed resolution:

This wording is relative to N4600.

1. Adjust [numeric.ops.gcd] p3 as indicated:

   template<class M, class N>
     constexpr common_type_t<M, N> gcd(M m, N n);
   

   […]

   -3- Remarks: If either M or N is not an integer type, or if either is (possibly cv-qualified) bool, the program is ill-formed.

2. Adjust [numeric.ops.lcm] p3 as indicated:

   template<class M, class N>
     constexpr common_type_t<M, N> lcm(M m, N n);
   

   […]

   -3- Remarks: If either M or N is not an integer type, or if either is (possibly cv-qualified) bool, the program is ill-formed.

[ 2016-08, Chicago ]

Monday PM: Moved to Tentatively Ready

[ 2016-08-01, Walter Brown suggests wording ]

A corresponding issue has been added addressing the WP, see LWG 2759.

Addresses: fund.ts.v2

According to N4562, gcd and lcm support bool as the operand type. The wording doesn't appear to cover the behavior for that case, since bool does not have a zero value and gcd / lcm are not normally mathematically defined over {false, true}.

Presumably gcd and lcm shouldn't accept arguments of type bool.