public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Kirkham <Robin.Kirkham@mlb.dmt.csiro.au>
To: richard.earnshaw@arm.com
Cc: egcs@cygnus.com
Subject: Re: 971122 for arm-coff dies building newlib/libm: testcase attached
Date: Mon, 01 Dec 1997 19:30:00 -0000	[thread overview]
Message-ID: <19971202030004.4982.qmail@ragnarok.mlb.dmt.csiro.au> (raw)
In-Reply-To: <199711281251.MAA19730@sun52.NIS.cambridge>

On Fri, 28 Nov 1997, Richard Earnshaw <rearnsha@arm.com> said:
 
> Robin.Kirkham@mlb.dmt.csiro.au said:
> > > Fri Oct 17 13:00:38 EDT 1997  Richard Earnshaw  (rearnsha@arm.com)
> > > 
> > >       * arm.md (movsfcc): If not TARGET_HARD_FLOAT, ensure operand[3] val
> >
> > Richard,
> >
> > Thanks for the patch but I'm afraid to say it made no difference at
> > all! Still the same error with the same testcase. And yes I did check
> > it had applied properly, and a rebuilt egcs in a fresh build
> > directory. 
> 
> You have probably been bitten by "patch" (I just have -- first time 
> ever!).  patch incorrectly applies the patch to the wrong insn (it must be 
> applied to the movsfcc pattern, NOT the movdfcc pattern.  The two insns 
> contained the same body of code, and since I extracted the patch from the 
> gcc2 sources, the line numbers weren't exact.

Yes, that's what happened. 971122 egcs now compiles all of newlib for the
ARM without a problem. Thanks kindly.

Robin Kirkham			CSIRO Manufacturing Science and Technology
Project Engineer		Locked Bag 9, Preston 3072, Australia
robin.kirkham@mlb.dmt.csiro.au	Phone: +61 3 9662-7756  Fax: +61 3 9662-7851

       reply	other threads:[~1997-12-01 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199711281251.MAA19730@sun52.NIS.cambridge>
1997-12-01 19:30 ` Robin Kirkham [this message]
1997-11-26 23:40 Robin Kirkham
1997-11-27  4:34 ` Richard Earnshaw
1997-11-27  8:38   ` Jeffrey A Law

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=19971202030004.4982.qmail@ragnarok.mlb.dmt.csiro.au \
    --to=robin.kirkham@mlb.dmt.csiro.au \
    --cc=egcs@cygnus.com \
    --cc=richard.earnshaw@arm.com \
    /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).