From: Falk Hueffner <hueffner@informatik.uni-tuebingen.de>
To: "Yang Ye" <leafyoung@yahoo.com>
Cc: <gcc-help@gcc.gnu.org>, "'wei lei'" <wrag201@hotmail.com>
Subject: Re: gcc optimization and stack allocation.
Date: Thu, 17 Jun 2004 09:25:00 -0000 [thread overview]
Message-ID: <871xkepmcs.fsf@informatik.uni-tuebingen.de> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebvFnS24L0iO8cmxZFTW3AKBAAAQAAAAu6Ol5DnR20m1cQ5WFOEHJQEAAAAA@yahoo.com> (Yang Ye's message of "Thu, 17 Jun 2004 16:47:44 +0800")
"Yang Ye" <leafyoung@yahoo.com> writes:
> Do you have any idea on this scenario: When gcc(3.3.3) allocating
> space for local varibles, e.g. a statement like 'char buf[256];',
> the allocated buffers in stack always come with some space filled in
> at the end. If choose higher optimization level, let's say gcc -O6,
> the spaced filled at the end are smaller. I searched quite a lot
> documents, cannot find the official reason.
There is no "official reason". This depends on various gcc internals
in a hard to predict way. The real question is: why do you care?
--
Falk
prev parent reply other threads:[~2004-06-17 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 8:49 Yang Ye
2004-06-17 9:25 ` Falk Hueffner [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=871xkepmcs.fsf@informatik.uni-tuebingen.de \
--to=hueffner@informatik.uni-tuebingen.de \
--cc=gcc-help@gcc.gnu.org \
--cc=leafyoung@yahoo.com \
--cc=wrag201@hotmail.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).