From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: Compilers
Date: Sat, 29 May 2004 12:58:00 +0100 [thread overview]
Message-ID: <40B87AC8.1010307@cowlark.com> (raw)
In-Reply-To: <40B87734.6050109@gmx.de>
Mark Junker wrote:
[...]
>> A -fno-frame-pointer option would be nice, too. I guess that most people
>> wouldn't want them on ELKS, and it will make code smaller and use less
>> stack space.
>
> This can (sometimes) produce smaller code.
The main advantage is that you free up a register that can be used for
other things. On the register-starved x86 family this is a huge benefit.
I really don't know why people use a frame pointer anyway. Given that
the i86 can do arbitrary relative stack addressing there's no real need
for it. It makes debugging marginally easier, but then the debug
information should provide all the necessary data to find the stack
frame from any point in the code...
(I work for a company that produces embedded operating systems, with our
own cross-platform compiler architecture. The PowerPC has 32
general-purpose registers. Guess how many the 386 has? *Five*. That
leads to interesting scalability issues in our register allocation code...)
--
dg@cowlark.com --- http://www.cowlark.com
My other account has a real signature.
next prev parent reply other threads:[~2004-05-29 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 10:42 Compilers David Given
2004-05-28 14:44 ` Compilers sandeep
2004-05-28 14:47 ` Compilers Eduardo Pereira Habkost
2004-05-29 11:42 ` Compilers Mark Junker
2004-05-29 11:58 ` David Given [this message]
2004-05-29 12:32 ` Compilers Mark Junker
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=40B87AC8.1010307@cowlark.com \
--to=dg@cowlark.com \
--cc=linux-8086@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