public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: binutils@sources.redhat.com, bug-binutils@sources.redhat.com
Subject: vax quad.exp testsuite failure
Date: Thu, 08 Feb 2001 19:53:00 -0000	[thread overview]
Message-ID: <200102090353.WAA27551@hiauly1.hia.nrc.ca> (raw)

The following failure occurs with the cvs source from 20010202 under vax-ultrix:

Running /xxx/gnu/binutils-2.10.91/gas/testsuite/gas/vax/quad.exp ...
GAS LISTING /xxx/gnu/binutils-2.10.91/gas/testsuite/gas/vax/quad.s
        page 1


   1                            .text
   2 0000 7D8F7856              movq $0xaabbccdd12345678,r0
   2      3412DDCC
   2      BBAA50
FAIL: quad.s: quadword immediate values

The expected value for the last line is:

   2      BBAA5001

My first impression is that the expected test result is wrong (ie, the
last '01' is incorrect) and the listing output is ok.  However, in testing,
I noted that the native vax as pads the file in the following manner:

bash-2.04# /usr/bin/as -o quad.o quad.s
bash-2.04# /usr/bin/od -x quad.o
0000000  0107 0000 000c 0000 0000 0000 0000 0000
0000020  0000 0000 0000 0000 0000 0000 0000 0000
0000040  8f7d 5678 1234 ccdd aabb 0050 0004 0000
0000060

Here is a dump of the gas generated file:

bash-2.04# ../../../../objdir/gas/as-new -o quad.o quad.s
bash-2.04# /usr/bin/od -x quad.o
0000000  0107 0000 000b 0000 0000 0000 0000 0000
0000020  0000 0000 0000 0000 0000 0000 0000 0000
0000040  8f7d 5678 1234 ccdd aabb 0050
0000053

Note the different file offsets for the data section.  Also, if I add a
`nop' to the test, objdump doesn't print it:

bash-2.04# ../../../../objdir/gas/as-new -o quad.o quad.s
bash-2.04# od -x quad.o
0000000 0107 0000 000c 0000 0000 0000 0000 0000
0000020 0000 0000 0000 0000 0000 0000 0000 0000
0000040 8f7d 5678 1234 ccdd aabb 0150
0000054
bash-2.04# ../../../../objdir/binutils/objdump -hd quad.o

quad.o:     file format a.out

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .text         0000000c  00000000  00000000  00000020  2**2
		  CONTENTS, ALLOC, LOAD, CODE
  1 .data         00000000  0000000c  0000000c  0000002c  2**2
		  CONTENTS, ALLOC, LOAD, DATA
  2 .bss          00000000  0000000c  0000000c  00000000  2**2
		  ALLOC
../../../../objdir/binutils/objdump: quad.o: no symbols
Disassembly of section .text:

00000000 <.text>:
   0:   7d 8f 78 56     movq $0xaabbccdd12345678,r0
   4:   34 12 dd cc
   8:   bb aa 50
   b:   Address 0xb is out of bounds.

Thus, there appear to be issues with the padding of the text section
and the disassembly of instructions at the end of the text section.
The native vax assembler appears to pad the text section so that the
data section is aligned to a 4 byte boundary.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

             reply	other threads:[~2001-02-08 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 19:53 John David Anglin [this message]
     [not found] <no.id>
2001-03-14 15:52 ` John David Anglin
2001-03-15  3:05   ` Alan Modra
2001-03-15  8:15     ` John David Anglin
2001-03-14 16:06 ` John David Anglin

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=200102090353.WAA27551@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=binutils@sources.redhat.com \
    --cc=bug-binutils@sources.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).