From: Richard Earnshaw <rearnsha@arm.com>
To: Robin Kirkham <Robin.Kirkham@mlb.dmt.csiro.au>
Cc: rearnsha@arm.com
Subject: Re: 971122 for arm-coff dies building newlib/libm: testcase attached
Date: Thu, 27 Nov 1997 04:34:00 -0000 [thread overview]
Message-ID: <199711271232.MAA13804@sun52.NIS.cambridge> (raw)
In-Reply-To: <19971127064525.24524.qmail@ragnarok.mlb.dmt.csiro.au>
This patch was checked into the gcc2 sources back in October to fix
precisely this bug. There are a large number of ARM related patches that
have been made to the gcc2 tree that have not yet propagated to egcs (ie
most of them). I thought there were going to be regular merges of gcc2
changes into the egcs tree?
Fri Oct 17 13:00:38 EDT 1997 Richard Earnshaw (rearnsha@arm.com)
* arm.md (movsfcc): If not TARGET_HARD_FLOAT, ensure operand[3]
valid.
next prev parent reply other threads:[~1997-11-27 4:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-26 23:40 Robin Kirkham
1997-11-27 4:34 ` Richard Earnshaw [this message]
1997-11-27 8:38 ` Jeffrey A Law
[not found] <199711281251.MAA19730@sun52.NIS.cambridge>
1997-12-01 19:30 ` Robin Kirkham
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=199711271232.MAA13804@sun52.NIS.cambridge \
--to=rearnsha@arm.com \
--cc=Robin.Kirkham@mlb.dmt.csiro.au \
/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).