public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/4508: [ARM] gcc 3.0, ARM/thumb target, generates invalid asm
Date: Tue, 15 Jan 2002 02:36:00 -0000 [thread overview]
Message-ID: <20020115103602.15354.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/4508; it has been noted by GNATS.
From: Richard Earnshaw <rearnsha@arm.com>
To: Ted Merrill <ted@arraycomm.com>
Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
nobody@gcc.gnu.org, rearnsha@arm.com
Subject: Re: target/4508: [ARM] gcc 3.0, ARM/thumb target, generates
invalid asm
Date: Tue, 15 Jan 2002 10:34:43 +0000
Ted,
I'm sorry I've not been more pro-active on this, I've been overloaded with
other issues recently, plus I was on sabatical late last year.
It is a bit difficult even for me here to accept code that might be
considered confidential (our lawyers would probably have something to say
about it unless there was some form of legal agreement in place).
However, I don't think there is any need, since I suspect that I already
know what the basic problem is here.
If the problem is what I think, then I believe the latest CVS copy of the
compiler has a fix for this bug installed now. I would be grateful if you
could find a chance to check it out and try it on your problem code,
please let us know how you get on, then we can close this report.
R.
next reply other threads:[~2002-01-15 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 2:36 Richard Earnshaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 22:06 wb
2002-01-15 13:28 rodrigc
2002-01-15 13:06 Ted Merrill
2002-01-14 19:46 Ted Merrill
2002-01-14 18:48 rodrigc
2002-01-14 18:36 Ted Merrill
2002-01-13 16:35 rodrigc
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=20020115103602.15354.qmail@sources.redhat.com \
--to=rearnsha@arm.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).