From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new version of gcc
Date: Tue, 3 Nov 2009 12:27:23 +0100 [thread overview]
Message-ID: <200911031227.24041.wonko@wonkology.org> (raw)
In-Reply-To: <87d440sed9.fsf@newsguy.com>
Harry Putnam writes:
> I noticed I've been masking gcc beyond version 4.3.2-r3, and have
> forgotten why I had it masked.
>
> I'm updating world right now, and wondered if I were to move up to
> most recent gcc (4.4.2), which would be a 5 version jump, what I could
> expect in the way of problems.
>
> Would I need to re-emerge just about everything?
The upgrade guide says yes, but this seems to be true only when the ABI
changes, which happend for the last time when gcc 4.3 was introduced. I
would not do the emerge -e thing.
Unless this new gcc has some cool features you want to use. Then you would
change your CFLAGS, and either let the changes gradually drop in, or re-
emerge everything to make them happen at once.
What do you people think, are there fancy new and yet save CFLAGS that
would improve our Gentoos? http://gcc.gnu.org/gcc-4.4/changes.html lists
some improvements, to me they don't look too spectacular. Well, maybe
apart from the graphite stuff
(http://gcc.gnu.org/wiki/Graphite/PolyhedralInterface) which has been
mentioned here. I don't know how much of an improvement this may be.
Wonko
next prev parent reply other threads:[~2009-11-03 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 23:20 [gentoo-user] new version of gcc Harry Putnam
2009-11-02 23:48 ` Volker Armin Hemmann
2009-11-02 23:56 ` [gentoo-user] " Harry Putnam
2009-11-03 0:17 ` Dale
2009-11-03 0:51 ` walt
2009-11-03 6:45 ` [gentoo-user] " Graham Murray
2009-11-03 11:27 ` Alex Schuster [this message]
2009-11-03 20:03 ` [gentoo-user] " Harry Putnam
2009-11-03 20:15 ` Neil Bothwick
2009-11-03 21:49 ` Harry Putnam
2009-11-03 23:42 ` Marcus Wanner
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=200911031227.24041.wonko@wonkology.org \
--to=wonko@wonkology.org \
--cc=gentoo-user@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