Summary: | [ICE] sys-devel/gcc-4.4.3-r2: verify_ssa failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | antonis <noobscene900> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | holmberm |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
antonis
2010-06-03 10:35:46 UTC
*** Bug 322573 has been marked as a duplicate of this bug. *** *** Bug 322577 has been marked as a duplicate of this bug. *** You need to attach build.log here (or because the file might be too big to attach, upload it somewhere and post link here). That's because it's not clear from Comment #0 what went wrong, the real error is above all that. *** Bug 322603 has been marked as a duplicate of this bug. *** *** Bug 322605 has been marked as a duplicate of this bug. *** *** Bug 322619 has been marked as a duplicate of this bug. *** (In reply to comment #3) > You need to attach build.log here (or because the file might be too big to > attach, upload it somewhere and post link here). That's because it's not clear > from Comment #0 what went wrong, the real error is above all that. > somw additional infos /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/gcc/ira-conflicts.c: In function ‘print_hard_reg_set’: /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/gcc/ira-conflicts.c:667: warning: format not a string literal and no format arguments /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/gcc/ira-build.c: In function ‘create_insn_allocnos’: /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/gcc/ira-build.c:1421: error: missing definition for SSA_NAME: flag_branch_probabilities_157 in statement: flag_branch_probabilities_76 = PHI <flag_branch_probabilities_146(D)(4), flag_branch_probabilities_157(5)> PHI argument flag_branch_probabilities_157 for PHI node flag_branch_probabilities_76 = PHI <flag_branch_probabilities_146(D)(4), flag_branch_probabilities_157(5)> /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/gcc/ira-build.c:1421: internal compiler error: verify_ssa failed Please submit a full bug report, there is my build log http://www.2shared.com/file/_a299rsF/build.html? compress it and attach it here please. Created attachment 234045 [details]
build.log
(In reply to comment #8) > compress it and attach it here please. > any help?it is important.. everybody's bug is important to them (In reply to comment #11) > everybody's bug is important to them > of course but i am a step near to system ctash we talk about gcc....not for an application.. (In reply to comment #12) > (In reply to comment #11) > > everybody's bug is important to them > > > > of course but i am a step near to system ctash > we talk about gcc....not for an application.. > now with the command emerge --ask --update --deep --newuse world gentoo wants to install all the 4,3,5 kde components...why?is thiss another bug? i have 4.4.2 before that i gave eix-sync and eix-remote update if you dont know how deps work, ask in the forums/mailing lists/irc. bugzilla is not a support forum for questions. does it fail in the same spot every time you try to emerge it ? how about if you use MAKEOPTS=-j1 ? the first error you posted does not match the second log (In reply to comment #15) > does it fail in the same spot every time you try to emerge it ? how about if > you use MAKEOPTS=-j1 ? > > the first error you posted does not match the second log > -j1 ? i have quad core processor i could use -j1 and after emerging gcc i can change it again with -j6 -l8 ? (In reply to comment #16) > i have quad core processor i could use -j1 and after emerging gcc i can change > it again with -j6 -l8 ? > on your command line type: MAKEOPTS="-j1" emerge gcc > on your command line type: > MAKEOPTS="-j1" emerge gcc > it seems to be right but at the end i took the messages * The current gcc config appears valid, so it will not be * automatically switched for you. If you would like to * switch to the newly installed gcc version, do the * following: * gcc-config x86_64-pc-linux-gnu-4.4.3 * source /etc/profile * Switching native-compiler to x86_64-pc-linux-gnu-4.3.4 ... >>> Regenerating /etc/ld.so.cache... [ ok ] * If you have issues with packages unable to locate libstdc++.la, * then try running 'fix_libtool_files.sh' on the old gcc versions. >>> Regenerating /etc/ld.so.cache... >>> Recording sys-devel/gcc in "world" favorites file... * Messages for package sys-devel/gcc-4.4.3-r2: * If you have issues with packages unable to locate libstdc++.la, * then try running 'fix_libtool_files.sh' on the old gcc versions. (In reply to comment #18) > > on your command line type: > > MAKEOPTS="-j1" emerge gcc > > > > it seems to be right but at the end i took the messages I get the same error, but MAKEOPTS="-j1" emerge gcc doesn't make a difference for me. Having never used bugzilla, I thougt it best to ask a couple of questions: I'm supposed to continue this bug report, right, not file a new one? And do I post my build log and emerge --info right here? Anything else? (In reply to comment #18) > > on your command line type: > > MAKEOPTS="-j1" emerge gcc > > > > it seems to be right but at the end i took the messages > > * The current gcc config appears valid, so it will not be > * automatically switched for you. If you would like to > * switch to the newly installed gcc version, do the > * following: > > * gcc-config x86_64-pc-linux-gnu-4.4.3 > * source /etc/profile > > * Switching native-compiler to x86_64-pc-linux-gnu-4.3.4 ... > >>> Regenerating /etc/ld.so.cache... [ ok ] > > * If you have issues with packages unable to locate libstdc++.la, > * then try running 'fix_libtool_files.sh' on the old gcc versions. > > >>> Regenerating /etc/ld.so.cache... > > >>> Recording sys-devel/gcc in "world" favorites file... > > * Messages for package sys-devel/gcc-4.4.3-r2: > > * If you have issues with packages unable to locate libstdc++.la, > * then try running 'fix_libtool_files.sh' on the old gcc versions. > Please read http://www.gentoo.org/doc/en/gcc-upgrading.xml, Portage keeps at least one version of each minor release because things sometimes break with new gcc-versions and in those cases you want to be able to switch back to the old version. Because of that and other reasons portage does not try to be smarter then you, and therefore does not switch to the new version but tells you to do it if you want to. The other message about fix_libtool_files does always appear. > Please read http://www.gentoo.org/doc/en/gcc-upgrading.xml,
>
> Portage keeps at least one version of each minor release because things
> sometimes break with new gcc-versions and in those cases you want to be able to
> switch back to the old version. Because of that and other reasons portage does
> not try to be smarter then you, and therefore does not switch to the new
> version but tells you to do it if you want to.
> The other message about fix_libtool_files does always appear.
>
thank you mark it as solved please although i can not understand the reason for not compiling new gcc with my makeopts
*** This bug has been marked as a duplicate of bug 20600 *** |