From: Maciej Hrebien <m_hrebien@wp.pl>
To: linux-assembly@vger.kernel.org
Subject: Re: gas' nop(s)
Date: Fri, 09 Aug 2002 21:47:12 +0200 [thread overview]
Message-ID: <3D541C40.C8BD3519@wp.pl> (raw)
In-Reply-To: 20020809160727.0462fe8c.*@lxhp.in-berlin.de
h-peter recktenwald wrote:
>
> > > > Yes, right! But it still adds "89F6" padding which stands for "mov
> > > > %esi,%esi" & my question was how to avoid this.
> >
> > just tried: apparently, the ".end" directive inhibits those alignemt bytes,
> > (if not a label at end of code).
>
> that was an error. though i wonder how some program of mine ends up
> with an odd address. probably due to its .data end. so i tried asm
> into a .data section, which works and, does #not# align. so, since you
> seem not to asm to any fixed 'format', that might be the alternative.
Good idea!! I've tried to move our example (this with simple exit call)
to the .data section but it still adds padding - it's: add %al,(%eax)
(coded as "00 00") on my gas even with .align directive set to 1. But!
I've followed Your way of thinking and guess what?! :) "why not to move
this code to the .rodata section?" and... it works just fine!! No
paddings!! :)
Thank You very much for Your suggestion Peter (is that Your name?)!!!
--
Maciej Hrebien
prev parent reply other threads:[~2002-08-09 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 20:28 gas' nop(s) m_hrebien
[not found] ` <20020805091651.245c7d4b.jani@iv.ro>
2002-08-05 9:23 ` m_hrebien
2002-08-05 10:20 ` h-peter recktenwald
2002-08-05 17:53 ` m_hrebien
2002-08-05 22:21 ` h-peter recktenwald
2002-08-06 9:30 ` m_hrebien
2002-08-07 7:41 ` h-peter recktenwald
2002-08-08 15:50 ` h-peter recktenwald
2002-08-09 16:07 ` h-peter recktenwald
2002-08-09 19:47 ` Maciej Hrebien [this message]
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=3D541C40.C8BD3519@wp.pl \
--to=m_hrebien@wp.pl \
--cc=linux-assembly@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).