Priority: P3
Component: c++
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: d...@boost-consulting.com
This program should compile, but instead it blows the instantiation stack.
template
constexpr int factorial(int n)
{
return n ? n * factorial(n - 1) : 1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51452
--- Comment #5 from d...@boost-consulting.com 2011-12-07 18:41:12 UTC ---
(In reply to comment #1)
> I think this is by design, see the thread beginning with c++std-lib-30698
>
> I've been surprised by that reasoning several tim
Component: libstdc++
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: d...@boost-consulting.com
The traits that detect nothrow constructibility are buggy because they are
influenced by whether the object has a nothrow dtor; destruction is invoked at
the end of evaluation of the
Component: c++
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: d...@boost-consulting.com
I just noticed that GCC can be overly-helpful ;-) when formatting a
static assertion message:
static_assert('X' != '\130',"'X' has the wrong va
y: P3
Component: other
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: d...@boost-consulting.com
The following command (which works for me with macports gmp,mpfr,and mpc, and a
hand-built-from-source libiconv in /usr/local/lib) fails without
--disable-libitm.
export LDFLA
...@gcc.gnu.org
ReportedBy: d...@boost-consulting.com
Compile the following:
template
struct A
{
A() { float r = g(0); }
};
struct f_t
{
float operator() (float x) const { return 1; }
};
f_t f;
A x;
Now replace "g(0)" with "(*g)(0)". It compiles!
It'
