public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sdirkse at gams dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37472]  New: bad output on default-format write of double in common block with -m64 flag i
Date: Thu, 11 Sep 2008 00:57:00 -0000	[thread overview]
Message-ID: <bug-37472-14147@http.gcc.gnu.org/bugzilla/> (raw)

If I do write (6,*) 'x=', x   for a double, I get lots of stars for doubles in
a common block when I do a 64-bit compile.  The output is OK for 32-bit or for
doubles not in common.  Here's some output, I'll try attaching the test case
too.

sigvm:/export/home/distrib/lang/f90$make && ./bug 
gfortran -c -m64 bug.f
gfortran -o bug -m64 ./bug.o -ldl
 x =    1001.0000000000000     
 r =  ********************     
sigvm:/export/home/distrib/lang/f90$gfortran -c -m32 bug.f
sigvm:/export/home/distrib/lang/f90$gfortran  -o bug32 -m32 bug.o -ldl
sigvm:/export/home/distrib/lang/f90$./bug32
 x =    1001.0000000000000     
 r =   1000.00000000000000


-- 
           Summary: bad output on default-format write of double in common
                    block with -m64 flag i
           Product: gcc
           Version: 4.3.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sdirkse at gams dot com
  GCC host triplet: i386-pc-solaris2.10


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37472


             reply	other threads:[~2008-09-11  0:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11  0:57 sdirkse at gams dot com [this message]
2008-09-11  0:58 ` [Bug fortran/37472] " sdirkse at gams dot com
2008-09-11  6:03 ` burnus at gcc dot gnu dot org
2008-09-11 11:38 ` dominiq at lps dot ens dot fr
2008-09-11 14:29 ` burnus at gcc dot gnu dot org
2008-09-12  3:54 ` jvdelisle at gcc dot gnu dot org
2008-10-11 15:55 ` jvdelisle at gcc dot gnu dot org
2008-10-11 16:01 ` jvdelisle at gcc dot gnu dot org
2008-11-17  5:04 ` jvdelisle at gcc dot gnu dot org
2008-11-21  4:32 ` jvdelisle at gcc dot gnu dot org
2008-11-21  4:38 ` jvdelisle at gcc dot gnu dot org
2008-11-21  4:40 ` jvdelisle at gcc dot gnu dot org
2008-12-13 15:31 ` jvdelisle at gcc dot gnu dot org
2008-12-21  5:30 ` jvdelisle at gcc dot gnu dot org
2008-12-21 13:36 ` dominiq at lps dot ens dot fr
2008-12-22 14:56 ` jvdelisle at gcc dot gnu dot org
2008-12-22 16:30 ` dominiq at lps dot ens dot fr
2008-12-22 20:38 ` sdirkse at gams dot com
2008-12-22 21:04 ` kargl at gcc dot gnu dot org
2008-12-22 21:29 ` jvdelisle at gcc dot gnu dot org
2009-05-02 23:29 ` jvdelisle at gcc dot gnu dot org
2010-04-16 23:03 ` [Bug fortran/37472] bad output on default-format write of double in common block with -m64 jvdelisle at gcc dot gnu dot org

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=bug-37472-14147@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).