http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48446
Summary: internal compiler error: in gimplify_var_or_parm_decl,
at gimplify.c:1946
Product: gcc
Version: 4.4.5
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: [email protected]
ReportedBy: [email protected]
Created attachment 23878
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23878
The failing source file
I compile the attached file using this command:
$ g++ -std=gnu++0x -Wall -Wextra -c test.cpp
with this version of GCC:
$ gcc --version
gcc (Gentoo 4.4.5 p1.2, pie-0.4.5) 4.4.5
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
on Gentoo x86-64 and x86 (both produce identical error messages). I get this
output:
test.cpp: In member function ‘void Sender::flush()’:
test.cpp:168: internal compiler error: in gimplify_var_or_parm_decl, at
gimplify.c:1946
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.gentoo.org/> for instructions.
I also have access to an OpenSUSE x86-64 environment reading out this version:
$ gcc --version
gcc (SUSE Linux) 4.5.0 20100604 [gcc-4_5-branch revision 160292]
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This gives the following output:
test.cpp: In member function ‘void Sender::flush()’:
test.cpp:175:71: internal compiler error: in gimplify_var_or_parm_decl, at
gimplify.c:1816
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.opensuse.org/> for instructions.
(yes, the source line number of the error in test.cpp is different for this GCC
version even though the sources are identical).
Finally, a friend using Arch Linux x86-64 tested the same code on GCC 4.6 and
also reproduced the bug, though I don't have the line numbers from that test.
I can attach preprocessed source if you want, though the source doesn't use
anything but standard headers and the problem seems quite easily reproducible
as I already described.
