Processing of gcc-4.6_4.6.2-5_i386.changes
gcc-4.6_4.6.2-5_i386.changes uploaded successfully to localhost along with the files: gcc-4.6_4.6.2-5.dsc gcc-4.6_4.6.2-5.diff.gz gcc-4.6-source_4.6.2-5_all.deb libstdc++6-4.6-doc_4.6.2-5_all.deb gcc-4.6-locales_4.6.2-5_all.deb gcc-4.6-base_4.6.2-5_i386.deb libgcc1_4.6.2-5_i386.deb libgcc1-dbg_4.6.2-5_i386.deb lib64gcc1_4.6.2-5_i386.deb lib64gcc1-dbg_4.6.2-5_i386.deb libquadmath0_4.6.2-5_i386.deb libquadmath0-dbg_4.6.2-5_i386.deb lib64quadmath0_4.6.2-5_i386.deb lib64quadmath0-dbg_4.6.2-5_i386.deb libgomp1_4.6.2-5_i386.deb libgomp1-dbg_4.6.2-5_i386.deb lib64gomp1_4.6.2-5_i386.deb lib64gomp1-dbg_4.6.2-5_i386.deb cpp-4.6_4.6.2-5_i386.deb fixincludes_4.6.2-5_i386.deb libmudflap0-4.6-dev_4.6.2-5_i386.deb libmudflap0_4.6.2-5_i386.deb libmudflap0-dbg_4.6.2-5_i386.deb lib64mudflap0_4.6.2-5_i386.deb lib64mudflap0-dbg_4.6.2-5_i386.deb gobjc++-4.6-multilib_4.6.2-5_i386.deb gobjc++-4.6_4.6.2-5_i386.deb gobjc-4.6-multilib_4.6.2-5_i386.deb gobjc-4.6_4.6.2-5_i386.deb libobjc3_4.6.2-5_i386.deb libobjc3-dbg_4.6.2-5_i386.deb lib64objc3_4.6.2-5_i386.deb lib64objc3-dbg_4.6.2-5_i386.deb libgo0_4.6.2-5_i386.deb libgo0-dbg_4.6.2-5_i386.deb lib64go0_4.6.2-5_i386.deb lib64go0-dbg_4.6.2-5_i386.deb gccgo-4.6_4.6.2-5_i386.deb gccgo-4.6-multilib_4.6.2-5_i386.deb g++-4.6-multilib_4.6.2-5_i386.deb g++-4.6_4.6.2-5_i386.deb libstdc++6_4.6.2-5_i386.deb lib64stdc++6_4.6.2-5_i386.deb lib64stdc++6-4.6-dbg_4.6.2-5_i386.deb libstdc++6-4.6-dev_4.6.2-5_i386.deb libstdc++6-4.6-pic_4.6.2-5_i386.deb libstdc++6-4.6-dbg_4.6.2-5_i386.deb libgfortran3_4.6.2-5_i386.deb libgfortran3-dbg_4.6.2-5_i386.deb lib64gfortran3_4.6.2-5_i386.deb lib64gfortran3-dbg_4.6.2-5_i386.deb gfortran-4.6-multilib_4.6.2-5_i386.deb gfortran-4.6_4.6.2-5_i386.deb gcc-4.6-multilib_4.6.2-5_i386.deb gcc-4.6-plugin-dev_4.6.2-5_i386.deb gcc-4.6_4.6.2-5_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1rsqvq-0001cz...@franck.debian.org
gcc-4.6_4.6.2-5_i386.changes ACCEPTED into unstable
Accepted: cpp-4.6_4.6.2-5_i386.deb to main/g/gcc-4.6/cpp-4.6_4.6.2-5_i386.deb fixincludes_4.6.2-5_i386.deb to main/g/gcc-4.6/fixincludes_4.6.2-5_i386.deb g++-4.6-multilib_4.6.2-5_i386.deb to main/g/gcc-4.6/g++-4.6-multilib_4.6.2-5_i386.deb g++-4.6_4.6.2-5_i386.deb to main/g/gcc-4.6/g++-4.6_4.6.2-5_i386.deb gcc-4.6-base_4.6.2-5_i386.deb to main/g/gcc-4.6/gcc-4.6-base_4.6.2-5_i386.deb gcc-4.6-locales_4.6.2-5_all.deb to main/g/gcc-4.6/gcc-4.6-locales_4.6.2-5_all.deb gcc-4.6-multilib_4.6.2-5_i386.deb to main/g/gcc-4.6/gcc-4.6-multilib_4.6.2-5_i386.deb gcc-4.6-plugin-dev_4.6.2-5_i386.deb to main/g/gcc-4.6/gcc-4.6-plugin-dev_4.6.2-5_i386.deb gcc-4.6-source_4.6.2-5_all.deb to main/g/gcc-4.6/gcc-4.6-source_4.6.2-5_all.deb gcc-4.6_4.6.2-5.diff.gz to main/g/gcc-4.6/gcc-4.6_4.6.2-5.diff.gz gcc-4.6_4.6.2-5.dsc to main/g/gcc-4.6/gcc-4.6_4.6.2-5.dsc gcc-4.6_4.6.2-5_i386.deb to main/g/gcc-4.6/gcc-4.6_4.6.2-5_i386.deb gccgo-4.6-multilib_4.6.2-5_i386.deb to main/g/gcc-4.6/gccgo-4.6-multilib_4.6.2-5_i386.deb gccgo-4.6_4.6.2-5_i386.deb to main/g/gcc-4.6/gccgo-4.6_4.6.2-5_i386.deb gfortran-4.6-multilib_4.6.2-5_i386.deb to main/g/gcc-4.6/gfortran-4.6-multilib_4.6.2-5_i386.deb gfortran-4.6_4.6.2-5_i386.deb to main/g/gcc-4.6/gfortran-4.6_4.6.2-5_i386.deb gobjc++-4.6-multilib_4.6.2-5_i386.deb to main/g/gcc-4.6/gobjc++-4.6-multilib_4.6.2-5_i386.deb gobjc++-4.6_4.6.2-5_i386.deb to main/g/gcc-4.6/gobjc++-4.6_4.6.2-5_i386.deb gobjc-4.6-multilib_4.6.2-5_i386.deb to main/g/gcc-4.6/gobjc-4.6-multilib_4.6.2-5_i386.deb gobjc-4.6_4.6.2-5_i386.deb to main/g/gcc-4.6/gobjc-4.6_4.6.2-5_i386.deb lib64gcc1-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64gcc1-dbg_4.6.2-5_i386.deb lib64gcc1_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64gcc1_4.6.2-5_i386.deb lib64gfortran3-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64gfortran3-dbg_4.6.2-5_i386.deb lib64gfortran3_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64gfortran3_4.6.2-5_i386.deb lib64go0-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64go0-dbg_4.6.2-5_i386.deb lib64go0_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64go0_4.6.2-5_i386.deb lib64gomp1-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64gomp1-dbg_4.6.2-5_i386.deb lib64gomp1_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64gomp1_4.6.2-5_i386.deb lib64mudflap0-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64mudflap0-dbg_4.6.2-5_i386.deb lib64mudflap0_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64mudflap0_4.6.2-5_i386.deb lib64objc3-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64objc3-dbg_4.6.2-5_i386.deb lib64objc3_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64objc3_4.6.2-5_i386.deb lib64quadmath0-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64quadmath0-dbg_4.6.2-5_i386.deb lib64quadmath0_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64quadmath0_4.6.2-5_i386.deb lib64stdc++6-4.6-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64stdc++6-4.6-dbg_4.6.2-5_i386.deb lib64stdc++6_4.6.2-5_i386.deb to main/g/gcc-4.6/lib64stdc++6_4.6.2-5_i386.deb libgcc1-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/libgcc1-dbg_4.6.2-5_i386.deb libgcc1_4.6.2-5_i386.deb to main/g/gcc-4.6/libgcc1_4.6.2-5_i386.deb libgfortran3-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/libgfortran3-dbg_4.6.2-5_i386.deb libgfortran3_4.6.2-5_i386.deb to main/g/gcc-4.6/libgfortran3_4.6.2-5_i386.deb libgo0-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/libgo0-dbg_4.6.2-5_i386.deb libgo0_4.6.2-5_i386.deb to main/g/gcc-4.6/libgo0_4.6.2-5_i386.deb libgomp1-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/libgomp1-dbg_4.6.2-5_i386.deb libgomp1_4.6.2-5_i386.deb to main/g/gcc-4.6/libgomp1_4.6.2-5_i386.deb libmudflap0-4.6-dev_4.6.2-5_i386.deb to main/g/gcc-4.6/libmudflap0-4.6-dev_4.6.2-5_i386.deb libmudflap0-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/libmudflap0-dbg_4.6.2-5_i386.deb libmudflap0_4.6.2-5_i386.deb to main/g/gcc-4.6/libmudflap0_4.6.2-5_i386.deb libobjc3-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/libobjc3-dbg_4.6.2-5_i386.deb libobjc3_4.6.2-5_i386.deb to main/g/gcc-4.6/libobjc3_4.6.2-5_i386.deb libquadmath0-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/libquadmath0-dbg_4.6.2-5_i386.deb libquadmath0_4.6.2-5_i386.deb to main/g/gcc-4.6/libquadmath0_4.6.2-5_i386.deb libstdc++6-4.6-dbg_4.6.2-5_i386.deb to main/g/gcc-4.6/libstdc++6-4.6-dbg_4.6.2-5_i386.deb libstdc++6-4.6-dev_4.6.2-5_i386.deb to main/g/gcc-4.6/libstdc++6-4.6-dev_4.6.2-5_i386.deb libstdc++6-4.6-doc_4.6.2-5_all.deb to main/g/gcc-4.6/libstdc++6-4.6-doc_4.6.2-5_all.deb libstdc++6-4.6-pic_4.6.2-5_i386.deb to main/g/gcc-4.6/libstdc++6-4.6-pic_4.6.2-5_i386.deb libstdc++6_4.6.2-5_i386.deb to main/g/gcc-4.6/libstdc++6_4.6.2-5_i386.deb Override entries for your package: cpp-4.6_4.6.2-5_i386.deb - optional interpreters fixincludes_4.6.2-5_i386.deb - optional devel g++-4.6-multilib_4.6.2-5_i386.deb - optional devel g++-4.6_4.6.2-5_i386.deb - optional devel gcc-4.6-base_4.6.2-5_i386.deb - required libs gcc-4.6-locales_4.6.2-5_all.deb - optional devel gcc-4.6-multilib_4.6.2-5_i386.deb - optional devel gcc-4.6-plugin-dev_4.6.2-5_i386.deb -
Re: Increasing minimum 'i386' processor
On Tue, Nov 22, 2011 at 04:47:20PM +, Ian Jackson wrote: Ben Hutchings writes (Increasing minimum 'i386' processor): The 486-class processors that would no longer be supported are: 1. All x86 processors with names including '486' I'm still running the machine below, and it would be irritating to have to replace it. vendor_id : CentaurHauls model name: VIA Samuel 2 I don't see any 486 in this name. Bastian -- There's a way out of any cage. -- Captain Christopher Pike, The Menagerie (The Cage), stardate unknown. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2022172828.ga31...@wavehammer.waldi.eu.org
Re: Increasing minimum 'i386' processor
Ben Hutchings writes (Increasing minimum 'i386' processor): The 486-class processors that would no longer be supported are: 1. All x86 processors with names including '486' I'm still running the machine below, and it would be irritating to have to replace it. Perhaps a better approach would be to suggest that people with shiny new hardware should be running amd64 kernels with i386 userland, or even amd64 (with multiarch i386 for proprietary crap that isn't available for amd64) ? Ian. processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 7 model name : VIA Samuel 2 stepping: 3 cpu MHz : 533.401 cache size : 64 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de tsc msr cx8 mtrr pge mmx 3dnow bogomips: 1066.80 clflush size: 32 cache_alignment : 32 address sizes : 32 bits physical, 32 bits virtual power management: -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20171.53784.119523.574...@chiark.greenend.org.uk
Re: Increasing minimum 'i386' processor
OoO Lors de la soirée naissante du mardi 22 novembre 2011, vers 18:28, Bastian Blank wa...@debian.org disait : The 486-class processors that would no longer be supported are: 1. All x86 processors with names including '486' I'm still running the machine below, and it would be irritating to have to replace it. vendor_id: CentaurHauls model name : VIA Samuel 2 I don't see any 486 in this name. This processor does not run with a 686 kernel and needs a 486 kernel. If I remember correctly, it is because the lack of CMOV instruction. Therefore, no problem with 586. -- Vincent Bernat ☯ http://vincent.bernat.im Indent to show the logical structure of a program. - The Elements of Programming Style (Kernighan Plauger) pgpCLXEAQqCXs.pgp Description: PGP signature
Bug#649615: gdc-4.4: Annoying multilib warning
Package: gdc-4.4 Version: 1.063-4.4.6-7 Severity: important Any invocation of the gdc-4.4 compiler prints a multilib-relted warning: cc1d: warning: command line option -imultilib is valid for C/C++/Fortran/ObjC/ObjC++ but not for D This is rather annoying and hides useful compiler warnings. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdc-4.4 depends on: ii g++-4.44.4.6-11 ii gcc-4.4-base 4.4.6-11 ii libc6 2.13-21 ii libgcc11:4.6.2-4 ii libgmp10 2:5.0.2+dfsg-2 ii libmpfr4 3.1.0-3 ii libphobos-4.4-dev 1.063-4.4.6-7 ii libstdc++6 4.6.2-4 gdc-4.4 recommends no packages. gdc-4.4 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2022182705.6609.38932.reportbug@wallach.localdomain
Re: Increasing minimum 'i386' processor
On Tue, Nov 22, 2011 at 04:47:20PM +, Ian Jackson wrote: Ben Hutchings writes (Increasing minimum 'i386' processor): The 486-class processors that would no longer be supported are: 1. All x86 processors with names including '486' I'm still running the machine below, and it would be irritating to have to replace it. As Bastian says, this does not look like a 486. The flags include tsc msr cx8. Perhaps a better approach would be to suggest that people with shiny new hardware should be running amd64 kernels with i386 userland, or even amd64 (with multiarch i386 for proprietary crap that isn't available for amd64) ? [...] I believe Debian should now treat amd64 as the default architecture for PCs. The i386 installer does provide it as an option in expert mode (though it's not on CD 1) but I'm not sure we're quite at the point where it should be automatically selected. In any case this is irrelevant to the question of optimising userland. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2022183646.gr3...@decadent.org.uk
Bug#649615: gdc-4.4: Annoying multilib warning
On 11/22/2011 07:27 PM, Peter De Wachter wrote: Package: gdc-4.4 Version: 1.063-4.4.6-7 Severity: important Any invocation of the gdc-4.4 compiler prints a multilib-relted warning: cc1d: warning: command line option -imultilib is valid for C/C++/Fortran/ObjC/ObjC++ but not for D This is rather annoying and hides useful compiler warnings. If you are annoyed, please send a fix. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecc2d4a.5030...@debian.org
Re: Increasing minimum 'i386' processor
On 11/19/2011 11:42 PM, Ben Hutchings wrote: The i386 architecture was the first in Linux and in Debian, but we have long since dropped support for the original i386-compatible processors and now require a minimum of a 486-class processor. I think it is time to increase the minimum requirement to 586-class, if not for wheezy then immediately after. note that squeeze is built this way, and single packages like openjdk only build for 586. (Later it should be increased further, and eventually i386 should be reduced to a partial architecture that may be installed on amd64 systems.) This would allow the use of optimisations and new instructions throughout userland that improve performance for the vast majority of users. could you give numbers what kind of improvements you would expect? The biggest burden for i386 is the register pressure, which you won't fix with targeting a newer processor. The better approach would be a new port, the x32 architecture; I don't know if anybody did look into building a distribution for this architecture yet. The next thing could be to default to sse2 math instead of x87 (didn't look if this is already the default for x32). Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecc33cd.7040...@debian.org
Re: Increasing minimum 'i386' processor
On 11/20/2011 01:08 AM, Guillem Jover wrote: Hi! On Sat, 2011-11-19 at 22:42:11 +, Ben Hutchings wrote: The i386 architecture was the first in Linux and in Debian, but we have long since dropped support for the original i386-compatible processors and now require a minimum of a 486-class processor. I think it is time to increase the minimum requirement to 586-class, if not for wheezy then immediately after. (Later it should be increased further, and eventually i386 should be reduced to a partial architecture that may be installed on amd64 systems.) This would allow the use of optimisations and new instructions throughout userland that improve performance for the vast majority of users. It seems gcc has been targetting i586 instruction set by default since gcc 4.4.0-1~exp1, although the triplet was not changed to match. On the discussion regarding multiarch tuples I proposed we should switch the triplet back to i386-linux-gnu to avoid this kind of confusion, fix the internal inconsistency and the one with other architectures (which do not track the base instruction set in the triplet) and so that we can use them directly as the multiarch tuples. For more details please see: http://lists.debian.org/debian-dpkg/2011/02/msg00061.html http://lists.debian.org/debian-dpkg/2011/02/msg00039.html No, that's wrong. i386-linux-gnu has a different ABI for at least some libraries (libstdc++) than i486-linux-gnu. Unfortunately the proposal to use ix86-linux-gnu for the i386 multiarch triplet didn't find a consensus. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecc34e9.6090...@debian.org
