public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ghazi@caip.rutgers.edu To: gcc-gnats@gcc.gnu.org Cc: mark@codesourcery.com Subject: c++/10070: [3.3 regression] mips-sgi-irix6.5 error in g++.other/decl5.C Date: Fri, 14 Mar 2003 01:06:00 -0000 [thread overview] Message-ID: <20030314010003.19606.qmail@sources.redhat.com> (raw) >Number: 10070 >Category: c++ >Synopsis: [3.3 regression] mips-sgi-irix6.5 error in g++.other/decl5.C >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Fri Mar 14 01:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Kaveh Ghazi >Release: gcc 3.3 20030313 (prerelease) >Organization: >Environment: mips-sgi-irix6.5 >Description: Sometime between 20030309 and 20030311 I started getting crashes in g++.other/decl5.C as shown between these two reports: http://gcc.gnu.org/ml/gcc-testresults/2003-03/msg00575.html http://gcc.gnu.org/ml/gcc-testresults/2003-03/msg00732.html gdb says: Program received signal SIGSEGV, Segmentation fault. yyparse () at parse.y:2337 (gdb) bt #0 yyparse () at parse.y:2337 #1 0x1018e9d0 in c_common_parse_file (set_yydebug=200) at ../../egcc-3.3-CVS20030312/gcc/c-lex.c:159 #2 0x101ad144 in compile_file () at ../../egcc-3.3-CVS20030312/gcc/toplev.c:2126 #3 0x101b4958 in do_compile () at ../../egcc-3.3-CVS20030312/gcc/toplev.c:5363 #4 0x101b4a88 in toplev_main (argc=16, argv=0x7fff2ef4) at ../../egcc-3.3-CVS20030312/gcc/toplev.c:5393 #5 0x1019b404 in main (argc=200, argv=0x7fff20e0) at ../../egcc-3.3-CVS20030312/gcc/main.c:35 (gdb) >How-To-Repeat: Target mips-sgi-irix6.5 and compile decl5.ii with: cc1plus -fpreprocessed decl5.ii -quiet -dumpbase decl5.C -ansi -auxbase-strip /var/tmp/gcc-testing/branch/build/gcc/testsuite/decl5.o -pedantic-errors -Wno-long-long -ansi -version -fmessage-length=0 -o decl5.s # 1 "/caip/u58/ghazi/gcc-testing/branch/egcc-3.3-CVS20030312/gcc/testsuite/g++.old-deja/g++.other/decl5.C" # 1 "<built-in>" # 1 "<command line>" # 1 "/caip/u58/ghazi/gcc-testing/branch/egcc-3.3-CVS20030312/gcc/testsuite/g++.old-deja/g++.other/decl5.C" # 10 "/caip/u58/ghazi/gcc-testing/branch/egcc-3.3-CVS20030312/gcc/testsuite/g++.old-deja/g++.other/decl5.C" struct A { int A::fn(); int A::m; struct e; struct A::e {int i;}; struct A::expand { int m; }; struct Z; expand me; void foo(struct A::e); void foo(struct A::z); }; struct Q; struct B { struct A::fink { int m; }; struct A::Z { int m; }; int m; int n; struct ::Q { int m; }; int A::fn() { return 0; } void fn(struct ::Q &); void foo(struct A::y); }; struct ::C { int i; }; namespace N { int fn(); struct F; } namespace NMS { void NMS::fn(); int NMS::i; struct NMS::D { int i; }; struct N::E { int i; }; struct ::F { int i; }; int N::fn() { return 0; } struct N::F { int i; }; } NMS::D thing; void NMS::fn() { i = 3; } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-14 1:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-14 1:06 ghazi [this message] 2003-03-14 8:16 Eric Botcazou 2003-03-14 13:46 Kaveh R. Ghazi 2003-03-14 14:16 Kaveh R. Ghazi 2003-03-14 15:39 ebotcazou
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030314010003.19606.qmail@sources.redhat.com \ --to=ghazi@caip.rutgers.edu \ --cc=gcc-gnats@gcc.gnu.org \ --cc=mark@codesourcery.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).