Bug 61728 – Call for arch stabilizations of gcc

• Product: Gentoo Linux
• Status: RESOLVED LATER

[Description solar (RETIRED) 2004-08-25 22:27:09 UTC]

I've just pruned a few gcc ebuilds from the tree but we could stand to
remove a few more in order to make general bug maintenance easier.
(current count is 21 down from 30)

We would like to remove gcc-3.3.[23]-r[0-5] and aim to get the 
<=gcc-3.4.0 down to one or two builds per gnu major/minor versions.

x86, amd64, mips, sparc:
Please try to mark gcc-3.3.4-r1

alpha:
If your stuck in gcc-3.2/3.3 series can you please test and mark
gcc-3.3.2-r7 stable.

hppa:
Is your arch stuck at gcc-3.3.2?  If not try to mark something latter
not in the range of gcc-3.3.[23]-r[0-5] as stable.

s390:
The gcc-3.4.x branch should treat you well. (this arch might be lacking
any maintainers and may have to be dropped in the future)

ppc64:
Please test and mark gcc-3.4.1-r2 stable and remove gcc-3.4.1 when your
done.

----
Arches please close any open toolchain bugs which can be resolved by upgrading gcc for your arch. http://tinyurl.com/647of

Current KEYWORDS:

gcc-2.95.3-r8.ebuild:KEYWORDS="x86 ppc sparc alpha"
gcc-3.1.1-r2.ebuild:KEYWORDS="x86 sparc -ppc"
gcc-3.2.3-r4.ebuild:KEYWORDS="x86 ppc sparc mips alpha -hppa ia64 s390"
gcc-3.3.1-r5.ebuild:KEYWORDS="-* ~x86 ~mips ~sparc amd64 ia64"
gcc-3.3.2-r1.ebuild:KEYWORDS="-* ~x86 ~mips ~sparc ~amd64 -hppa ~ia64"
gcc-3.3.2-r2.ebuild:KEYWORDS="-* ~x86 ~mips ~sparc amd64 -hppa alpha ia64"
gcc-3.3.2-r3.ebuild:KEYWORDS="-* ~x86 ~mips ~sparc ~amd64 -hppa ~alpha ~ia64"
gcc-3.3.2-r4.ebuild:KEYWORDS="~x86 mips ~sparc ~amd64 -hppa ~alpha ~ia64"
gcc-3.3.2-r5.ebuild:KEYWORDS="x86 mips ~sparc ~amd64 -hppa alpha -ia64 ppc64"
gcc-3.3.2-r7.ebuild:KEYWORDS="~x86 ~mips ~sparc ~amd64 -hppa ~alpha ~ia64 ~ppc64"
gcc-3.3.2.ebuild:KEYWORDS="-* hppa"
gcc-3.3.3-r3.ebuild:KEYWORDS="~x86 ~sparc ~mips ~alpha arm -hppa ~amd64 -ia64 ~ppc64 s390"
gcc-3.3.3-r5.ebuild:KEYWORDS="-* -hppa arm ~x86 ~sparc ~amd64"
gcc-3.3.3-r6.ebuild:KEYWORDS="x86 amd64 mips"
gcc-3.3.3.ebuild:KEYWORDS="~x86 mips sparc amd64 -hppa ~alpha -ia64 ~ppc64 s390"
gcc-3.3.3_pre20040408-r1.ebuild:KEYWORDS="-* ppc64 ppc"
gcc-3.3.3_pre20040426.ebuild:KEYWORDS="-* ~ppc64 ~ppc"
gcc-3.3.4-r1.ebuild:KEYWORDS="-hppa ~x86 ~amd64 ~mips arm ~sparc"
gcc-3.3.ebuild:KEYWORDS="-* amd64 ~ia64"
gcc-3.4.1-r2.ebuild:KEYWORDS="-* amd64 ~mips ~ppc64 ~x86 -hppa ~ppc"
gcc-3.4.1.ebuild:KEYWORDS="-* ~x86 ~mips -hppa amd64 ppc64"

[Comment 1 Ciaran McCreesh 2004-08-26 08:09:57 UTC]

Not sure that sparc is ready to move 3.3.4 stable yet... Upstream tell us we're supposed to use 3.3.3 for kernel building. OTOH, I haven't personally had any problems with 3.3.4.

[Comment 2 Gustavo Zacarias (RETIRED) 2004-08-26 08:34:24 UTC]

I'm running a few more tests on gcc-3.3.4-r1 this week, so far so good for everything. I wanna do an extra packagecd build before going stable. After that i feel confident about it.
gcc-sparc64-3.3.4 worksforme, but i rather see other sparc devels experiences before saying anything.

[Comment 3 Travis Tilley (RETIRED) 2004-08-26 08:56:50 UTC]

3.3.4-r1 stable on amd64, though it soon-ish wont be the default compiler. :)

[Comment 4 Ferris McCormick (RETIRED) 2004-08-26 10:23:43 UTC]

Note to comment 2: Gustavo, as we discussed on IRC, gcc-3.3.4-r1 is doing fine for me
on both sparc64 and spar32.  For what it's worth, my versions are all built
USE='hardened'.

[Comment 5 Jon Portnoy (RETIRED) 2004-08-26 13:25:16 UTC]

3.3.4-r1 stable on x86

[Comment 6 Joshua Kinard 2004-08-26 15:00:35 UTC]

mips is looking at gcc-3.4.x for stabilization, however our only hold up is gcc-3.4.x does not produce bootable kernels.  Probably just a small kernel patch is all that is needed.

gcc-3.4.x is needed to build functional userland binaries on SGI Origin systems.

[Comment 7 Gustavo Zacarias (RETIRED) 2004-08-31 11:56:13 UTC]

gcc-3.3.4-r1 sparc stable, run for the hills!

[Comment 8 SpanKY 2004-09-07 15:58:41 UTC]

currently, all varieties of 3.3.3, 3.3.4, 3.4.0, and 3.4.1 bomb on ia64 ... either they fail to compile or they dont work properly after building

[Comment 9 solar (RETIRED) 2004-09-07 16:44:56 UTC]

Do we have more than 1 maintaier of ia64?

[Comment 10 solar (RETIRED) 2004-09-08 16:21:00 UTC]

Perhaps 3.4.2 will be better for ia64
Changes from 3.4.1 include.

IA64-specific

    * 16130 ICE on valid code: in bundling, in config/ia64/ia64.c (-mtune=merced)
    * 16142 ICE on valid code: in bundling, in config/ia64/ia64.c (-mtune=itanium)
    * 16278 Gcc failed to build Linux kernel with -mtune=merced
    * 16414 ICE on valid code: typo in comparison of asm_noperands result
    * 16445 ICE on valid code: don't count ignored insns
    * 16490 ICE (segfault) while compiling with -fprofile-use
    * 16683 ia64 does not honor SUBTARGET_EXTRA_SPECS

http://gcc.gnu.org/gcc-3.4/changes.html#3.4.2

[Comment 11 Tom Gall (RETIRED) 2004-10-31 07:56:31 UTC]

gcc-3.4.1-r3.ebuild is stable on ppc64

We have no requirements or dependancies on older version of gcc. 

[Comment 12 Travis Tilley (RETIRED) 2004-11-21 08:59:17 UTC]

3.3.5 shows promise of working on ia64. this will be re-opened when it looks like we can remove previous 3.3 ebuilds and have all archs on 3.3.5 or 3.4.3.