public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53691] [4.7/4.8 Regression] ICE in LAPACK 3.4.1 cgbrfsx.f
Date: Fri, 15 Jun 2012 20:51:00 -0000 [thread overview]
Message-ID: <bug-53691-4-gurAeU0kS5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53691-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53691
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-06-15
Summary|ICE in LAPACK 3.4.1 |[4.7/4.8 Regression] ICE in
|cgbrfsx.f |LAPACK 3.4.1 cgbrfsx.f
Ever Confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-06-15 20:50:56 UTC ---
Confirmed with only -Wall.
r176696 is OK,
r177649 gives the segmentation fault.
The backtrace for trunk is
#0 gfc_calculate_transfer_sizes (source=0x142275aa0, mold=0x142276350,
size=0x142276110, source_size=0x7fff5fbfce80, result_size=0x7fff5fbfce88,
result_length_p=0x0) at /opt/mp/include/gmp.h:1745
#1 0x000000010000fa59 in gfc_check_transfer (source=0x142275aa0,
mold=0x142276350, size=0x142276110) at ../../work/gcc/fortran/check.c:4070
#2 0x000000010003a405 in check_specific (specific=0x142829e28,
expr=0x1422761d0, error_flag=0) at ../../work/gcc/fortran/intrinsic.c:3916
#3 0x0000000100046f67 in gfc_intrinsic_func_interface (expr=0x1422761d0,
error_flag=0) at ../../work/gcc/fortran/intrinsic.c:4132
#4 0x00000001000863fa in gfc_resolve_expr (e=<value optimized out>) at
../../work/gcc/fortran/resolve.c:2335
#5 0x0000000100086d39 in resolve_actual_arglist (arg=<value optimized out>,
ptype=<value optimized out>, no_formal_args=<value optimized out>)
at ../../work/gcc/fortran/resolve.c:1774
#6 0x00000001000874e3 in resolve_call (c=<value optimized out>) at
../../work/gcc/fortran/resolve.c:3691
#7 0x000000010008d66e in resolve_code (code=<value optimized out>, ns=<value
optimized out>) at ../../work/gcc/fortran/resolve.c:9533
#8 0x000000010008d1ec in gfc_resolve_blocks (b=<value optimized out>,
ns=<value optimized out>) at ../../work/gcc/fortran/resolve.c:9103
#9 0x000000010008d366 in resolve_code (code=<value optimized out>, ns=<value
optimized out>) at ../../work/gcc/fortran/resolve.c:9372
#10 0x000000010008d1ec in gfc_resolve_blocks (b=<value optimized out>,
ns=<value optimized out>) at ../../work/gcc/fortran/resolve.c:9103
#11 0x000000010008d366 in resolve_code (code=<value optimized out>, ns=<value
optimized out>) at ../../work/gcc/fortran/resolve.c:9372
#12 0x000000010008fc84 in resolve_codes (ns=<value optimized out>) at
../../work/gcc/fortran/resolve.c:14044
#13 0x000000010007f868 in gfc_resolve (ns=<value optimized out>) at
../../work/gcc/fortran/resolve.c:14071
#14 0x000000010007514b in gfc_parse_file () at
../../work/gcc/fortran/parse.c:4387
#15 0x00000001000b4216 in gfc_be_parse_file () at
../../work/gcc/fortran/f95-lang.c:191
#16 0x000000010072ada1 in toplev_main (argc=3, argv=0x7fff5fbfd750) at
../../work/gcc/toplev.c:550
#17 0x00000001000018c4 in start ()
next prev parent reply other threads:[~2012-06-15 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 19:49 [Bug fortran/53691] New: " foldy at rmki dot kfki.hu
2012-06-15 20:51 ` dominiq at lps dot ens.fr [this message]
2012-06-15 21:24 ` [Bug fortran/53691] [4.7/4.8 Regression] " dominiq at lps dot ens.fr
2012-06-16 6:15 ` burnus at gcc dot gnu.org
2012-06-16 6:16 ` [Bug fortran/53691] [4.7/4.8 Regression] ICE with -Wsurprising " burnus at gcc dot gnu.org
2012-06-17 19:31 ` burnus at gcc dot gnu.org
2012-06-22 10:28 ` burnus at gcc dot gnu.org
2012-06-22 10:29 ` burnus 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=bug-53691-4-gurAeU0kS5@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).