public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105182] [11/12 Regression] compiling NJOY21 causes a ICE segmentation fault: 11
Date: Fri, 08 Apr 2022 08:04:34 +0000	[thread overview]
Message-ID: <bug-105182-4-E6RnmAziN1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105182-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105182

G. Steinmetz <gscfq@t-online.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gscfq@t-online.de

--- Comment #16 from G. Steinmetz <gscfq@t-online.de> ---

Seems to be fully covered by pr103609 (gfc_sym_get_dummy_args).
(that began to give an ICE between 20200726 and 20200809)

For this case :
Status of gcc-11 changed between 20200726 (ok) and 20200809 (ICE)
too, and gcc-11 was fixed between 20211113 (ICE) and 20211211 (ok).
Primarily gcc-12 was fixed between 20211205 (ICE) and 20211212 (ok).

Last backtrace for pr105182.f90 is :

$ gfortran-12-20211205 -c pr105182.f90
f951: internal compiler error: Segmentation fault
0xf0b99f crash_signal
        ../../gcc/toplev.c:322
0x87f8f0 gfc_sym_get_dummy_args(gfc_symbol*)
        ../../gcc/fortran/symbol.c:5243
0x94ec51 doloop_contained_procedure_code
        ../../gcc/fortran/frontend-passes.c:2483
0x954519 gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int
(*)(gfc_expr**, int*, void*), void*)
        ../../gcc/fortran/frontend-passes.c:5333
0x956a32 doloop_code
        ../../gcc/fortran/frontend-passes.c:2627
0x954519 gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int
(*)(gfc_expr**, int*, void*), void*)
        ../../gcc/fortran/frontend-passes.c:5333
0x954697 gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int
(*)(gfc_expr**, int*, void*), void*)
        ../../gcc/fortran/frontend-passes.c:5669
0x95570b doloop_warn
        ../../gcc/fortran/frontend-passes.c:3059
0x955c5a gfc_run_passes(gfc_namespace*)
        ../../gcc/fortran/frontend-passes.c:156
0x856467 gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.c:17572
0x8569a5 gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.c:17551
0x8569a5 update_current_proc_array_outer_dependency
        ../../gcc/fortran/resolve.c:3182
0x856d17 resolve_call
        ../../gcc/fortran/resolve.c:3809
0x853e49 gfc_resolve_code(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.c:12150
0x856377 resolve_codes
        ../../gcc/fortran/resolve.c:17531
0x8562ae resolve_codes
        ../../gcc/fortran/resolve.c:17514
0x85643e gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.c:17566
0x83e562 gfc_parse_file()
        ../../gcc/fortran/parse.c:6792
0x88c73f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.c:216


BTW, an almost complete variation run did not yield any 
additional problem cases, only replicated the already known 
bug groups around pr103507 and pr99036.

  parent reply	other threads:[~2022-04-08  8:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 15:59 [Bug fortran/105182] New: " kermitnuc at gmail dot com
2022-04-06 17:06 ` [Bug fortran/105182] " kargl at gcc dot gnu.org
2022-04-06 20:50 ` kermitnuc at gmail dot com
2022-04-06 20:57 ` sgk at troutmask dot apl.washington.edu
2022-04-06 21:54 ` kermitnuc at gmail dot com
2022-04-06 23:38 ` sgk at troutmask dot apl.washington.edu
2022-04-07  1:09 ` kermitnuc at gmail dot com
2022-04-07  2:58 ` sgk at troutmask dot apl.washington.edu
2022-04-07  4:51 ` kargl at gcc dot gnu.org
2022-04-07  7:08 ` [Bug fortran/105182] [11/12 Regression] " rguenth at gcc dot gnu.org
2022-04-07  7:08 ` rguenth at gcc dot gnu.org
2022-04-07 19:47 ` kargl at gcc dot gnu.org
2022-04-07 21:23 ` kargl at gcc dot gnu.org
2022-04-07 21:35 ` anlauf at gcc dot gnu.org
2022-04-07 21:41 ` kargl at gcc dot gnu.org
2022-04-07 21:58 ` anlauf at gcc dot gnu.org
2022-04-07 22:35 ` sgk at troutmask dot apl.washington.edu
2022-04-08  8:04 ` gscfq@t-online.de [this message]
2022-04-08 16:04 ` kargl at gcc dot gnu.org
2022-04-10 15:43 ` kermitnuc at gmail dot com

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-105182-4-E6RnmAziN1@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).