After upgrading GCC I tried to build my C++ project and noticed crashing produced binaries. After debugging this issue I located the place gcc
emits invalid code. g++-4.3.4 works correctly. I'm not sure what caused regression: vanilla GCC, or gentoo patches, so I post bug here.
Steps to Reproduce:
1. Unpack .tat.gz from attach
the result is SIGSEGV
Created attachment 201854 [details]
Archive contains source sample, makefile and disassembler dumps for gcc-4.3.4 and gcc-4.4.1 of suspicious file.
Please note I build i386 binaries(-m32) on amd64
Upstream bug entry: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40718
assigning to maintainers.
Created attachment 202579 [details, diff]
Upstream committed fix http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=151030 to gcc-4_4 branch.
I got it from svn and stripped ChangeLog entries (they don't apply cleanly).
Fix works for me.
Should I attach gcc .ebuild or something other to make patch hit portage?
nah, we'll get it next time a new patchset is rolled.
Assuming fixed in 4.4.2
> Assuming fixed in 4.4.2
Sorry for a delayed response. I confirm - fixed.