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, nobody@gcc.gnu.org, pike@cs.berkeley.edu Subject: Re: c/4304: wrong code on sparc-sun-solaris2.6 Date: Wed, 24 Apr 2002 15:55:00 -0000 [thread overview] Message-ID: <20020424225515.32734.qmail@sources.redhat.com> (raw) Synopsis: wrong code on sparc-sun-solaris2.6 State-Changed-From-To: open->feedback State-Changed-By: rth State-Changed-When: Wed Apr 24 15:55:14 2002 State-Changed-Why: No, in <m1yImT5Hello+3804>: st %l5, [ %l4 + %i1 ] %l5 is *not* being used as a pointer. Rather, %l5 is being stored. Your report is too vague to be able to figure out what you really meant. This is hindered further by not supplying an executable test case. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4304
next reply other threads:[~2002-04-24 22:55 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-24 15:55 rth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-25 12:37 davem 2001-09-11 18:46 pike
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=20020424225515.32734.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=nobody@gcc.gnu.org \ --cc=pike@cs.berkeley.edu \ /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).