public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45793] [4.6 Regressions] Numerous test-suite failures
Date: Sun, 26 Sep 2010 07:43:00 -0000 [thread overview]
Message-ID: <20100926074300.VV_Q9bidMntKCkx8jwEZdjPtOjpDjLZNrmxwNTt2mts@z> (raw)
In-Reply-To: <bug-45793-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45793
Kazumoto Kojima <kkojima at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Last reconfirmed| |2010.09.25 23:16:59
date| |
CC| |kkojima at gcc dot gnu.org
Resolution|INVALID |
Ever Confirmed|0 |1
--- Comment #3 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2010-09-25 23:16:59 UTC ---
I've got similar failures on cross sh4-linux. gfortran.log says
that f951 segfaults for these tests. gdb shows that the segfault
happens at
Program received signal SIGSEGV, Segmentation fault.
0x0811130c in create_int_parameter_array (name=<value optimized out>, size=2,
value=0x8b18bb0, id=22, module=<value optimized out>,
modname=<value optimized out>)
at ../../ORIG/trunk/gcc/fortran/module.c:5345
5345 e->shape = gfc_get_shape (1);
When building f951, there was a warning
../trunk/gcc/fortran/module.c: In function 'create_int_parameter_array':
../trunk/gcc/fortran/module.c:5346: warning: 'e' may be used uninitialized in
this function
with my fedora environment. It looks that there is still something wrong.
next prev parent reply other threads:[~2010-09-25 23:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 19:57 [Bug fortran/45793] New: " jvdelisle at gcc dot gnu.org
2010-09-25 22:43 ` [Bug fortran/45793] " jvdelisle at gcc dot gnu.org
2010-09-26 2:11 ` jvdelisle at gcc dot gnu.org
2010-09-26 7:43 ` kkojima at gcc dot gnu.org [this message]
2010-09-26 10:27 ` jvdelisle at gcc dot gnu.org
2010-09-26 10:42 ` jvdelisle at gcc dot gnu.org
2010-09-26 12:31 ` jvdelisle at gcc dot gnu.org
2010-09-26 13:22 ` kkojima at gcc dot gnu.org
2010-09-26 13:44 ` burnus at gcc dot gnu.org
2010-09-26 15:17 ` jvdelisle at gcc dot gnu.org
2010-09-26 16:43 ` jvdelisle at gcc dot gnu.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=20100926074300.VV_Q9bidMntKCkx8jwEZdjPtOjpDjLZNrmxwNTt2mts@z \
--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).