From: Brian Ford <ford@vss.fsi.com>
To: Tim Prince <tprince@computer.org>
Cc: Dave Korn <dk@artimi.com>, cygwin@cygwin.com, gcc@gcc.gnu.org
Subject: RE: g++ 3.4.0 cygwin, codegen SSE & alignement issues
Date: Wed, 28 Apr 2004 20:42:00 -0000 [thread overview]
Message-ID: <Pine.CYG.4.58.0404281254020.5560@fordpc.vss.fsi.com> (raw)
In-Reply-To: <6.0.1.1.0.20040428085945.01f20a90@imap.myrealbox.com>
On Wed, 28 Apr 2004, Tim Prince wrote:
> At 08:51 AM 4/28/2004, Dave Korn wrote:
>
> > > From: cygwin-owner On Behalf Of tbp
> > > Sent: 28 April 2004 16:16
> >
> >[ Now x-posted to gcc list, since it's seemingly a gcc issue rather than a
> >cygwin environment issue.
It's an interoperability issue.
> > I'd recommend doing that in the startup code in gcc's crt0.s myself.
That won't help for threads. See:
http://www.cygwin.com/ml/cygwin/2004-04/msg01134.html
> > The real question is, is the compiler generating code that guarantees
> > the stack stays aligned, so you can do that just once at startup? It
> > certainly ought to.
It is supposed to, given the call back and new thread caveats.
> As Dave said, this is more of a gcc than a cygwin issue,
For threads, it happens to be easiest to fix this in Cygwin.
> gcc made a decision, which is different from commercial compilers,
and the ABI.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...
next prev parent reply other threads:[~2004-04-28 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-04-29 4:49 Ross Ridge
2004-04-29 6:12 ` DJ Delorie
2004-04-29 6:46 Ross Ridge
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=Pine.CYG.4.58.0404281254020.5560@fordpc.vss.fsi.com \
--to=ford@vss.fsi.com \
--cc=cygwin@cygwin.com \
--cc=dk@artimi.com \
--cc=gcc@gcc.gnu.org \
--cc=tprince@computer.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).