Summary: | emacs, gcc 3.3 w/ hammer patch, and -O3: the story of an unhappy family | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Travis Tilley (RETIRED) <lv> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | drobbins, gcc-porting |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Travis Tilley (RETIRED)
![]() I forgot I had even filed this bug about two and a half weeks ago, but after weeks of attacking gcc 3.3 bugs and issues I have come to the conclusion that most of them are caused by the hammer update patch. I re-merged gcc without this evil patch and then attempted to compile emacs with -O3.
Suprise suprise, the end result was a perfect errorless merge and as such this bug should be closed. This isnt an emacs related bug in any way shape or form. This is a hammer update bug. The fix is simple and solves most of the issues i've seen that arent true legitimate C99 changes or other such issues that arent really bugs.
ayanami gcc # diff ./gcc-3.3.ebuild ./gcc-3.3-r1.ebuild
191c191
< epatch ${DISTDIR}/${P}-athlon-hammer-branch-20030515.patch.bz2
---
> use athlon64 && epatch ${DISTDIR}/${P}-athlon-hammer-branch-20030515.patch.bz2
ok thats an interesting find. i've been suspect of the hammer patch for another (not yet in portage) package called LUSH (the lisp universal shell), which also works without the hammer patch applied. not emacs related please use a newer version of gcc |