Bug#516727: marked as done (gcc segfaults on simple wrong c++ code)

g - GNU Ada compiler version library libgnatvsn4.3-dev - GNU Ada compiler version library - development files Closes: 516727 Changes: gnat-4.3 (4.3.3-2) unstable; urgency=low . merge from gcc-4.3 (4.3.3-5): . [Matthias Klose] * Update to SVN 20090301 from the gcc-4_3-branch. - Fix PR c/

gnat-4.3_4.3.3-2_amd64.changes ACCEPTED

Accepted: gnat-4.3-base_4.3.3-2_amd64.deb to pool/main/g/gnat-4.3/gnat-4.3-base_4.3.3-2_amd64.deb gnat-4.3_4.3.3-2.diff.gz to pool/main/g/gnat-4.3/gnat-4.3_4.3.3-2.diff.gz gnat-4.3_4.3.3-2.dsc to pool/main/g/gnat-4.3/gnat-4.3_4.3.3-2.dsc gnat-4.3_4.3.3-2_amd64.deb to pool/main/g/gnat-4.3/g

Bug#515841: marked as done (gnat-4.3: fails to run Ada Conformity Assessment Test Suite)

Your message dated Mon, 02 Mar 2009 00:26:30 +0100 with message-id <87ljrox1sp@ludovic-brenta.org> and subject line gnat-4.3: fails to run Ada Conformity Assessment Test Suite has caused the Debian Bug report #515841, regarding gnat-4.3: fails to run Ada Conformity Assessment Test Suite to be

Processing of gnat-4.3_4.3.3-2_amd64.changes

gnat-4.3_4.3.3-2_amd64.changes uploaded successfully to localhost along with the files: gnat-4.3_4.3.3-2.dsc gnat-4.3_4.3.3-2.diff.gz gnat-4.3-base_4.3.3-2_amd64.deb libgnat-4.3_4.3.3-2_amd64.deb libgnatvsn4.3-dev_4.3.3-2_amd64.deb libgnatvsn4.3_4.3.3-2_amd64.deb libgnatprj4.3-dev_4.3

Bug#516727: marked as done (gcc segfaults on simple wrong c++ code)

patches/ada-acats.dpatch: attempt to fix ACATS tests (not entirely successful yet). * New upstream version. Fixes: #514565. . [Matthias Klose] * Update to SVN 20090301 from the gcc-4_3-branch. - Fix PR c/35446, PR c++/38950, PR fortran/38852, PR fortran/39006, PR c++/39

gcc-4.3_4.3.3-5_multi.changes ACCEPTED

Accepted: cpp-4.3_4.3.3-5_i386.deb to pool/main/g/gcc-4.3/cpp-4.3_4.3.3-5_i386.deb cpp-4.3_4.3.3-5_powerpc.deb to pool/main/g/gcc-4.3/cpp-4.3_4.3.3-5_powerpc.deb fixincludes_4.3.3-5_i386.deb to pool/main/g/gcc-4.3/fixincludes_4.3.3-5_i386.deb fixincludes_4.3.3-5_powerpc.deb to pool/main/g/

Processing of gcc-4.3_4.3.3-5_multi.changes

gcc-4.3_4.3.3-5_multi.changes uploaded successfully to localhost along with the files: lib64gomp1_4.3.3-5_powerpc.deb libmudflap0-dbg_4.3.3-5_powerpc.deb g++-4.3-multilib_4.3.3-5_powerpc.deb lib64gfortran3-dbg_4.3.3-5_i386.deb libmudflap0_4.3.3-5_i386.deb lib64gcc1-dbg_4.3.3-5_powerpc.d

Bug#517659: ppl - FTBFS: Missuse of buildd resources

Bastian Blank wrote: Package: ppl Version: 0.10-4 Severity: serious The build of ppl needs 7 CPU-hours on a fast machine, including a long documentation run. This is probably due to `make check', which is something you can disable if you are prepared to accept the risk of miscompilation of the

lenny mips64el gcc-4.3-multilib is missing libstdc++.so symlink to be able to compile C++

Hi, After installing gcc-4.3-multilib, lib64* and libn32* I had to add: gcc51:/usr/lib/gcc/mipsel-linux-gnu/4.3.2/n32# ln -s /usr/lib32/libstdc++.so.6 libstdc++.so gcc51:/usr/lib/gcc/mipsel-linux-gnu/4.3.2/n32# cd ../64 gcc51:/usr/lib/gcc/mipsel-linux-gnu/4.3.2/64# ln -s /usr/lib64/libstdc++.so

Bug#517653: gcc-4.3: "warning: comparison with string literal results in unspecified behavior" when comparing two different literals

On Sun, Mar 01, 2009 at 04:04:07PM +0200, Kalle Olavi Niemitalo wrote: > Falk Hueffner writes: > > > I can't imagine any sensible code whatsoever that triggers this > > warning but does not have logical errors. Can you show how it is used? > > Here are all the source lines from net-snmp 5.2.3-7e

Bug#517653: gcc-4.3: "warning: comparison with string literal results in unspecified behavior" when comparing two different literals

Falk Hueffner writes: > I can't imagine any sensible code whatsoever that triggers this > warning but does not have logical errors. Can you show how it is used? Here are all the source lines from net-snmp 5.2.3-7etch4 that trigger this warning. snmplib/data_list.c:108 netsnmp_assert("li

Bug#517653: gcc-4.3: "warning: comparison with string literal results in unspecified behavior" when comparing two different literals

On Sun, Mar 01, 2009 at 10:40:40AM +0200, Kalle Olavi Niemitalo wrote: > Compiling this with gcc-4.3 -Wall -c > > int > main (void) > { > return "hello" == "there"; > } > > results in a warning: > > hoh.c: In function ???main???: > hoh.c:4: warning: comparison with string literal results in un

Bug#517653: gcc-4.3: "warning: comparison with string literal results in unspecified behavior" when comparing two different literals

Bastian Blank writes: > §6.4.5 6) say: > | It is unspecified whether these arrays are distinct provided their > | elements have the appropriate values. If the arrays resulting from "hello" and "there" were not distinct from each other, then their elements would not have the appropriate values.

Bug#517659: ppl - FTBFS: Missuse of buildd resources

Package: ppl Version: 0.10-4 Severity: serious The build of ppl needs 7 CPU-hours on a fast machine, including a long documentation run. Also I saw at least 4 runs of the same test set. > Automatic build of ppl_0.10-4 on lxdebian.bfinv.de by sbuild/s390 98 [...] > Build needed 06:58:18, 1434876k

Bug#517653: gcc-4.3: "warning: comparison with string literal results in unspecified behavior" when comparing two different literals

On Sun, Mar 01, 2009 at 10:40:40AM +0200, Kalle Olavi Niemitalo wrote: > results in a warning: > hoh.c: In function ‘main’: > hoh.c:4: warning: comparison with string literal results in unspecified > behavior > The warning claims the behaviour is unspecified. The warning is correct. The behaviour

Bug#517653: gcc-4.3: "warning: comparison with string literal results in unspecified behavior" when comparing two different literals

Package: gcc-4.3 Version: 4.3.1-4 Severity: minor Compiling this with gcc-4.3 -Wall -c int main (void) { return "hello" == "there"; } results in a warning: hoh.c: In function ‘main’: hoh.c:4: warning: comparison with string literal results in unspecified behavior The warning claims the behav