Summary: | [patch] sys-devel/gcc-4.4.1: produces broken binaries with stdcall tailcalls and -foptimize-sibling-calls | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergei Trofimovich (RETIRED) <slyfox> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | galtgendo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://gcc.gnu.org/PR40718 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gcc_4.4.1_destroys_tailcall.tar.gz
pr151030.patch |
Description
Sergei Trofimovich (RETIRED)
2009-08-21 11:39:42 UTC
Created attachment 201854 [details]
gcc_4.4.1_destroys_tailcall.tar.gz
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] pr151030.patch 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.
Thanks!
|