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
