Quoting [1]: > 4.7.x is not supported anymore, so even if this was a bug in 4.7.4, it is not going to be fixed. Does it seem feasible to stabilize the supported 4.8 branch? [1]:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61639
Let's get it keyworded first. :) I also want to let SSP cook a while longer, and we need to figure out the gcj multilib stuff, etc. But we can get it started.
some arches are known to break w/gcc-4.8, but we can move forward with the rest at least
Can we please stabilize 4.8 on amd64 atleast?
(This doesn't look like a tracker.) Just any 4.8.* ?
What about the blockers of "gcc-4.8" bug? I am thinking in bug 513386, but there are some others opened :/
Stable for HPPA.
Let's get this going. What arches are broken?
Would like to see gcc-4.8.? become stable sometime soon, as many programs, including one that I maintain, can only be compiled on >=gcc-4.8.?
(In reply to Ryan Hill from comment #7) > Let's get this going. What arches are broken? MIPS is somewhat broken. I can only test on SGI equipment, but it appears that the __atomic_* builtins added for MIPS in gcc-4.8 have issues w/ the R10000 processor. I have no way to verify if similar problems are present on newer MIPS hardware. I've updated Bug #516548 with additional details. Since MIPS doesn't have a stable tree, this shouldn't be a blocker for other arches, but I'd still like to keep the issue tracked until I poke upstream enough to get someone who understands gcc's internals to take a look and maybe fix it.
From http://www.gossamer-threads.com/lists/gentoo/dev/293411#293411: > One highlight is <https://bugs.gentoo.org/show_bug.cgi?id=513386>. It > occurs only when the user has gcc-4.7 and 4.8 installed simultaneously > and using 4.7 as the active compiler. It's not obvious to me whether we > have to support this (while it's obviously better to support rather than > not, it's webkit-gtk in a specific and rare configuration versus > chromium with security updates in all configurations). Well, that's kind of false. It's by no means webkit-gtk specific - it's only that webkit-gtk is the only at the moment *known* package, that uses API, that had incompatible ABI changes. I don't have info about how widespread the changes were, so it's hard to even guesstimate the number of affected packages (though it's likely low, as c++11 isn't that widespread now), but as long as gcc upstream doesn't declare c++11 ABI stable (has that already happen in the meanwhile ?), such failures will pop up every now and then. The patch from bug 513386 comment 18 has its charm, but might become a maintenance burden.
Needs dev-libs/cloog and dev-libs/isl stable. Any objections or which version should we stabilize? dependency.bad 2 sys-devel/gcc/gcc-4.8.3.ebuild: DEPEND: arm(default/linux/arm/13.0) ['>=dev-libs/cloog-0.18.0', '>=dev-libs/isl-0.11.1'] sys-devel/gcc/gcc-4.8.3.ebuild: RDEPEND: arm(default/linux/arm/13.0) ['>=dev-libs/cloog-0.18.0', '>=dev-libs/isl-0.11.1']
(In reply to Markus Meier from comment #11) > Needs dev-libs/cloog and dev-libs/isl stable. Any objections or which > version should we stabilize? > > dependency.bad 2 > sys-devel/gcc/gcc-4.8.3.ebuild: DEPEND: arm(default/linux/arm/13.0) > ['>=dev-libs/cloog-0.18.0', '>=dev-libs/isl-0.11.1'] > sys-devel/gcc/gcc-4.8.3.ebuild: RDEPEND: arm(default/linux/arm/13.0) > ['>=dev-libs/cloog-0.18.0', '>=dev-libs/isl-0.11.1'] I would aim for the following set for stabilization: =sys-devel/gcc-4.8.3 =dev-libs/cloog-0.18.1 =dev-libs/isl-0.12.2 and for gmp we can stay on 5.1.3-r1 but 6.0.0a should also work. I'v tested on amd64 and mipsel3. Let me test on ppc and ppc64 and report back. I can also test on arm, by if you like Markus, you can try that.
(In reply to Anthony Basile from comment #12) > (In reply to Markus Meier from comment #11) > > Needs dev-libs/cloog and dev-libs/isl stable. Any objections or which > > version should we stabilize? > > > > dependency.bad 2 > > sys-devel/gcc/gcc-4.8.3.ebuild: DEPEND: arm(default/linux/arm/13.0) > > ['>=dev-libs/cloog-0.18.0', '>=dev-libs/isl-0.11.1'] > > sys-devel/gcc/gcc-4.8.3.ebuild: RDEPEND: arm(default/linux/arm/13.0) > > ['>=dev-libs/cloog-0.18.0', '>=dev-libs/isl-0.11.1'] > > I would aim for the following set for stabilization: > > =sys-devel/gcc-4.8.3 > =dev-libs/cloog-0.18.1 > =dev-libs/isl-0.12.2 > > and for gmp we can stay on 5.1.3-r1 but 6.0.0a should also work. I'v tested > on amd64 and mipsel3. Let me test on ppc and ppc64 and report back. I can > also test on arm, by if you like Markus, you can try that. Preliminary tests show this combination works on ppc and ppc64.
arm stable
Keywords for sys-devel/gcc: | | u | | a a a p s | n | | l m r h i m m p s p | u s | r | p d a m p a 6 i p c 3 a x | s l | e | h 6 r 6 p 6 8 p p 6 9 s r 8 | e o | p | a 4 m 4 a 4 k s c 4 0 h c 6 | d t | o 4.8.2 | ~ ~ ~ + ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | o | gentoo [I]4.8.3 | ~ ~ + ~ + ~ ~ ~ ~ ~ ~ ~ ~ ~ | o | gentoo Adding hppa back
Adding hppa back(In reply to Manuel Rüger from comment #15) > Keywords for sys-devel/gcc: > | | u | > | a a a p s | n | > | l m r h i m m p s p | u s | r > | p d a m p a 6 i p c 3 a x | s l | e > | h 6 r 6 p 6 8 p p 6 9 s r 8 | e o | p > | a 4 m 4 a 4 k s c 4 0 h c 6 | d t | o > 4.8.2 | ~ ~ ~ + ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | o | gentoo > [I]4.8.3 | ~ ~ + ~ + ~ ~ ~ ~ ~ ~ ~ ~ ~ | o | gentoo > > > Adding hppa back Pardon, I meant arm64.
stable on ppc and ppc64
gcc stable itself on amd64. For the rest i've got these complaints: dependency.bad 20 dev-libs/cloog/cloog-0.18.1.ebuild: RDEPEND: amd64(default/linux/amd64/13.0) ['>=dev-libs/gmp-5.1.3-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]', '>=dev-libs/isl-0.12.2:0/10[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] dev-libs/cloog/cloog-0.18.1.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop) ['>=dev-libs/gmp-5.1.3-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]', '>=dev-libs/isl-0.12.2:0/10[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] dev-libs/cloog/cloog-0.18.1.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop/gnome) ['>=dev-libs/gmp-5.1.3-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]', '>=dev-libs/isl-0.12.2:0/10[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] dev-libs/cloog/cloog-0.18.1.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop/gnome/systemd) ['>=dev-libs/gmp-5.1.3-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]', '>=dev-libs/isl-0.12.2:0/10[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] ...... oMan scours the neighborhood... dependency.bad 18 dev-libs/isl/isl-0.12.2.ebuild: DEPEND: amd64(default/linux/amd64/13.0) ['>=dev-libs/gmp-5.1.3-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] dev-libs/isl/isl-0.12.2.ebuild: RDEPEND: amd64(default/linux/amd64/13.0) ['>=dev-libs/gmp-5.1.3-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] dev-libs/isl/isl-0.12.2.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop) ['>=dev-libs/gmp-5.1.3-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] dev-libs/isl/isl-0.12.2.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop) ['>=dev-libs/gmp-5.1.3-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] ..........
+ 24 Oct 2014; Michał Górny <mgorny@gentoo.org> + no-emul-linux-x86/package.use.stable.mask, package.use.stable.mask: + Stable-mask abi_x86_32 on dev-libs/{cloog,isl}, bug #516152. Sort lexically. Now amd64 should be happy.
amd64 done now.
x86 stable
sparc stable
arm64 is already stable
cloog and isl were stabilized on alpha as part of bug 545124, which also stabilized gcc-4.8.4. I only see ia64@ still in Cc, which is Cc'd in 545124 as well. Marking as resolved.
ia64 is now stable since glibc has a workaround: http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a494a1557ce5a4d199234307cb8504dce9a04465 http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=157e85ed681e5ff46e7f6b79ccea11865181e7d9 http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a5e16e46a4452f26cbc44643b3025a09c1704303
