From: "Gerrit P. Haase" <gp@familiehaase.de>
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: Thu, 27 May 2004 22:11:00 -0000 [thread overview]
Message-ID: <277403406.20040527205859@familiehaase.de> (raw)
In-Reply-To: <OFFB435626.E532FF68-ONC1256EA0.003FCC45-C1256EA0.00405F9A@philips.com>
Hallo mathias,
> GCC 3.3.1 has a problem when printing multiple long double variables using
> printf and the -m128bit-long-double compile option on a Pentium-based
> machine.
Seems to be a bug in gcc, for bug reporting instructions, please see:
http://gcc.gnu.org/bugs.html.
> compile the code below with
> gcc -m128bit-long-double test.c
> and with
> gcc test.c
> The later will print stuff correctly in both printf statements, whereas
> the former will print fine only as long as the printf statement contains a
> single long double variable only, but will issue garbage when printing
> more than one long double variable in the same printf statement.
> #include <stdlib.h>
> #include <stdio.h>
> #include <string.h>
> #include <math.h>
> int
> main( int argc, char *argv[] )
> {
> long double first_long_double_variable = 5.6;
> long double second_long_double_variable = 9.3;
> printf ("here comes a long double %Lg\n", first_long_double_variable);
> printf ("here come TWO long doubles %Lg %Lg\n",
> first_long_double_variable, second_long_double_variable);
> }
> Installation Info as copied from cygcheck.out:
Please don't send cygcheck output inline an email, send it as
attachment.
Gerrit
--
=^..^=
--
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-27 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 15:17 mathias.wagner
2004-05-27 22:11 ` Gerrit P. Haase [this message]
2004-05-27 23:30 ` Brian Ford
2004-05-28 11:19 mathias.wagner
2004-05-28 16:20 ` 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=277403406.20040527205859@familiehaase.de \
--to=gp@familiehaase.de \
--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).