Re: GCC-4.5 as the default for (at least some) architectures
On 04/26/2011 09:28 PM, Kurt Roeckx wrote: On Tue, Apr 26, 2011 at 08:51:04PM +0200, Aurelien Jarno wrote: On Tue, Apr 26, 2011 at 05:03:01PM +0200, Matthias Klose wrote: I'll make GCC 4.6 the default after the release of GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and powerpc. If you do the switch, please also add mips and mipsel, that would avoid you to have to complain in two weeks that these architectures have not yet been switched. Is there a reason not to switch the remaining (release) arches (ia64, kfreebsd-*, sparc, s390)? Maybe hurd-i386 too? I don't know, and I will not invest time to check. If you did check, and if you are confident to fix issues on these architectures, then please tell here. At least for other ports this seems to be possible (s390: Bastian Blank, kfreebsd-*: Aurelian, Petr). I assume you want to release with at least 4.6 on all arches as the default, so I see no point in waiting with switching if there are no known issues. I will not work on toolchain issues specific to these architectures for the wheezy release, so if nobody steps forward, then at least I will not change the default for these architectures. Matthias -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4db73b0c.4000...@debian.org
Re: GCC-4.5 as the default for (at least some) architectures
Kurt Roeckx, le Tue 26 Apr 2011 21:28:57 +0200, a écrit : > Is there a reason not to switch the remaining (release) arches > (ia64, kfreebsd-*, sparc, s390)? Maybe hurd-i386 too? There's no real reason to defer hurd-i386, as it's basically like i386, and the key packages (glibc/hurd/gnumach) already use a fixed version and can be handled independently. Samuel -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110426204147.gs4...@const.famille.thibault.fr
Re: GCC-4.5 as the default for (at least some) architectures
On Tue, Apr 26, 2011 at 08:51:04PM +0200, Aurelien Jarno wrote: > On Tue, Apr 26, 2011 at 05:03:01PM +0200, Matthias Klose wrote: > > I'll make GCC 4.6 the > > default after the release of GCC 4.5.3, expected later this week, at > > least on amd64, armel, i386 and powerpc. > > If you do the switch, please also add mips and mipsel, that would avoid > you to have to complain in two weeks that these architectures have not > yet been switched. Is there a reason not to switch the remaining (release) arches (ia64, kfreebsd-*, sparc, s390)? Maybe hurd-i386 too? I assume you want to release with at least 4.6 on all arches as the default, so I see no point in waiting with switching if there are no known issues. Kurt -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110426192857.ga10...@roeckx.be
Re: GCC-4.5 as the default for (at least some) architectures
Matthias Klose dixit: > At this point, pretty well after the GCC 4.6.0 release, I would like to avoid > switching more architectures to 4.5, but rather get rid of GCC 4.5 to reduce > maintenance efforts on the debian-gcc side, even before the multiarch changes Porters side, too. I’m okay with keeping gcc-4.4 for a while (kernel?) and switching to gcc-4.6 directly for m68k. I know I’ll probably have to invest some work into the latter, but considering the kernel problem is almost solved, chances are good. (I do want to bring out a new base emulator image first, though, but then…) bye, //mirabilos -- 13:47⎜ if i were omnipotent, i would divide by zero all day long ;) (thinking about http://lobacevski.tumblr.com/post/3260866481 by waga) -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1104261853560.28...@herc.mirbsd.org
Re: GCC-4.5 as the default for (at least some) architectures
On Tue, Apr 26, 2011 at 05:03:01PM +0200, Matthias Klose wrote: > On 04/17/2011 09:33 PM, Adam D. Barratt wrote: > >On Wed, 2011-03-02 at 02:34 +0100, Matthias Klose wrote: > >>I'll make gcc-4.5 the default for (at least some) architectures within the > >>next > >>two weeks before more transitions start. GCC-4.5 is already used as the > >>default > >>compiler for almost any other distribution, so there shouldn't be many > >>surprises > >>on at least the common architectures. About 50% of the build failures > >>exposed > >>by GCC-4.5 are fixed [1]. I didn't see issues on amd64 and i386, armel > >>(although optimized for a different processor) and powerpc (some object > >>files > >>linked into shared libs had to be built as pic). > > > >It looks like kfreebsd-* also made the switch and there's been a request > >to switch for mips and mipsel. > > > >Looking through the bug list for src:gcc-4.5, none of the open issues > >seem to be specific to the remaining release architectures which haven't > >switched yet - i.e. ia64, s390 and sparc. Are you aware of any issues > >which would preclude switching the default on those architectures? Has > >there been any discussion with the port maintainers regarding switching? > > At this point, pretty well after the GCC 4.6.0 release, I would like > to avoid switching more architectures to 4.5, but rather get rid of > GCC 4.5 to reduce maintenance efforts on the debian-gcc side, even > before the multiarch changes go into unstable. I'll make GCC 4.6 the > default after the release of GCC 4.5.3, expected later this week, at > least on amd64, armel, i386 and powerpc. GCC 4.6 apparently will be If you do the switch, please also add mips and mipsel, that would avoid you to have to complain in two weeks that these architectures have not yet been switched. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110426185104.gb29...@hall.aurel32.net
Re: GCC-4.5 as the default for (at least some) architectures
On Tue, Apr 26, 2011 at 5:31 PM, Konstantinos Margaritis wrote: > On 26 April 2011 18:03, Matthias Klose wrote: >> I'll make GCC 4.6 the default after the release of >> GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and >> powerpc. > > Could you include armhf in the list as well? I am also getting an ICE with g++ 4.5 on mips too on one of my C++ package: https://buildd.debian.org/status/package.php?p=vxl but since there is no log I cannot confirm this is the same ICE as on i386/armel thanks, -- Mathieu -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimr8sshy4vvasvzoxk4gyj1pb9...@mail.gmail.com
Re: GCC-4.5 as the default for (at least some) architectures
On 04/26/2011 05:31 PM, Konstantinos Margaritis wrote: On 26 April 2011 18:03, Matthias Klose wrote: I'll make GCC 4.6 the default after the release of GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and powerpc. Could you include armhf in the list as well? yes, forgot about that. with GCC 4.6, armhf is built again from the 4.6 fsf branch, and lets us drop the GCC 4.5 Linaro variant. Matthias -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4db6eb11.2080...@debian.org
Re: GCC-4.5 as the default for (at least some) architectures
On 26 April 2011 18:03, Matthias Klose wrote: > I'll make GCC 4.6 the default after the release of > GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and > powerpc. Could you include armhf in the list as well? Thanks Konstantinos -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTimddKkTaiy1fyka6zMOj0o1YzBS=a...@mail.gmail.com
Re: GCC-4.5 as the default for (at least some) architectures
On 04/17/2011 09:33 PM, Adam D. Barratt wrote: On Wed, 2011-03-02 at 02:34 +0100, Matthias Klose wrote: I'll make gcc-4.5 the default for (at least some) architectures within the next two weeks before more transitions start. GCC-4.5 is already used as the default compiler for almost any other distribution, so there shouldn't be many surprises on at least the common architectures. About 50% of the build failures exposed by GCC-4.5 are fixed [1]. I didn't see issues on amd64 and i386, armel (although optimized for a different processor) and powerpc (some object files linked into shared libs had to be built as pic). It looks like kfreebsd-* also made the switch and there's been a request to switch for mips and mipsel. Looking through the bug list for src:gcc-4.5, none of the open issues seem to be specific to the remaining release architectures which haven't switched yet - i.e. ia64, s390 and sparc. Are you aware of any issues which would preclude switching the default on those architectures? Has there been any discussion with the port maintainers regarding switching? At this point, pretty well after the GCC 4.6.0 release, I would like to avoid switching more architectures to 4.5, but rather get rid of GCC 4.5 to reduce maintenance efforts on the debian-gcc side, even before the multiarch changes go into unstable. I'll make GCC 4.6 the default after the release of GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and powerpc. GCC 4.6 apparently will be used for the next Fedora and OpenSuse releases, and a test rebuild of Ubuntu natty doesn't look too bad (mostly adding new easily fixable C++ build failures). A test rebuild of the unstable archive is still outstanding, but these build failures will have to be fixed anyway. From my point of view it's important to expose GCC 4.6 early in the release cycle to fix issues like #617628 (which are issues in the packages itself) now. With GCC 4.6 comes one soname change, bumping the libobjc version from 2 to 3, which is not easily detachable from the GCC version change. However this change only affects GNUstep, which can be dealt with NMU's, or migration to a new GNUstep version. It's unlikely that GCC 4.5 will be released with wheezy, as the Debian Ada and D maintainers are already working on GCC 4.6 support. Matthias -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4db6dea5.5010...@debian.org
Re: GCC-4.5 as the default for (at least some) architectures
On Wed, 2011-03-02 at 02:34 +0100, Matthias Klose wrote: > I'll make gcc-4.5 the default for (at least some) architectures within the > next > two weeks before more transitions start. GCC-4.5 is already used as the > default > compiler for almost any other distribution, so there shouldn't be many > surprises > on at least the common architectures. About 50% of the build failures exposed > by GCC-4.5 are fixed [1]. I didn't see issues on amd64 and i386, armel > (although optimized for a different processor) and powerpc (some object files > linked into shared libs had to be built as pic). It looks like kfreebsd-* also made the switch and there's been a request to switch for mips and mipsel. Looking through the bug list for src:gcc-4.5, none of the open issues seem to be specific to the remaining release architectures which haven't switched yet - i.e. ia64, s390 and sparc. Are you aware of any issues which would preclude switching the default on those architectures? Has there been any discussion with the port maintainers regarding switching? Regards, Adam -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303068791.3489.499.ca...@hathi.jungle.funky-badger.org
Re: GCC-4.5 as the default for (at least some) architectures
> On Tue, Mar 1, 2011 at 8:34 PM, Matthias Klose wrote: > > I'll make gcc-4.5 the default for (at least some) architectures within th= > e next > > two weeks before more transitions start. =A0GCC-4.5 is already used as th= > e default > > compiler for almost any other distribution, so there shouldn't be many su= > rprises > > on at least the common architectures. =A0About 50% of the build failures = > exposed > > by GCC-4.5 are fixed [1]. =A0I didn't see issues on amd64 and i386, armel > > (although optimized for a different processor) and powerpc (some object f= > iles > > linked into shared libs had to be built as pic). > > > > As the maintainer file for the ports in GCC is a bit outdated, I'd like t= > o ask > > which architectures should do the switch together with the four architect= > ures > > mentioned above, and which not, and which ones should be better delayed, = > or dropped. > > Dave, > > What's your opinion on switching to GCC 4.5 for HPPA? Do it! I have built glibc with it and all my recent kernel have been with 4.5. I'm not aware of any new issues with 4.5 and a number of things are fixed. For kernel builds, the following patch must be included: 2010-12-18 John David Anglin PR target/46915 * config/pa/pa.c (branch_to_delay_slot_p): Use next_active_insn instead of next_real_insn. Search forward checking for both ASM_INPUT and ASM_OPERANDS asms until exit condition is found. (branch_needs_nop_p): Likewise. (use_skip_p): New function. (output_cbranch): Use use_skip_p. (output_bb, output_bvb): Likewise. There are some other bug fixes in 4.6 that might need back porting. We also need this binutils change: 2011-02-18 John David Anglin PR ld/12376 emulparams/hppalinux.sh (DATA_ADDR): Define. (SHLIB_DATA_ADDR): Likewise. This should eliminate cache issues arising from non equivalent aliasing. Hopefully, the above will help resolve some of the build and kernel issues that blocked squeeze. I personally don't know what the critical blockers were. If they involve GCC or binutils, I'm willing to take a look. I'm sure a number of things have been magically fixed by updates to the middle-end. The biggest issue is the callee copies args on HPPA and this differs from most other targets. Regards, Dave -- J. David Anglin dave.ang...@nrc-cnrc.gc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110307013751.74c8c5...@hiauly1.hia.nrc.ca
Re: GCC-4.5 as the default for (at least some) architectures
On Wed, 02 Mar 2011 02:34:01 +0100 Matthias Klose wrote: > I'll make gcc-4.5 the default for (at least some) architectures > within the next two weeks before more transitions start. GCC-4.5 is > already used as the default compiler for almost any other > distribution, so there shouldn't be many surprises on at least the > common architectures. About 50% of the build failures exposed by > GCC-4.5 are fixed [1]. I didn't see issues on amd64 and i386, armel > (although optimized for a different processor) and powerpc (some > object files linked into shared libs had to be built as pic). GCC4.5 still segfault when i try to compile, all previous version work fine (without any kind of warning), maybe my GCC4.5 isn't the right one (4.5.2-4), but i'm not so sure can be deployed as "default" (compiling on i386) -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110307015837.a9d87800.syt...@sythos.net
Re: GCC-4.5 as the default for (at least some) architectures
On Tue, Mar 1, 2011 at 8:34 PM, Matthias Klose wrote: > I'll make gcc-4.5 the default for (at least some) architectures within the > next > two weeks before more transitions start. GCC-4.5 is already used as the > default > compiler for almost any other distribution, so there shouldn't be many > surprises > on at least the common architectures. About 50% of the build failures exposed > by GCC-4.5 are fixed [1]. I didn't see issues on amd64 and i386, armel > (although optimized for a different processor) and powerpc (some object files > linked into shared libs had to be built as pic). > > As the maintainer file for the ports in GCC is a bit outdated, I'd like to ask > which architectures should do the switch together with the four architectures > mentioned above, and which not, and which ones should be better delayed, or > dropped. Dave, What's your opinion on switching to GCC 4.5 for HPPA? Cheers, Carlos. -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinznkgbhpaqc7hd6peyppr8da+1iponh1im6...@mail.gmail.com
Re: GCC-4.5 as the default for (at least some) architectures
On 02.03.2011 17:54, Martin Guy wrote: > On 2 March 2011 02:34, Matthias Klose wrote: >> armel (although optimized for a different processor) > > Hi > For which processor (/architecture) is it optimized, and do you mean > optimized-for, or only-runs-on? > I ask in case this would mean dumping all the armv4t systems that are > using Debian armel. I didn't propose changing the minimum required processor for armel. I said that 4.5 looks ok, although I can only say that for another processor default (armv7-a). Matthias -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d6e787c.9090...@debian.org
Re: GCC-4.5 as the default for (at least some) architectures
On 2 March 2011 02:34, Matthias Klose wrote: > armel (although optimized for a different processor) Hi For which processor (/architecture) is it optimized, and do you mean optimized-for, or only-runs-on? I ask in case this would mean dumping all the armv4t systems that are using Debian armel. M -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiktn0zoa_hzgciwhkzbup7_ji6pbeji+p4c7...@mail.gmail.com
Re: GCC-4.5 as the default for (at least some) architectures
On 02.03.2011 07:36, Konstantinos Margaritis wrote: > On 2 March 2011 03:34, Matthias Klose wrote: > >> I'll make gcc-4.5 the default for (at least some) architectures within the >> next >> two weeks before more transitions start. GCC-4.5 is already used as the >> default >> compiler for almost any other distribution, so there shouldn't be many >> surprises >> on at least the common architectures. About 50% of the build failures >> exposed >> by GCC-4.5 are fixed [1]. I didn't see issues on amd64 and i386, armel >> (although optimized for a different processor) and powerpc (some object >> files >> linked into shared libs had to be built as pic). >> >> As the maintainer file for the ports in GCC is a bit outdated, I'd like to >> ask >> which architectures should do the switch together with the four >> architectures >> mentioned above, and which not, and which ones should be better delayed, or >> dropped. >> > Could you add armhf to the list? keeping armhf to build from the linaro branch? Matthias -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d6e5293.8060...@debian.org
Re: GCC-4.5 as the default for (at least some) architectures
On 2 March 2011 03:34, Matthias Klose wrote: > I'll make gcc-4.5 the default for (at least some) architectures within the > next > two weeks before more transitions start. GCC-4.5 is already used as the > default > compiler for almost any other distribution, so there shouldn't be many > surprises > on at least the common architectures. About 50% of the build failures > exposed > by GCC-4.5 are fixed [1]. I didn't see issues on amd64 and i386, armel > (although optimized for a different processor) and powerpc (some object > files > linked into shared libs had to be built as pic). > > As the maintainer file for the ports in GCC is a bit outdated, I'd like to > ask > which architectures should do the switch together with the four > architectures > mentioned above, and which not, and which ones should be better delayed, or > dropped. > > Could you add armhf to the list? Konstantinos