public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9895: [SH] GCC unable to retain array values in registers
Date: Sat, 10 May 2003 09:16:00 -0000 [thread overview]
Message-ID: <20030510091602.802.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/9895; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: tm_gccmail@kloo.net, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: optimization/9895: [SH] GCC unable to retain array values in registers
Date: Sat, 10 May 2003 02:09:11 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=9895
Hello,
the submitter of this bug report did not specify which version of gcc
has the problem in question. Would it be possible for the submitter
please check whether gcc 3.3 branch or mainline still has this problem?
Thanks,
Dara
next reply other threads:[~2003-05-10 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 9:16 Dara Hazeghi [this message]
2003-05-12 11:46 giovannibajo
2003-05-12 20:46 tm_gccmail
2003-05-13 6:20 steven
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=20030510091602.802.qmail@sources.redhat.com \
--to=dhazeghi@yahoo.com \
--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: link
Be 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).