public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Christoph Breitkopf <chr.breitkopf@magrathea.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: optimization/3480 Date: Thu, 13 Sep 2001 06:06:00 -0000 [thread overview] Message-ID: <20010913130602.26657.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR optimization/3480; it has been noted by GNATS. From: Christoph Breitkopf <chr.breitkopf@magrathea.de> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, jk@tools.de, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: optimization/3480 Date: Thu, 13 Sep 2001 14:57:45 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3480&database=gcc Hello, I have observed the same bug in one of our Applications with gcc-3.01 under Linux: Reading specs from /usr/local/gcc-3.0.1/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/specs Configured with: ../gcc-3.0.1/configure --prefix=/usr/local/gcc-3.0.1 Thread model: single gcc version 3.0.1 Getting a segmentation fault with -O3 -fomit-frame-pointer. I can send preprocessed source and assembly output, if you need another example besides the one Juergen sent. Regards, Chris
reply other threads:[~2001-09-13 6:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010913130602.26657.qmail@sourceware.cygnus.com \ --to=chr.breitkopf@magrathea.de \ --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).