From: rridge@csclub.uwaterloo.ca (Ross Ridge)
To: gcc@gcc.gnu.org
Subject: RE: g++ 3.4.0 cygwin, codegen SSE & alignement issues
Date: Thu, 29 Apr 2004 04:49:00 -0000 [thread overview]
Message-ID: <20040429004827.D81B6A8555@perpugilliam.csclub.uwaterloo.ca> (raw)
> Well, it's quicker to allocate a constant size stack frame than to
>dynamically calculate the alignment requirements, but only by two or
>three fairly trivial instructions. And although aligning the frame just
>once at startup and keeping it aligned by always allocating aligned-size
>stack frames, in some situations stack memory is a limited resource, and
>particularly since not all code uses vector registers, there's a lot of
>stack memory usage to be saved by not making all the stack frames bigger
>just for the sake of the very few frames for functions that actually
>use the vector regs. So I'd say it's probably one of those trade-offs
>for which there's no one 'right' answer.
I think a happy middle-way, at least for the i386 port, would be to
implement a special function attribute, say __attribute__((align_stack)),
that only dynamically aligns the stack of functions defined with the
attribute.
Ross Ridge
--
l/ // Ross Ridge -- The Great HTMU
[oo][oo] rridge@csclub.uwaterloo.ca
-()-/()/ http://www.csclub.uwaterloo.ca/u/rridge/
db //
next reply other threads:[~2004-04-29 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 4:49 Ross Ridge [this message]
2004-04-29 6:12 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 6:46 Ross Ridge
[not found] <408FCABF.2050702@ompf.org>
2004-04-28 16:56 ` Dave Korn
2004-04-28 17:04 ` Tim Prince
2004-04-28 19:17 ` Dave Korn
2004-04-28 20:42 ` Brian Ford
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=20040429004827.D81B6A8555@perpugilliam.csclub.uwaterloo.ca \
--to=rridge@csclub.uwaterloo.ca \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).