From: Brian Ford <ford@vss.fsi.com>
To: mathias.wagner@philips.com
Cc: cygwin@cygwin.com
Subject: Re: GCC 3.3.1 problem with printf %Lg %Lg and -m128bit-long-double compile option
Date: Fri, 28 May 2004 16:20:00 -0000 [thread overview]
Message-ID: <Pine.CYG.4.58.0405281045070.1584@fordpc.vss.fsi.com> (raw)
In-Reply-To: <OF4B525423.BF84D3AE-ONC1256EA2.00331803-C1256EA2.003360F4@philips.com>
On Fri, 28 May 2004, mathias.wagner wrote:
> To: "Gerrit @ cygwin" <cygwin at cygwin dot com>
http://www.cygwin.com/acronyms/#PCYMTNQREAIYR
> Meanwhile I have had some help from another colleague here at Philips and
> he found out that the -m96bit-long-double compile option works fine.
My understanding is that this is the default ie. no switch requried.
> Note that 96 bit is what a long double takes. This makes sense in
> conjunction with what Brian said: The alignment of the parameters handed
> over to a function is changed when using -m128bit-long-double, and hence
> all functions affected must be recompiled - so presumably cygwin itself.
Yes.
> There was no particular reason for using -m128bit-long-double other than
> that I have always used it, and I will switch to -m96bit-long-double.
It might have performed better with respect to caching, but YMMV.
> But perhaps one could insert somewhere in gcc a warning when using such
> a combination of compile options. I know it is in the documentation
> somewhere, but compiler warnings are much more visible... :-)
You could take this up on the gcc list if it is still important to you,
but I suspect they would frown on the idea. The philosophy goes
something like this:
You had to read the documentation to discover that this switch existed.
It is not a compiler warnings job to advise you to read the documentation
more carefully. It would also penalize those that did read the docs, so
they would want a way to turn off the gratuitous warning with via another
switch or attribute.
Can you see why this isn't a good idea?
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2004-05-28 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 11:19 mathias.wagner
2004-05-28 16:20 ` Brian Ford [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 15:17 mathias.wagner
2004-05-27 22:11 ` Gerrit P. Haase
2004-05-27 23:30 ` 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=Pine.CYG.4.58.0405281045070.1584@fordpc.vss.fsi.com \
--to=ford@vss.fsi.com \
--cc=cygwin@cygwin.com \
--cc=mathias.wagner@philips.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).