Bug#188943: g++-3.2: code using dynamic_cast causes segfaults when -fno-rtti is used

On Thursday 01 May 2003 06:57, Matthias Klose wrote: > Please can you check, if the behaviour is the same with g++-3.3? > Yes, it is. Attached is a program which shows this problem. Normally it will work just fine however add -fno-rtti and it segfaults. Using -Wall -W -pedantic does not give a

Bug#178561: libstdc++ docs: forwarded message from herbert@gondor.apana.org.au

> The stream::attach entry in porting-howto.html does not mention the > stdio_filebuf as an alternative. I'll try to get in touch with the upstream author of porting-howto.xml. Failing that, if anybody knows how to use "docbook" to edit or generate or do whatever to porting-howto.xml, a patch to u

Processed: gcc report: pascal on the hurd

Processing commands for [EMAIL PROTECTED]: > reopen 189851 Bug#189851: FTBFS on hurd-i386 Bug reopened, originator not changed. > severity 189851 normal Bug#189851: FTBFS on hurd-i386 Severity set to `normal'. > retitle 189851 gpc does not build on hurd-i386 Bug#189851: FTBFS on hurd-i386 Change

Results for 3.3 20030429 (Debian prerelease) testsuite on arm-unknown-linux-gnu

LAST_UPDATED: Tue Apr 29 23:59:54 UTC 2003 Native configuration is arm-unknown-linux-gnu === libjava tests === Running target unix FAIL: calls run WARNING: program timed out. FAIL: cxxtest run FAIL: field run FAIL: final_method run FAIL: findclass run FAIL: invoke run FAIL: mart

Results for 3.3 20030429 (Debian prerelease) testsuite on sparc-unknown-linux-gnu

LAST_UPDATED: Tue Apr 29 23:59:54 UTC 2003 Native configuration is sparc-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/parse/crash2.C (test for errors, line 5) FAIL: g++.dg/parse/crash2.C (test for excess errors) FAIL: g++.law/profile1.C Execution test X

Processed: gcc: submitted Debian report #189365 to gcc-gnats as PR 10587

Processing commands for [EMAIL PROTECTED]: > # submitted Debian report #189365 to gcc-gnats as PR 10587 > # http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=10587&database=gcc > forwarded 189365 [EMAIL PROTECTED] Bug#189365: libquicktime_0.9.2pre1-7 triggers ICE on ia64 Noted your statement that

Bug#189365: target/10587: [3.2/3.3 regression] [ia64] ICE in copy_to_mode_reg compiling libquicktime

