From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ICC Profile
Date: Thu, 17 Jul 2008 21:56:03 -0700 [thread overview]
Message-ID: <20080718045603.GA7446@comet> (raw)
In-Reply-To: <20080717142344.CHK42419@mirapoint.uc.edu>
[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]
On 14:23 Thu 17 Jul , Adam Stylinski wrote:
> The intel C Compiler (icc) has an ebuild for gentoo and the wiki has a
> script to integrate it with portage. This script works will in terms
> of building binaries, however when mixed with gcc environments there
> are massive linking issues. I propose that an ICC profile is made
> which contains specific versions and default flags for people who want
> to build a mixed icc-gcc environment. ICC is much faster than GCC and
> although not free, offers a free non-commercial license. I would be
> very interested in this project and more than willing to help to the
> best of my abilities. I've already been trying to maintain a mixed
> environment with some luck, while there have been a lot of problems
> using dynamically linked libraries (ld from intel and ld from gcc
> don't always get along), my system is substatially faster. The kernel
> obviously will still be built under gcc as well as bash (unless intel
> helps submit patches to make the code work with their compiler).
> There are many tools icc has to offer for vectorization. If these
> were streamlined into Gentoo with a fetch restriction for ICC, a
> bootsrapping boot disk could be made and result in a very fast
> distribution. -- gentoo-dev@lists.gentoo.org mailing list
Adam,
I've already got a mixed system that works reasonably well. I use
/etc/portage/env/ to control which packages build with icc and
icc-specific CFLAGS by having /etc/portage/env/$CATEGORY/$PN be symlinks
to /etc/portage/env/env.icc with these contents:
echo " * Exporting: Intel compilers in $EBUILD_PHASE"
CC="icc"
CXX="icc"
FC="ifort"
F77="ifort"
FFLAGS="-openmp -parallel -ipo -xO -O2 -no-prec-div"
FCFLAGS="${FFLAGS}"
export CC CXX FC F77 FFLAGS FCFLAGS
Is what you're proposing here an improvement over something like the
above setup? If so, could you explain how?
--
Thanks,
Donnie
Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-18 4:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 18:23 [gentoo-dev] ICC Profile Adam Stylinski
2008-07-18 2:34 ` Luca Barbato
2008-07-18 3:15 ` Robert Bridge
2008-07-18 13:55 ` Doug Goldstein
2008-07-18 4:56 ` Donnie Berkholz [this message]
2008-07-18 9:55 ` [gentoo-dev] " Nikos Chantziaras
2008-07-18 14:16 ` [gentoo-dev] " Sébastien Fabbro
2008-07-18 15:29 ` Robert Bridge
2008-07-19 11:01 ` Michael Hammer
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 3:24 Adam Stylinski
2008-07-18 5:02 ` Donnie Berkholz
2008-07-18 14:16 ` Sébastien Fabbro
2008-07-18 3:25 Adam Stylinski
2008-07-18 3:35 Adam Stylinski
2008-07-18 13:24 Adam Stylinski
2008-07-18 17:28 Adam Stylinski
2008-07-19 15:16 Adam Stylinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080718045603.GA7446@comet \
--to=dberkholz@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox