public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: alan@spri.levels.unisa.edu.au (Alan Modra)
To: gas2@cygnus.com
Subject: gas fixup problem?
Date: Wed, 21 Jun 1995 16:57:00 -0000	[thread overview]
Message-ID: <m0sOZeD-0000y0C@mullet> (raw)

/usr/i486-linux/bin/as zzz.s; nm a.out
00000000 t L0
00000006 t L1
00000002 t L2		!!!!!!!!!
00000006 t L3
00000015 t L4
00000094 t L5

 --------------------zzz.s----------------
	.text
L0:
	jz L5
L1:
L2:
L3:
	.space -(L2 - L0 + 0x7f) & (16-1), 0x90

L4:
	.space 0x7f, 0x90
L5:
 -----------------------------------------

The idea of the .space here is to align L5, given we know how much
code is between the .space and L5.  Maybe this bug is just related to
.space, but if it's something to do with expression evaluation, then
it is a more serious one.  I'll see if I can fix it myself, but my
time is rather limited at the moment.  Maybe someone else will get
curious as to what is wrong here?


             reply	other threads:[~1995-06-21 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-06-21 16:57 Alan Modra [this message]
     [not found] <no.id>
1995-06-24  3:51 ` Alan Modra

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=m0sOZeD-0000y0C@mullet \
    --to=alan@spri.levels.unisa.edu.au \
    --cc=gas2@cygnus.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).