linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: peter willy krause <wklux@yahoo.co.uk>
To: Martin <asmfreshmeat@gmx.de>
Cc: linux-assembly@vger.kernel.org, linux-assembly@mlists.in-berlin.de
Subject: Re: GAS/GCC Assembler Code Modification
Date: Sat, 15 May 2004 14:32:01 +0100	[thread overview]
Message-ID: <200405151432.01409.wklux@yahoo.co.uk> (raw)
In-Reply-To: <20040515112807.579e4d89@deepblack>

Am Samstag, 15. Mai 2004 10:28 schrieb Martin:
> Hi folks,
>
> I have a question regarding GAS and GCC.
> Does the GAS modify the Assembler Code? If I try to assemble (for
> example) the following line:
>
> popl %esi
>
> the gas changes that to
>
> pop %esi

though gas 'optimizes', which cannot be configured(!), in your example gas 
doesn't, re listing by gas, itself! (my version ex binutils 2.14.90) - 
apparently, your disassembler translates differently. compare the code...

the only 'optimization' by gas, which I'm aware of, is branches distance 
coding and selection of alignment fill code. branches coding can be 
forced to always 'long' (4 bytes) by declaring the destn label '.global'.

while assembling gas tries to deduce the oprands' formats by mnemonics and 
register nameing and, tries some correction if the proper size specs were 
missing, plus emanating a concerning warning (not an error!) message.


best,
	hp
-- 
mail to 'hp': lx at lxhp : in-berlin : de


  parent reply	other threads:[~2004-05-15 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-15  9:28 GAS/GCC Assembler Code Modification Martin
2004-05-15 10:15 ` sandeep
2004-05-15 13:32 ` peter willy krause [this message]
2004-05-15 20:08   ` Martin
2004-05-15 21:45     ` peter willy krause
2004-05-15 21:01       ` Martin

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=200405151432.01409.wklux@yahoo.co.uk \
    --to=wklux@yahoo.co.uk \
    --cc=asmfreshmeat@gmx.de \
    --cc=linux-assembly@mlists.in-berlin.de \
    --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).