public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Matthias Klose <doko@net.local> To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org Subject: target/10580: [3.3] [powerpc] ICE with -O -Wunreachable-code Date: Thu, 01 May 2003 13:56:00 -0000 [thread overview] Message-ID: <E19BENs-00085Q-00@tango.net.local> (raw) >Number: 10580 >Category: target >Synopsis: [3.3] [powerpc] ICE with -O -Wunreachable-code >Confidential: no >Severity: serious >Priority: low >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Thu May 01 13:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: "Robertson, Evin C" <ECR1120@MAIL.ECU.EDU> >Release: >Organization: The Debian Project >Environment: >Description: [ Reported to the Debian BTS as report #189702. Please CC 189702@bugs.debian.org on replies. Log of report can be found at http://bugs.debian.org/189702 ] behaviour seen with 3.3 CVS 20030427, not with 3.4 CVS 20030302 gcc segfaults sometimes on PPC when run with -O -Wunreachable-code Attached code sample is from bison output. Does not seem to happen with the same version on x86. $ gcc -c -O -Wunreachable-code test.c test.c: In function `yystpcpy': test.c:14: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. char * yystpcpy(char *yydest, const char *yysrc) { char *yyd = yydest; const char *yys = yysrc; while ((*yyd++ = *yys++) != '\0') ; return yyd - 1; } >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-05-01 13:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-01 13:56 Matthias Klose [this message] 2003-05-01 14:01 bangerth 2003-05-01 15:24 doko
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=E19BENs-00085Q-00@tango.net.local \ --to=doko@net.local \ --cc=189702@bugs.debian.org \ --cc=debian-gcc@lists.debian.org \ --cc=gcc-gnats@gcc.gnu.org \ /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).