public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9015: bc segfaults when compiled with optimization Date: Fri, 03 Jan 2003 19:46:00 -0000 [thread overview] Message-ID: <20030103194604.13637.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9015; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Patrick Smith <patsmith@pobox.com> Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Subject: Re: optimization/9015: bc segfaults when compiled with optimization Date: Fri, 3 Jan 2003 13:45:35 -0600 (CST) On Tue, 24 Dec 2002, Patrick Smith wrote: > Found it. > > This turns out to be a bug in GNU bc. As luck would have it, it only > seems to cause damage when compiled with optimization on and a recent > gcc. :-( > > Sorry to have bothered you. No need to apologize. Rather: Thanks for looking into this, as otherwise one of us would have to do the work. > (In case you're interested... load_code saves data in a local variable > on one call, and then tries to retrieve that data on a subsequent call.) I assume that the variable is not static, right? Regards Wolfgang PS: Don't forget to send a patch (or some other indication of the problem) to the bc people. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2003-01-03 19:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-03 19:46 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-03 19:46 bangerth 2002-12-24 16:56 Patrick Smith 2002-12-20 22:06 Wolfgang Bangerth 2002-12-20 21:56 Patrick Smith 2002-12-20 19:20 bangerth 2002-12-19 20:46 patsmith
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=20030103194604.13637.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).