From: Andreas Schwab <schwab@suse.de>
To: Finn Thain <ft01@webmastery.com.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: make checkstack on m68k
Date: Thu, 17 Jun 2004 17:31:58 +0200 [thread overview]
Message-ID: <jeoenip5e9.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0406180048180.13963@bonkers.disegno.com.au> (Finn Thain's message of "Fri, 18 Jun 2004 01:17:31 +1000 (EST)")
Finn Thain <ft01@webmastery.com.au> writes:
> On Thu, 17 Jun 2004, Andreas Schwab wrote:
>
>> Geert Uytterhoeven <geert@linux-m68k.org> writes:
>>
>> > I tried to add m68k support to `make checkstack', but got stuck due to my
>> > limited knowledge of complex perl expressions. I actually need to catch both
>> > expressions (incl. the one I commented out). Anyone who can help?
>>
>> Untested:
>>
>> $re = qr/.*(?:linkw %fp,|addw )#-([0-9]{1,4})(?:,%sp)?$/o;
>>
>> Andreas.
>
> I think that should be addaw, not addw.
Right, typo.
> And it may be necessary to remove the $ anchor at the end.
That won't work, because we must be sure to require ",%sp" when addaw is
matched since we don't want to match, say, "addaw #-1024,%a0". We know
that this is the whole line to be matched.
> Your solution makes very nice use of the fact that objdump produces
> exactly one comma for those opcodes :)
We know exactly the format of the output produced by objdump. So even
though the regex is able to match some random junk we know that objdump
would never produce that.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-06-17 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 16:51 Geert Uytterhoeven
2004-06-16 18:04 ` Jörn Engel
2004-06-17 8:25 ` Geert Uytterhoeven
2004-06-17 11:45 ` Jörn Engel
2004-06-17 11:41 ` Andreas Schwab
2004-06-17 15:17 ` Finn Thain
2004-06-17 15:31 ` Andreas Schwab [this message]
2004-06-17 18:26 ` Jörn Engel
2004-06-17 19:15 ` Geert Uytterhoeven
2004-06-17 19:36 ` Geert Uytterhoeven
2004-06-18 13:02 ` Jörn Engel
2004-06-18 13:16 ` Geert Uytterhoeven
2004-06-17 17:41 ` Jörn Engel
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=jeoenip5e9.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ft01@webmastery.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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
all inboxes | Powered by JetHome®