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 fortran/40440] [4.4/4.5 Regression] Garbage or segmentation fault in allocatable array derived type structures
Date: Mon, 15 Jun 2009 08:52:00 -0000 [thread overview]
Message-ID: <20090615085230.31255.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40440-15192@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from burnus at gcc dot gnu dot org 2009-06-15 08:52 -------
(In reply to comment #2)
> COmplete code for the test case including the module iso_varying_string
Works with: gfortran 4.3.3, ifort 11, sunf95, NAG f95 5.1 (w/o flush
statements)
Fails (abort) with gfortran 4.4.1/4.5
Valgrind shows several uninitialized accesses (gfortran 4.3.3, 4.4, and 4.5),
but no errors with NAG f95 or ifort. Interestingly, it runs through with
valgrind + gfortran 4.5, which means that it could be no regression and working
in 4.3.3 only by chance.
valgrind finds essentially the following two errors with gfortran 4.5:
Invalid read of size 1
at 0x4091FC: __iso_varying_string_MOD_char_auto (foo.f90:868)
by 0x40B73F: __syntax_rules_MOD_monitor_syntax_rules (foo.f90:3450)
by 0x40B8F5: __syntax_rules_MOD_syntax_get_rule_ptr (foo.f90:3431)
by 0x40C242: set_children.6490 (foo.f90:3410)
by 0x40C933: __syntax_rules_MOD_set_rule_contents (foo.f90:3366)
by 0x40E9E5: __syntax_rules_MOD_syntax_init_from_ifile (foo.f90:3287)
by 0x412C6E: MAIN__ (foo.f90:3472)
Use of uninitialised value of size 8
at 0x40C261: set_children.6490 (foo.f90:3410)
by 0x40C933: __syntax_rules_MOD_set_rule_contents (foo.f90:3366)
by 0x40E9E5: __syntax_rules_MOD_syntax_init_from_ifile (foo.f90:3287)
by 0x412C6E: MAIN__ (foo.f90:3472)
by 0x412D09: main (foo.f90:3462)
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Known to fail| |4.4.1 4.5.0
Known to work| |4.3.3
Summary|[4.5.0 Regression] Garbage |[4.4/4.5 Regression] Garbage
|or segmentation fault in |or segmentation fault in
|allocatable array derived |allocatable array derived
|type structures |type structures
Target Milestone|--- |4.4.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40440
next prev parent reply other threads:[~2009-06-15 8:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 21:50 [Bug fortran/40440] New: [4.5.0 " juergen dot reuter at desy dot de
2009-06-14 22:14 ` [Bug fortran/40440] " kargl at gcc dot gnu dot org
2009-06-14 22:19 ` juergen dot reuter at desy dot de
2009-06-15 8:52 ` burnus at gcc dot gnu dot org [this message]
2009-06-15 12:17 ` [Bug fortran/40440] [4.4/4.5 " burnus at gcc dot gnu dot org
2009-06-15 13:09 ` [Bug fortran/40440] Automatic deallocation component of DT function return value burnus at gcc dot gnu dot org
2009-06-18 9:44 ` pault at gcc dot gnu dot org
2009-06-18 13:33 ` juergen dot reuter at desy dot de
2009-06-18 14:45 ` burnus at gcc dot gnu dot org
2009-06-18 15:18 ` burnus at gcc dot gnu dot org
2009-06-18 20:52 ` pault at gcc dot gnu dot org
2009-06-18 21:15 ` burnus at gcc dot gnu dot org
2009-06-19 0:20 ` pault at gcc dot gnu dot org
2009-06-19 21:58 ` pault at gcc dot gnu dot org
2009-07-09 19:28 ` pault at gcc dot gnu dot org
2009-07-09 19:29 ` pault at gcc dot gnu dot org
2009-10-11 12:20 ` pault at gcc dot gnu dot org
2009-10-11 12:26 ` pault 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=20090615085230.31255.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).