From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 06/15] MIPS/GAS/test: Adjust LD for multi-target testing
Date: Mon, 18 Oct 2010 17:46:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.00.1010180410510.15889@eddie.linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1010180157491.15889@eddie.linux-mips.org>
On Mon, 18 Oct 2010, Maciej W. Rozycki wrote:
> > The patch seems to contain some parts that make the matching more strict
> > and some that make it less so. The former look good, but I'm less sure
> > about the latter. For example, with something like:
> >
> > [0-9a-f]+ <[^>]*> lw a0,(0|4096)\(at\)
> > [ ]*[0-9a-f]+: [A-Z0-9_]*LO[A-Z0-9_]* \.data(\+0xfffff000)?
> >
> > the difference seems relatively important: on some targets the addend
> > must be in-place, on some it mustn't be. It might make more sense
> > to have separate dumps for the two cases. However, that sort of
> > difference is probably picked up by other tests too, so the risk
> > might not be great.
>
> This is certainly strictier than the original that for the record was:
>
> [0-9a-f]+ <[^>]*> lw a0,0\(at\)
> [ ]*[0-9a-f]+: [A-Z0-9_]*LO[A-Z0-9_]* .data.*
>
> (and obviously failed for ECOFF because of the different in-place addend).
Wrong quotation actually, taken from the bit-rotten ld-ilocks.d -- the
typical patterns this addresses were ones like these in ld.d:
[0-9a-f]+ <[^>]*> lw a0,[-0-9]+\(at\)
[ ]*[0-9a-f]+: [A-Z0-9_]*LO[A-Z0-9_]* .data.*
that have been clearly adjusted for ECOFF and matched any in-place as well
as relocation addends. The new patterns are no less strict and then the
rest of my consideration applies.
Maciej
prev parent reply other threads:[~2010-10-18 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 19:40 Maciej W. Rozycki
2010-10-10 9:45 ` Richard Sandiford
2010-10-18 1:39 ` Maciej W. Rozycki
2010-10-18 17:46 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.00.1010180410510.15889@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=binutils@sourceware.org \
--cc=rdsandiford@googlemail.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).