From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Etienne Lorrain <etienne_lorrain@yahoo.fr>,
vgoyal@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Re : Re : Re : Re : [PATCH] Compressed ia32 ELF file generation for loading by Gujin 1/3
Date: Tue, 06 Feb 2007 19:48:43 -0700 [thread overview]
Message-ID: <m14ppyr8c4.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <45C9246F.9050300@zytor.com> (H. Peter Anvin's message of "Tue, 06 Feb 2007 16:59:27 -0800")
"H. Peter Anvin" <hpa@zytor.com> writes:
> Etienne Lorrain wrote:
>> H. Peter Anvin wrote:
>>> I've long wished that someone would do a proper 16-bit x86 port of gcc;
>>
>>> however, the .code16gcc is usually good enough, although it produces code
>>> which is a lot bigger than it needs to be.
>>
>> It is only that much bigger if you compare to 16 bits integer compilers,
>> but once you deal with 32 bits integers in real mode you have one extra byte
>> out of the two - which is still better than dealing with dx:ax.
>>
>> Last time I compiled (long time ago) some piece of code with and without
>> .code16gcc it was approx 15% bigger - approx what you get when optimising.
>>
>
> That's not a valid comparison, because you're using 32-bit registers to hold
> 16-bit pointers, and then sticking 67 prefixes on completely unnecessarily.
Regardless if the size is good enough we can use it :)
For romcc I had a 3x code bloat over had crafted assembler, because I
had no memory and had to inline every single function call because I
didn't have someplace to put a return register. So I have the
scenario with the most code bloat. I win!
Eric
prev parent reply other threads:[~2007-02-07 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 22:19 Re : Re : Re : Re : [PATCH] Compressed ia32 ELF file generation for loading by Gujin 1/3 Etienne Lorrain
2007-02-07 0:59 ` H. Peter Anvin
2007-02-07 2:48 ` Eric W. Biederman [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=m14ppyr8c4.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=etienne_lorrain@yahoo.fr \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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