From: DJ Delorie <dj@redhat.com>
To: dave.korn@artimi.com
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] x86: suppress emission of zero displacements inmemoryoperands
Date: Fri, 06 May 2005 16:55:00 -0000 [thread overview]
Message-ID: <200505061650.j46Gog1n014555@greed.delorie.com> (raw)
In-Reply-To: <SERRANOpvqnJNeO925B00000271@SERRANO.CAM.ARTIMI.COM> (dave.korn@artimi.com)
> Oh well, it seems a shame from the
> future-proofing-clean-design-and-maintainability point of view
Go back to the "self modifying code" part. At that point, you've
already blown most of the benefits of maintainable code ;-)
> to have to hard code opcode values as hex constants in your program
> when you have a handy assembler right there that could do the work
> for you.....
There was a program to do that job, an "optimizing assembler", but
Mel refused to use it.
"You never know where it's going to put things", he explained, "so
you'd have to use separate constants".
next prev parent reply other threads:[~2005-05-06 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 16:40 [PATCH] x86: suppress emission of zero displacements in memoryoperands 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 [this message]
2005-05-06 16:50 ` [PATCH] x86: suppress emission of zero displacements in memoryoperands H. J. Lu
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=200505061650.j46Gog1n014555@greed.delorie.com \
--to=dj@redhat.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).