public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@microdata-pos.de>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH-RFC] Testcase(s) for VAX' new -M entry:0xf00 feature
Date: Wed, 30 Mar 2005 14:28:00 -0000	[thread overview]
Message-ID: <20050329231148.D17534@microdata-pos.de> (raw)
In-Reply-To: <42498028.6000901@redhat.com>; from nickc@redhat.com on Tue, Mar 29, 2005 at 05:19:52PM +0100

On Tue, Mar 29, 2005 at 05:19:52PM +0100, Nick Clifton wrote:
> Hi Jan-Benedict,
> 
>    I have checked your new VAX test patch into the CVS repository.

Thanks!

> > - Also add a -M entry:0x... for label2 (which I'd prefer to do)
> 
> I think that I would prefer this approach as well.

Here's the patch. Passes cross-build/hosted on my PC for vax-linux,
vax-ultrix, vax-netbsd and vax-netbsdelf.

2005-03-29  Jan-Benedict Glaw  <jbglaw@lug-owl.>

	binutils/testsuite/binutils-all/vax/
	* objdump.exp: Condense the two tests into one and add a
	"-m entry:" for the second label.

diff -Nurp src-fresh/binutils/testsuite/binutils-all/vax/objdump.exp src-hacked/binutils/testsuite/binutils-all/vax/objdump.exp
--- src-fresh/binutils/testsuite/binutils-all/vax/objdump.exp	2005-03-29 18:13:48.000000000 +0200
+++ src-hacked/binutils/testsuite/binutils-all/vax/objdump.exp	2005-03-29 23:03:07.000000000 +0200
@@ -45,11 +45,12 @@ if [is_remote host] {
 }
 
 #
-# First run. We expect the function to be a function and the sole label
-# not to produce an entry mask.
+# We check both function entry points. The second one at offset 2 will
+# show up automatically on ELF targets, but needs to be set on a.out
+# targets.
 #
-set got [binutils_run $OBJDUMP "$OBJDUMPFLAGS -d $objfile"]
-set want1 "\[ 	\]+0:\[ 	\]+10 01\[ 	\]+bsbb 3"
+set got [binutils_run $OBJDUMP "$OBJDUMPFLAGS -d -M entry:0x0 -M entry:2 $objfile"]
+set want1 "\[ 	\]+0:\[ 	\]+10 01\[ 	\]+\\.word 0x0110.\*r8 r4"
 set want2 "\[ 	\]+2:\[ 	\]+24 02\[ 	\]+\\.word 0x0224.\*r9 r5 r2"
 if [regexp $want1 $got] then {
     pass "entrymask test 1"
@@ -62,21 +63,3 @@ if [regexp $want2 $got] then {
     fail "entrymask test 2"
 }
 
-#
-# Second run. Now, we force the label as a function, so we expect that
-# it also produces an entry mask, as any call'able function should.
-#
-set got [binutils_run $OBJDUMP "$OBJDUMPFLAGS -d -M entry:0x0 $objfile"]
-set want3 "\[ 	\]+0:\[ 	\]+10 01\[ 	\]+\\.word 0x0110.\*r8 r4"
-set want4 "\[ 	\]+2:\[ 	\]+24 02\[ 	\]+\\.word 0x0224.\*r9 r5 r2"
-if [regexp $want3 $got] then {
-    pass "entrymask test 3"
-} else {
-    fail "entrymask test 3"
-}
-if [regexp $want4 $got] then {
-    pass "entrymask test 4"
-} else {
-    fail "entrymask test 4"
-}
-

MfG, JBG

-- 
AWEK microdata GmbH -- Am Wellbach 4 -- 33609 Bielefeld

  reply	other threads:[~2005-03-29 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25  3:28 Jan-Benedict Glaw
2005-03-26 13:33 ` Jan-Benedict Glaw
2005-03-26 14:21   ` Jan-Benedict Glaw
2005-03-29 19:53   ` Nick Clifton
2005-03-30 14:28     ` Jan-Benedict Glaw [this message]
2005-04-04 17:20       ` Nick Clifton

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=20050329231148.D17534@microdata-pos.de \
    --to=jbglaw@microdata-pos.de \
    --cc=binutils@sources.redhat.com \
    --cc=nickc@redhat.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).