public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: davem@gcc.gnu.org To: Andreas.Krakowczyk@fujitsu-siemens.com, Erwin.Unruh@fujitsu-siemens.com, Jochen.Canisius@fujitsu-siemens.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: target/3328: [sparc/Solaris] wrong code with Optimization '-O' Date: Mon, 08 Apr 2002 09:35:00 -0000 [thread overview] Message-ID: <20020408163535.28401.qmail@sources.redhat.com> (raw) Synopsis: [sparc/Solaris] wrong code with Optimization '-O' State-Changed-From-To: analyzed->closed State-Changed-By: davem State-Changed-When: Mon Apr 8 09:35:35 2002 State-Changed-Why: Cannot reproduce any problem with either -m64 or -m32 and any level of optimization on Sparc. This is with gcc-3.1 20020406 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3328
reply other threads:[~2002-04-08 16:35 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=20020408163535.28401.qmail@sources.redhat.com \ --to=davem@gcc.gnu.org \ --cc=Andreas.Krakowczyk@fujitsu-siemens.com \ --cc=Erwin.Unruh@fujitsu-siemens.com \ --cc=Jochen.Canisius@fujitsu-siemens.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).