Bug#632938: fix

2011-07-09 Thread Matthias Berndt
> I would prefer if that would be tractable by an upstream report. I > currently can't see any connection about the upstream commit and the > debian report :-/ The commit adds a regression test which exhibits the exact same behaviour as the test case I've sent you. It compiles fine without -std=c+

Bug#632938: fix

2011-07-09 Thread Matthias Klose
On 07/09/2011 10:05 PM, Matthias Berndt wrote: > I mailed Jason Merrill about this, as he wrote the patch that broke it. He > told me he fixed it in revision 176087 of the 4.6 branch. Could you package > that fix? I would prefer if that would be tractable by an upstream report. I currently can't

Bug#632938: fix

2011-07-09 Thread Matthias Berndt
Hi, I mailed Jason Merrill about this, as he wrote the patch that broke it. He told me he fixed it in revision 176087 of the 4.6 branch. Could you package that fix? Cheers Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Con

Bug#632938: g++-4.6: fix

2011-07-09 Thread Matthias Berndt
Package: g++-4.6 Version: 4.6.1-2 Followup-For: Bug #632938 Hi, I wrote Jason Merrill about this, and he told me that it was fixed in the 4.6 branch in revision 176087. Cheers Matthias -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Arc

[Bug fortran/49690] [4.6/4.7 regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1019

2011-07-09 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49690 --- Comment #5 from Tobias Burnus 2011-07-09 18:11:42 UTC --- Draft patch. As both integer arguments and function-pointer arguments are pointers, using a generic "void *" (BT_VOID) is the simplest. A more cumbersome alternative would be to split

gcc-defaults_1.107_amd64.changes ACCEPTED into unstable

2011-07-09 Thread Debian FTP Masters
Accepted: cpp_4.6.1-2_amd64.deb to main/g/gcc-defaults/cpp_4.6.1-2_amd64.deb g++-multilib_4.6.1-2_amd64.deb to main/g/gcc-defaults/g++-multilib_4.6.1-2_amd64.deb g++_4.6.1-2_amd64.deb to main/g/gcc-defaults/g++_4.6.1-2_amd64.deb gcc-defaults_1.107.dsc to main/g/gcc-defaults/gcc-defaults_

Processing of gcc-defaults_1.107_amd64.changes

2011-07-09 Thread Debian FTP Masters
gcc-defaults_1.107_amd64.changes uploaded successfully to localhost along with the files: gcc-defaults_1.107.dsc gcc-defaults_1.107.tar.gz libgcj-common_4.4.6-2_all.deb cpp_4.6.1-2_amd64.deb gcc_4.6.1-2_amd64.deb gcc-multilib_4.6.1-2_amd64.deb gdc_4.4.6-2_amd64.deb g++_4.6.1-2_amd64

[Bug fortran/49690] [4.6/4.7 regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1019

2011-07-09 Thread doko at ubuntu dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49690 Matthias Klose changed: What|Removed |Added CC||debian-gcc at lists dot

Bug#633359: marked as done (gcc-defaults: some dissonance)

2011-07-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Jul 2011 17:47:20 + with message-id and subject line Bug#633359: fixed in gcc-defaults 1.107 has caused the Debian Bug report #633359, regarding gcc-defaults: some dissonance to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#633365: libppl-swi: Getting rid of unneeded *.la / emptying dependency_libs

2011-07-09 Thread Neil Williams
Package: libppl-swi Version: 0.11.2-3 Severity: normal User: codeh...@debian.org Usertags: la-file-removal To finish an old release goal from Squeeze, to comply with Policy 10.2 and to ease the introduction of MultiArch, I'm filing bugs against packages which contain .la files which can be either

Bug#633359: gcc-defaults: some dissonance

2011-07-09 Thread Thorsten Glaser
Source: gcc-defaults Version: 1.106 Three things I noticed in 1.105 which were not yet fixed in 1.106 – the second one must be addressed in another upload before I can build this on m68k; the third one is an FTBFS fix I could work around (but since we require an upload due to the second issue anyw

gcc-defaults_1.106_amd64.changes ACCEPTED into unstable

2011-07-09 Thread Debian FTP Masters
Accepted: cpp_4.6.1-1_amd64.deb to main/g/gcc-defaults/cpp_4.6.1-1_amd64.deb g++-multilib_4.6.1-1_amd64.deb to main/g/gcc-defaults/g++-multilib_4.6.1-1_amd64.deb g++_4.6.1-1_amd64.deb to main/g/gcc-defaults/g++_4.6.1-1_amd64.deb gcc-defaults_1.106.dsc to main/g/gcc-defaults/gcc-defaults_

Processing of gcc-defaults_1.106_amd64.changes

2011-07-09 Thread Debian FTP Masters
gcc-defaults_1.106_amd64.changes uploaded successfully to localhost along with the files: gcc-defaults_1.106.dsc gcc-defaults_1.106.tar.gz libgcj-common_4.4.6-1_all.deb cpp_4.6.1-1_amd64.deb gcc_4.6.1-1_amd64.deb gcc-multilib_4.6.1-1_amd64.deb gdc_4.4.6-1_amd64.deb g++_4.6.1-1_amd64

Bug#630853: marked as done (cpp: multi-arch: foreign or multi-arch: allowed?)

2011-07-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Jul 2011 15:33:29 + with message-id and subject line Bug#630853: fixed in gcc-defaults 1.106 has caused the Debian Bug report #630853, regarding cpp: multi-arch: foreign or multi-arch: allowed? to be marked as done. This means that you claim that the problem has bee

Bug#568299: marked as done (Don't remove alternative on package upgrade)

2011-07-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Jul 2011 15:33:29 + with message-id and subject line Bug#568299: fixed in gcc-defaults 1.106 has caused the Debian Bug report #568299, regarding Don't remove alternative on package upgrade to be marked as done. This means that you claim that the problem has been dea

Bug#633073: marked as done (gcc-defaults: Please set default to 4.6 for sh4)

2011-07-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Jul 2011 15:33:30 + with message-id and subject line Bug#633073: fixed in gcc-defaults 1.106 has caused the Debian Bug report #633073, regarding gcc-defaults: Please set default to 4.6 for sh4 to be marked as done. This means that you claim that the problem has been

Bug#633352: gcc-4.4: function name incorrect in -Wstrict-overflow diagnostic

2011-07-09 Thread James Youngman
Package: gcc-4.4 Version: 4.4.5-8 Severity: minor The shell script below reproduces this problem. Notice that the function name is incorrect (on my system the name shown is "T.4"). I get this result when I run the script: ~$ sh t98.sh t98.c: In function ‘T.4’: t98.c:5: warning: assuming signed

Bug#467341: marked as done (rrdtool built with -O2 segfaults on arm)

2011-07-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Jul 2011 17:00:55 +0200 with message-id <4e186d27.8040...@debian.org> and subject line closing obsolete report with no feedback has caused the Debian Bug report #467341, regarding rrdtool built with -O2 segfaults on arm to be marked as done. This means that you claim tha

Processed: forwarded gcc report

2011-07-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 631204 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49690 Bug #631204 [gfortran] gfortran 4.6 ICE ; gfc_typenode_for_spec, at fortran/trans-types.c:1019 Set Bug forwarded-to-address to 'http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49690'

Processed: Re: Bug#567533: -O interferes with debugging on amd64 (oprofile doesn't like -fomit-frame-pointers)

2011-07-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 567533 oprofile Bug #567533 [g++] -O interferes with debugging on amd64 (oprofile doesn't like -fomit-frame-pointers) Bug reassigned from package 'g++' to 'oprofile'. > thanks Stopping processing here. Please contact me if you need assi

Bug#567533: -O interferes with debugging on amd64 (oprofile doesn't like -fomit-frame-pointers)

2011-07-09 Thread Matthias Klose
reassign 567533 oprofile thanks On 01/29/2010 06:04 PM, Timothy Brownawell wrote: > Package: g++ > > -O is turning on -fomit-frame-pointers on amd64, which interferes with > debugging > performance issues (because it prevents oprofile from generating callgraph > information). "man g++" says >

Processed: raise severity of ftbfs with -Werror (please apologize for false positives, just close the report in this case)

2011-07-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 616296 serious Bug #616296 [src:btrfs-tools] btrfs-tools: will FTBFS with gcc-4.6 Bug #625312 [src:btrfs-tools] btrfs-tools: ftbfs with gcc-4.6 -Werror Severity set to 'serious' from 'important' Severity set to 'serious' from 'important'

Processed: raise severity of ftbfs's with gcc-4.5 to serious

2011-07-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 565026 serious Bug #565026 [libfreebob] libfreebob: ftbfs with gcc-4.5 Severity set to 'serious' from 'important' > severity 564845 serious Bug #564845 [acl2] acl2: ftbfs with gcc-4.5 Severity set to 'serious' from 'important' > severit