public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rth@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marcus@mc.pp.se, rth@gcc.gnu.org Subject: Re: optimization/5768: sh codegen leaves stuff on stack Date: Mon, 25 Mar 2002 14:06:00 -0000 [thread overview] Message-ID: <20020325220621.19476.qmail@sources.redhat.com> (raw) Synopsis: sh codegen leaves stuff on stack State-Changed-From-To: open->feedback State-Changed-By: rth State-Changed-When: Mon Mar 25 14:06:20 2002 State-Changed-Why: This appears to have been fixed for gcc 3.1. Would you mind checking the prerelease snapshots to verify this for your real application as opposed to merely the test case? For the last test in this thread, I see r8 being restored in the delay slot of the jump, like so: jmp @r4 mov.l @r15+,r8 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5768
next reply other threads:[~2002-03-25 22:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-25 14:06 rth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-27 14:20 rth 2002-03-27 14:16 Marcus Comstedt 2002-03-25 10:10 rth 2002-03-07 8:06 Marcus Comstedt 2002-03-06 21:36 Arati Dikey 2002-03-06 15:06 Marcus Comstedt 2002-02-23 21:47 marcus
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=20020325220621.19476.qmail@sources.redhat.com \ --to=rth@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=marcus@mc.pp.se \ /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).