https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112498
--- Comment #2 from Ingo Josopait ---
Yes, you are right. It is confusing, though. Maybe the warning message should
mention that it is actually invalid code. It looked more like a suggestion to
me.
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: josopait at goopax dot com
Target Milestone: ---
If I am not mistaken, this should succeed:
#include
int main()
{
static_assert(std::is_convertible::value); // ok
static_assert(std
Assignee: unassigned at gcc dot gnu.org
Reporter: josopait at goopax dot com
CC: ian at gcc dot gnu.org
Target Milestone: ---
I installed gcc on gentoo linux:
EXTRA_ECONF="--enable-libstdcxx-backtrace=yes" emerge gcc
and compiled the following program:
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: josopait at goopax dot com
Target Milestone: ---
Does gcc produce wrong code here? The program below is part of a bitwise
conversion mechanism, similar to std::bit_cast, but for more general types.
The output should
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65786
--- Comment #3 from Ingo Josopait ---
Yes, you are right. Thanks.
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: josopait at goopax dot com
In the program below, the assignment of the return value is messed up. While
the C++-14 style of fully automatic type deduction works fine, the mymax11
function call
