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/95107] New: [10/11 Regression] ICE in hash_operand, at fold-const.c:3768
Date: Wed, 13 May 2020 16:22:55 +0000	[thread overview]
Message-ID: <bug-95107-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95107
           Summary: [10/11 Regression] ICE in hash_operand, at
                    fold-const.c:3768
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Changed between 20191110 and 20191117, with -fno-automatic at -O2+ :


$ cat z1.f90
program p
   type t
      real, pointer :: a => null()
   end type
   type t2
      type(t) :: b(1)
   end type
   type(t2) :: x
   associate (y => x%b)
   end associate
end


$ gfortran-9 -c z1.f90 -fno-automatic -O2
$
$ gfortran-11-20200510 -c z1.f90 -fno-automatic -O2
during IPA pass: icf
z1.f90:11:0:

   11 | end
      |
internal compiler error: in hash_operand, at fold-const.c:3768
0x8dfc2a operand_compare::hash_operand(tree_node const*, inchash::hash&,
unsigned int)
        ../../gcc/fold-const.c:3768
0x8e038c operand_compare::hash_operand(tree_node const*, inchash::hash&,
unsigned int)
        ../../gcc/fold-const.c:3858
0x8dffa2 operand_compare::hash_operand(tree_node const*, inchash::hash&,
unsigned int)
        ../../gcc/fold-const.c:3685
0x142c58f ipa_icf::sem_variable::init(ipa_icf_gimple::func_checker*)
        ../../gcc/ipa-icf.c:1909
0x14340ce ipa_icf::sem_variable::parse(varpool_node*, bitmap_obstack*,
ipa_icf_gimple::func_checker*)
        ../../gcc/ipa-icf.c:1889
0x143897d ipa_icf::sem_item_optimizer::parse_funcs_and_vars()
        ../../gcc/ipa-icf.c:2457
0xaf61ec execute_ipa_summary_passes(ipa_opt_pass_d*)
        ../../gcc/passes.c:2191
0x7fca29 ipa_passes
        ../../gcc/cgraphunit.c:2642
0x7fca29 symbol_table::compile()
        ../../gcc/cgraphunit.c:2752
0x7fe806 symbol_table::compile()
        ../../gcc/cgraphunit.c:3002
0x7fe806 symbol_table::finalize_compilation_unit()
        ../../gcc/cgraphunit.c:2999

             reply	other threads:[~2020-05-13 16:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 16:22 gscfq@t-online.de [this message]
2020-05-14  6:16 ` [Bug fortran/95107] " rguenth at gcc dot gnu.org
2020-05-14  7:47 ` marxin at gcc dot gnu.org
2020-05-14 14:34 ` [Bug fortran/95107] " gscfq@t-online.de
2020-07-23  6:51 ` rguenth at gcc dot gnu.org
2020-10-23  4:39 ` egallager at gcc dot gnu.org
2020-10-23  4:42 ` egallager at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-12-20 19:43 ` pinskia at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2022-07-01 20:20 ` anlauf at gcc dot gnu.org
2023-02-06 20:12 ` anlauf at gcc dot gnu.org
2023-02-07 18:22 ` cvs-commit at gcc dot gnu.org
2023-02-08 20:19 ` cvs-commit at gcc dot gnu.org
2023-02-10 19:30 ` cvs-commit at gcc dot gnu.org
2023-02-11 18:16 ` cvs-commit at gcc dot gnu.org
2023-02-11 18:20 ` anlauf 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-95107-4@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).