public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, stucki@math.fu-berlin.de Subject: Re: optimization/4847: Optimizer on Sparc breaks routine-calls in vim60 Date: Tue, 26 Feb 2002 18:39:00 -0000 [thread overview] Message-ID: <20020227023651.29229.qmail@sources.redhat.com> (raw) Synopsis: Optimizer on Sparc breaks routine-calls in vim60 State-Changed-From-To: open->feedback State-Changed-By: rodrigc State-Changed-When: Tue Feb 26 18:36:50 2002 State-Changed-Why: Can you reproduce this with gcc 3.0.4? Can you provide a smaller, reproduceable testcase as described in the guidelines at http://gcc.gnu.org/bugs.html? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4847
next reply other threads:[~2002-02-27 2:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-26 18:39 rodrigc [this message] 2002-06-25 12:39 davem 2002-12-07 18:06 Nix
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=20020227023651.29229.qmail@sources.redhat.com \ --to=rodrigc@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=stucki@math.fu-berlin.de \ /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).