From: DJ Delorie <dj@redhat.com>
To: rridge@csclub.uwaterloo.ca
Cc: gcc@gcc.gnu.org
Subject: Re: g++ 3.4.0 cygwin, codegen SSE & alignement issues
Date: Thu, 29 Apr 2004 06:12:00 -0000 [thread overview]
Message-ID: <200404290055.i3T0tee7013240@greed.delorie.com> (raw)
In-Reply-To: <20040429004827.D81B6A8555@perpugilliam.csclub.uwaterloo.ca> (rridge@csclub.uwaterloo.ca)
> 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.
The existing align-stack code is target independent. Why not create a
target independent attribute? The x86 isn't the only target that has
this problem, just the only one with an OS that makes it so obvious
(although Windows runs on various embedded chips also).
next prev parent reply other threads:[~2004-04-29 0:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 4:49 Ross Ridge
2004-04-29 6:12 ` DJ Delorie [this message]
-- 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=200404290055.i3T0tee7013240@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=rridge@csclub.uwaterloo.ca \
/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).