public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at pci dot uzh.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45827] [4.6 Regression] ice in create_int_parameter_array
Date: Wed, 29 Sep 2010 12:44:00 -0000	[thread overview]
Message-ID: <20100929124400.ULv4FY0aADfmKD3RxzFC3pR8XTfa2h841Qmjb7pVKOg@z> (raw)
In-Reply-To: <bug-45827-4@http.gcc.gnu.org/bugzilla/>

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

Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org
      Known to work|                            |4.5.2
   Target Milestone|---                         |4.6.0
            Summary|mio_component_ref():        |[4.6 Regression] ice in
                   |Component not found when    |create_int_parameter_array
                   |mixing f90 and f03 in large |
                   |projects                    |
      Known to fail|                            |4.6.0

--- Comment #2 from Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> 2010-09-29 08:57:40 UTC ---
Program received signal SIGSEGV, Segmentation fault.
0x0000000000504fee in create_int_parameter_array (name=<value optimized out>,
size=2, value=0x144e150, modname=<value optimized out>,
    module=INTMOD_ISO_FORTRAN_ENV, id=22) at
/data03/vondele/gcc_trunk/gcc/gcc/fortran/module.c:5345
5345      e->shape = gfc_get_shape (1);
(gdb) bt
#0  0x0000000000504fee in create_int_parameter_array (name=<value optimized
out>, size=2, value=0x144e150, modname=<value optimized out>,
    module=INTMOD_ISO_FORTRAN_ENV, id=22) at
/data03/vondele/gcc_trunk/gcc/gcc/fortran/module.c:5345
#1  0x0000000000505709 in use_iso_fortran_env_module () at
/data03/vondele/gcc_trunk/gcc/gcc/fortran/iso-fortran-env.def:97
#2  0x000000000050b27d in gfc_use_module () at
/data03/vondele/gcc_trunk/gcc/gcc/fortran/module.c:5541
#3  0x0000000000510905 in accept_statement (st=20866384) at
/data03/vondele/gcc_trunk/gcc/gcc/fortran/parse.c:1574
#4  0x00000000005136a0 in parse_spec (st=ST_USE) at
/data03/vondele/gcc_trunk/gcc/gcc/fortran/parse.c:2588
#5  0x0000000000514de6 in parse_progunit (st=20866384) at
/data03/vondele/gcc_trunk/gcc/gcc/fortran/parse.c:3922
#6  0x0000000000516035 in gfc_parse_file () at
/data03/vondele/gcc_trunk/gcc/gcc/fortran/parse.c:4357
#7  0x000000000054fb8d in gfc_be_parse_file (set_yydebug=<value optimized out>)
at /data03/vondele/gcc_trunk/gcc/gcc/fortran/f95-lang.c:242
#8  0x00000000008667cd in toplev_main (argc=14, argv=0x7fff8331e858) at
/data03/vondele/gcc_trunk/gcc/gcc/toplev.c:955
#9  0x00007f771ead8436 in __libc_start_main () from /lib64/libc.so.6
#10 0x00000000004ab1b9 in _start ()


  parent reply	other threads:[~2010-09-29  8:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 11:49 [Bug fortran/45827] New: mio_component_ref(): Component not found when mixing f90 and f03 in large projects boschmann at tp1 dot physik.uni-siegen.de
2010-09-29 12:37 ` [Bug fortran/45827] " Joost.VandeVondele at pci dot uzh.ch
2010-09-29 12:44 ` Joost.VandeVondele at pci dot uzh.ch [this message]
2010-09-29 12:49 ` [Bug fortran/45827] [4.6 Regression] ice in create_int_parameter_array burnus at gcc dot gnu.org
2010-09-29 12:54 ` Joost.VandeVondele at pci dot uzh.ch
2010-09-29 13:02 ` mikael at gcc dot gnu.org
2010-09-29 13:18 ` Joost.VandeVondele at pci dot uzh.ch
2010-09-29 14:22 ` [Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects mikael at gcc dot gnu.org
2010-09-29 14:30 ` mikael at gcc dot gnu.org
2010-09-29 14:30 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-29 14:59 ` mikael at gcc dot gnu.org
2010-09-30 10:19 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-30 10:44 ` burnus at gcc dot gnu.org
2010-09-30 17:47 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-30 18:39 ` burnus at gcc dot gnu.org
2010-10-01  6:52 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-01  7:57 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-01  8:13 ` burnus at gcc dot gnu.org
2010-10-01 14:39 ` jvdelisle at gcc dot gnu.org
     [not found] ` <20101001143948.D63711C0008C@msfrf2419.sfr.fr>
2010-10-01 15:17   ` Mikael Morin
2010-10-01 17:42 ` jvdelisle at gcc dot gnu.org
2010-10-21 12:28 ` janus at gcc dot gnu.org
2010-10-21 14:04 ` burnus at gcc dot gnu.org
2010-10-24 10:17 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-24 11:10 ` burnus at gcc dot gnu.org
2010-10-24 11:56 ` mikael at gcc dot gnu.org
2010-10-24 12:02 ` mikael at gcc dot gnu.org
2010-10-24 15:15 ` jvdelisle at gcc dot gnu.org
2010-10-24 15:48 ` mikael at gcc dot gnu.org
2010-10-24 18:57 ` jvdelisle at gcc dot gnu.org
2010-10-24 19:59 ` mikael at gcc dot gnu.org
2010-10-26 15:27 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-27  9:35 ` boschmann at tp1 dot physik.uni-siegen.de
2010-12-27  2:23 ` dfranke at gcc dot gnu.org
2010-12-27 14:22 ` [Bug fortran/45827] [4.6 Regression] mio_component_ref(): Component not found janus at gcc dot gnu.org
2010-12-27 14:27 ` dfranke at gcc dot gnu.org
2010-12-27 15:37 ` [Bug fortran/45827] [4.6 Regression] [OOP] " janus at gcc dot gnu.org
2010-12-27 22:18 ` dfranke at gcc dot gnu.org
2010-12-28  8:15 ` janus at gcc dot gnu.org
2010-12-28 12:23 ` dfranke at gcc dot gnu.org
2010-12-28 13:19 ` janus at gcc dot gnu.org
2010-12-28 17:27 ` dfranke at gcc dot gnu.org
2010-12-28 18:53 ` janus at gcc dot gnu.org
2010-12-28 21:22 ` janus at gcc dot gnu.org
2010-12-31 11:21 ` jakub at gcc dot gnu.org
2011-01-02 21:28 ` janus at gcc dot gnu.org
2011-01-03 12:56 ` boschmann at tp1 dot physik.uni-siegen.de
2011-01-03 13:14 ` janus 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=20100929124400.ULv4FY0aADfmKD3RxzFC3pR8XTfa2h841Qmjb7pVKOg@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).