public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@bigfoot.com>
To: "binutils@sourceware.cygnus.com" <binutils@sourceware.cygnus.com>
Subject: gas: .align padding
Date: Fri, 15 Oct 1999 04:25:00 -0000	[thread overview]
Message-ID: <380710B0.43FB7D34@bigfoot.com> (raw)

Good morning.  A few things:

----
When padding .aligns gas seems to put random gunk into the object file
instead of nops or nulls. Can this be fixed?



bix:~> cat t.s
        nop
        .align 8
        nop

bix:~> objdump --disassemble t.o

t.o:     file format elf32-i386

Disassembly of section .text:

00000000 <.text>:
   0:   90                      nop
   1:   8d b4 26 00 00 00 00    leal   0x0(%esi,1),%esi
   8:   90                      nop

bix:~> as -v
GNU assembler version 2.9.1 (i386-mandrake-linux), using BFD version
2.9.1.0.25

bix:~> uname -a
Linux bix 2.2.9-27mdk #1 Mon Jun 14 16:44:05 CEST 1999 i586 unknown


----

I've noticed that if you have "." ahead of /usr/bin in $PATH then
binutils' configure script fails mysteriously.  It turns out this is
because collect2 is trying to execute the directory 'ld' in the binutils
toplevel.

I'm sure this is a known gcc problem (libiberty/pexecute, perhaps?), but
don't we think something a bit more user friendly can be done?

----

Finally...  I'd like to be wildly unorthodox here and actually
congratulate you folks on the GNU development system.  I used to bang on
this stuff quite a lot five years ago, and as I now revisit it I'm quite
astonished at the quality and at the amount of work that's been added.

There's a tendency 'out there' to take all this for granted, which is
regrettable because these products really are the foundation of
_everything_.

So, thanks!


- Andrew.

             reply	other threads:[~1999-10-15  4:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-15  4:25 Andrew Morton [this message]
1999-10-15  4:38 ` Alan Modra
1999-10-15  6:42   ` Andrew Morton
1999-10-15  4:40 ` Jakub Jelinek
1999-10-15 10:00 ` Ian Lance Taylor

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=380710B0.43FB7D34@bigfoot.com \
    --to=akpm@bigfoot.com \
    --cc=binutils@sourceware.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).