public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/31915] Failure with unf_io_convert_3.f90
Date: Mon, 14 May 2007 06:51:00 -0000 [thread overview]
Message-ID: <20070514065104.12143.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31915-10743@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from burnus at gcc dot gnu dot org 2007-05-14 07:51 -------
Same here, native and little_endian work, but big_endian/swap produces the
wrong number (here: NaN). It also works if one does not use real(10) but
real(8)
If I run the created program through valgrind:
==26772== Syscall param write(buf) points to uninitialised byte(s)
==26772== at 0x55FB550: write (in /lib64/libc-2.5.so)
==26772== by 0x4EBB760: do_write (unix.c:300)
==26772== by 0x4EBB7DD: fd_flush (unix.c:359)
==26772== by 0x4EB01DF: _gfortran_st_backspace (file_pos.c:226)
==26772== by 0x400B36: MAIN__ (pr31915.f90:9)
==26772== by 0x400E4D: main (fmain.c:18)
==26772== Address 0x4051781 is 153 bytes inside a block of size 8,344 alloc'd
==26772== at 0x4C22D06: malloc (in
/usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==26772== by 0x4E3DCB8: _gfortrani_get_mem (memory.c:53)
==26772== by 0x4EBB9C9: fd_to_stream (unix.c:1012)
==26772== by 0x4EBC72F: _gfortrani_open_external (unix.c:1289)
==26772== by 0x4EB56F7: _gfortrani_new_unit (open.c:374)
==26772== by 0x4EB5E59: _gfortran_st_open (open.c:531)
==26772== by 0x400AAB: MAIN__ (pr31915.f90:7)
==26772== by 0x400E4D: main (fmain.c:18)
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |wrong-code
Known to fail| |4.3.0 4.2.0 4.1.2
Last reconfirmed|0000-00-00 00:00:00 |2007-05-14 07:51:03
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31915
next prev parent reply other threads:[~2007-05-14 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 0:13 [Bug libfortran/31915] New: " jvdelisle at gcc dot gnu dot org
2007-05-14 6:51 ` burnus at gcc dot gnu dot org [this message]
2007-05-14 20:20 ` [Bug libfortran/31915] " patchapp at dberlin dot org
2007-05-15 10:17 ` burnus at gcc dot gnu dot org
2007-05-15 10:29 ` [Bug libfortran/31915] [4.2 only] " burnus at gcc dot gnu dot org
2007-05-22 14:28 ` [Bug libfortran/31915] " burnus at gcc dot gnu dot org
2007-05-22 14:28 ` [Bug libfortran/31915] [4.2 only] " burnus 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=20070514065104.12143.qmail@sourceware.org \
--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).