public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: cgd@broadcom.com To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9301: mips-linux gcc 3.2.1 SEGV in try_forward_edges Date: Mon, 13 Jan 2003 23:56:00 -0000 [thread overview] Message-ID: <20030113235603.1957.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9301; it has been noted by GNATS. From: cgd@broadcom.com To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: optimization/9301: mips-linux gcc 3.2.1 SEGV in try_forward_edges Date: 13 Jan 2003 15:47:35 -0800 Of course, wouldn't do to include all of the relevant info in the intial submission: command line to cause the problem is: gcc -O2 -c ~/trimmed3.c which results in: /home/cgd/trimmed3.c: In function `foo': /home/cgd/trimmed3.c:12: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. easy enough. 8-) chris
next reply other threads:[~2003-01-13 23:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-13 23:56 cgd [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-21 19:56 cgd 2003-01-13 23:46 cgd
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=20030113235603.1957.qmail@sources.redhat.com \ --to=cgd@broadcom.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).