Thank you very much for your problem report. It has the internal identification `target/10587'. The individual assigned to look at your report is: unassigned. >Category: target >Responsible:unassigned >Synopsis: [3.2/3.3 regression] [ia64] ICE in copy_to_mode_reg compiling >libqu

Bug#191407: FTBFS: Pascal breaks on (at least) netbsd-i386

On Wed, Apr 30, 2003 at 08:42:52PM +0200, Frank Heckenbach wrote: > > I can't tell anything from this report. With an access, I could try > to debug it. > > If you just want to continue the build, try creating an empty > gcc/p/utils/needed-options file in the build directory (but the > problem ma

Bug#180530: marked as done (PPC32: Segfault when compiling the kernel (2.4.20))

Your message dated Thu, 1 May 2003 21:22:35 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line Bug#180530: PPC32: Segfault when compiling the kernel (2.4.20) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#190791: gcc-3.2: random failure

Michel Dänzer writes: > Let me know if I can provide any more useful information, but I'm afraid the > randomness doesn't make that easy. please retry using the released gcc-3.2.3 (-1) and the current gcc-3.3 (0pre7) package. Matthias

Processed: gcc: submitted Debian report #186922 to gcc-gnats as PR 10581

Processing commands for [EMAIL PROTECTED]: > # submitted Debian report #186922 to gcc-gnats as PR 10581 > # http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=10581&database=gcc > forwarded 186922 [EMAIL PROTECTED] Bug#186922: gcj-3.2: crash trying to compile freenet Noted your statement that Bug

[3.2/3.3 regression] [ia64] ICE in copy_to_mode_reg compiling libquicktime

>Submitter-Id: net >Originator:Bdale Garbee <[EMAIL PROTECTED]> >Organization: The Debian Project >Confidential: no >Synopsis: >Severity: serious >Priority: medium >Category: target >Class: ice-on-legal-code >Description: [ Reported to the Debian BTS as report #

Re: Processed: Re: Bug#186937: [hppa, PR target/10271] Floating point args don't get reloaded across function calls at -O2

[EMAIL PROTECTED] (Debian Bug Tracking System) writes: > Processing commands for [EMAIL PROTECTED]: > > > retitle 186937 [fixed in 3.3] [hppa, PR target/10271] Floating point args > > don't get reloaded across function calls at -O2 This is fixed in 3.2.3 too, I say we just close it. --

Bug#186937: marked as done ([fixed in 3.3] [hppa, PR target/10271] Floating point args don't get reloaded across function calls at -O2)

Your message dated Thu, 1 May 2003 07:53:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#186937: [hppa, PR target/10271] Floating point args don't get reloaded across function calls at -O2 has caused the attached Bug report to be marked as done. This means that you claim that th

Bug#188811: marked as done (gcc segfaults on HPPA while building xprint-xprintorg)

Your message dated Thu, 1 May 2003 07:54:29 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#188811: gcc segfaults on HPPA while building xprint-xprintorg has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#191551: FTBFS: NetBSD files changed from 3.2 to 3.3

Package: gcc-3.3 Version: 1:3.3ds5-0pre5 Severity: normal Tags: patch The architecture config files for gcc have changed between 3.2 and 3.3; thus, the old NetBSD patches no longer work. However, the changes introduced a significant measure of sanity, and thus the new patches are much easier to wo

Processed: Re: Bug#186937: [hppa, PR target/10271] Floating point args don't get reloaded across function calls at -O2

Processing commands for [EMAIL PROTECTED]: > retitle 186937 [fixed in 3.3] [hppa, PR target/10271] Floating point args > don't get reloaded across function calls at -O2 Bug#186937: [hppa, PR target/10271] Floating point args don't get reloaded across function calls at -O2 Changed Bug title. >

Bug#186937: [hppa, PR target/10271] Floating point args don't get reloaded across function calls at -O2

retitle 186937 [fixed in 3.3] [hppa, PR target/10271] Floating point args don't get reloaded across function calls at -O2 forwarded 186937 [EMAIL PROTECTED] thanks Randolph Chung writes: > Package: gcc-3.2 > Severity: important > > [Debian note: this may be related to #185184 and #105816] > >

Bug#188811: gcc segfaults on HPPA while building xprint-xprintorg

Randolph Chung writes: > > #186447 is a segfault in the compiler, you get a segfault in the > > assembler (program as). Please recheck using gcc-3.3 and report the > > results. > > retrying with latest binutils seem to work. Lamont has rescheduled the > dozen-or-so packages that had segfaults on t

Bug#176081: marked as done (libgcj.so.3.0.0 has non-PIC static code linked in)

Your message dated Thu, 1 May 2003 17:42:39 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#176081: libgcj.so.3.0.0 has non-PIC static code linked in has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Processed: gcc: submitted Debian report #189702 to gcc-gnats as PR 10580

Processing commands for [EMAIL PROTECTED]: > # submitted Debian report #189702 to gcc-gnats as PR 10580 > # http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=10580&database=gcc > forwarded 189702 [EMAIL PROTECTED] Bug#189702: gcc segfaults with -O -Wunreachable-code Noted your statement that Bug

Bug#186922: java/10581: ICE compiling freenet

Thank you very much for your problem report. It has the internal identification `java/10581'. The individual assigned to look at your report is: unassigned. >Category: java >Responsible:unassigned >Synopsis: ICE compiling freenet >Arrival-Date: Thu May 01 14:46:01 UTC 2003

ICE compiling freenet

>Submitter-Id: net >Originator:Erno Kuusela <[EMAIL PROTECTED]> >Organization: The Debian Project >Confidential: no >Synopsis: >Severity: serious >Priority: medium >Category: java >Class: ice-on-legal-code >Description: [ Reported to the Debian BTS as report #18

Bug#188513: gcc generates invalid assembler on arm

Please can you recheck with g++-3.3? Eric Schwartz writes: > Package: gcc-3.2 > Version: 3.2.3-0pre7 > > When the buildds try to compile gforth for arm, I get the following > error messages: > > gcc -I./../arch/generic -I. -O2 -Wall -g -O2 -DHAVE_CONFIG_H > -DDEFAULTPATH=\".:/usr/lib/gforth

Bug#188943: g++-3.2: code using dynamic_cast causes segfaults when -fno-rtti is used

Please can you check, if the behaviour is the same with g++-3.3? Sean Perry writes: > Package: g++-3.2 > Version: 1:3.2.3-0pre7 > Severity: normal > > Now obviously, dynamic_cast requires rtti so using -fno-rtti is > silly. I ran into this on a C++ project where we had been using > -fno-rtti be

Bug#189702: target/10580: [3.3] [powerpc] ICE with -O -Wunreachable-code

Thank you very much for your problem report. It has the internal identification `target/10580'. The individual assigned to look at your report is: unassigned. >Category: target >Responsible:unassigned >Synopsis: [3.3] [powerpc] ICE with -O -Wunreachable-code >Arrival-Date: Thu M

[3.3] [powerpc] ICE with -O -Wunreachable-code

>Submitter-Id: net >Originator:"Robertson, Evin C" <[EMAIL PROTECTED]> >Organization: The Debian Project >Confidential: no >Synopsis: >Severity: serious >Priority: low >Category: target >Class: ice-on-legal-code >Description: [ Reported to the Debian BTS as repo