From: "H. J. Lu" <hjl@lucon.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: dave.korn@artimi.com, binutils@sources.redhat.com
Subject: Re: [PATCH] x86: suppress emission of zero displacements in memoryoperands
Date: Fri, 06 May 2005 16:50:00 -0000 [thread overview]
Message-ID: <20050506165033.GA19231@lucon.org> (raw)
In-Reply-To: <s27baa29.000@emea1-mh.id2.novell.com>
On Fri, May 06, 2005 at 06:33:00PM +0200, Jan Beulich wrote:
> This stripping is intentional; I'm running into this in many cases where structure offsets are generated (i.e. through a C translation), and the zero offset gets needlessly retained. The point is that you anyway can't force the assembler to everything, like use a 32-bit displacement when an 8-bit one (or even none) suffices. If that's already impossible, then adding this additional thing is no issue at all in my opinion. Jan
>
Please check out
http://people.redhat.com/drepper/tls.pdf
elf_i386_relocate_section and elf64_x86_64_relocate_section to make
sure that TLS optimization, which depends on the exact length of
the instruction, won't get affected.
I still prefer to fix compiler instead of assembler.
H.J.
next prev parent reply other threads:[~2005-05-06 16:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 16:40 Jan Beulich
2005-05-06 16:44 ` DJ Delorie
2005-05-06 16:50 ` [PATCH] x86: suppress emission of zero displacements inmemoryoperands Dave Korn
2005-05-06 16:55 ` DJ Delorie
2005-05-06 16:50 ` H. J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-09 10:29 [PATCH] x86: suppress emission of zero displacements in memoryoperands Jan Beulich
2005-05-09 14:02 ` H. J. Lu
2005-05-06 17:01 Jan Beulich
2005-05-06 12:04 [PATCH] x86: suppress emission of zero displacements in memory operands Jan Beulich
2005-05-06 14:00 ` [PATCH] x86: suppress emission of zero displacements in memoryoperands Dave Korn
2005-05-06 14:21 ` Andreas Schwab
2005-05-06 14:26 ` Dave Korn
2005-05-06 14:36 ` H. J. Lu
2005-05-06 14:39 ` Andreas Schwab
2005-05-06 14:56 ` Dave Korn
2005-05-06 15:04 ` Andreas Schwab
2005-05-06 19:35 ` Richard Henderson
2006-07-14 17:03 ` Clifford T. Matthews
2006-07-14 17:30 ` H. J. Lu
2006-07-14 17:34 ` Dave Korn
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=20050506165033.GA19231@lucon.org \
--to=hjl@lucon.org \
--cc=JBeulich@novell.com \
--cc=binutils@sources.redhat.com \
--cc=dave.korn@artimi.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).