Summary: | [toolchain-overlay] Add Intel Atom optimizations support to GCC-4.4 ebuilds | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexey Charkov <alchark> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED UPSTREAM | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://gcc.gnu.org/ml/gcc-patches/2009-01/msg00923.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Patch containing the changes to trunk
Stripped-down contents of the commit 145624 |
Description
Alexey Charkov
2009-03-15 21:19:23 UTC
Created attachment 185113 [details, diff]
Patch containing the changes to trunk
Here is a patch obtained by `svn diff` of the forementioned branch to a relevant trunk revision. I tested it with gcc-4.4 snapshots dated 20090227 and 20090313, and it applies, builds and runs well, as far as I can tell.
you should be able to put the patch into the /etc/portage/patches/sys-devel/gcc-4.4.0_alphaXXXXXXXX dir and it'll automatically get applied maybe extend the autopatch support so it also looks at ${PV:0:5} so you dont have to keep updating the dir ... (In reply to comment #2) > you should be able to put the patch into the > /etc/portage/patches/sys-devel/gcc-4.4.0_alphaXXXXXXXX dir and it'll > automatically get applied > > maybe extend the autopatch support so it also looks at ${PV:0:5} so you dont > have to keep updating the dir ... > Well, I personally do quite well by just renaming a trivially modified ebuild that adds 'epatch ${FILESDIR}/gcc-atom.diff' when new snapshots are published. The point I was filing this bug for is that probably this feature is interesting enough so that other people could directly benefit from it. This would be way more accessible if overlay ebuilds were providing the patch (probably with USE=atom or similar), as few people seem to know about the very existence of this code. Of course, the 'get it and apply yourself' strategy works, but... :) i know, i was just highlighting a simpler way for you to apply the patch rather than having to touch any ebuild This seems to be in trunk since r145624, see here: http://gcc.gnu.org/viewcvs?view=rev&revision=145624 Created attachment 188459 [details, diff]
Stripped-down contents of the commit 145624
This could be useful for those who wish to use Atom optimizations with pre-4.5 versions of GCC. Changelogs and non-critical diff information are stripped off to minimize size.
I've merged gcc-4.4.1_pre9999 from gcc-porting overlay but its not in there zlib says "no valid march" on emerge -e world could somebody please make an ebuild of the gcc atom branch http://gcc.gnu.org/viewcvs/branches/ix86/atom/ (In reply to comment #7) > I've merged gcc-4.4.1_pre9999 from gcc-porting overlay but its not in there > zlib says "no valid march" on emerge -e world > > could somebody please make an ebuild of the gcc atom branch > http://gcc.gnu.org/viewcvs/branches/ix86/atom/ > The one you used is from the 4.4* branch, which does not include Atom support. Just use 4.5* snapshots and you are done. Alternatively, you can try to apply the patch that I posted to a 4.4* build (for example, consider what vapier suggests in comment #2). I would rather not try to maintain a 65KiB patch against a live svn build. :P You should be able to use the existing ebuild to checkout the atom branch just by changing the ESVN_REPO_URI. (In reply to comment #9) > I would rather not try to maintain a 65KiB patch against a live svn build. :P > > You should be able to use the existing ebuild to checkout the atom branch just > by changing the ESVN_REPO_URI. > There is no need, in fact. After the merge to mainline they seem to update trunk frequently with the changes made in atom branch, so I do not see any benefit of using atom branch over mainline 4.5. This made sense before 4.4 was branched out, though. I am now using gcc 4.5 ebuilds from toolchain overlay with a bit fixes to let it merge properly look here http://bugs.gentoo.org/show_bug.cgi?id=270558 now i will test to remerge my whole system and adding kernel patch to activate inline pipelining. |