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/106048] New: [10/11/12/13 Regression] ICE in ubsan_encode_value, at ubsan.cc:143 / verify_gimple failed
Date: Tue, 21 Jun 2022 18:51:24 +0000	[thread overview]
Message-ID: <bug-106048-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106048
           Summary: [10/11/12/13 Regression] ICE in ubsan_encode_value, at
                    ubsan.cc:143 / verify_gimple failed
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r7, with and without -fsanitize=undefined :


$ cat z1.f90
program p
   integer :: real
   print *, real(2)
   associate (y => real+real)
      print *, y
   end associate
end


$ cat z2.f90
program p
   integer :: n
   print *, n(2)
   associate (y => n+n)
      print *, y
   end associate
end


$ gfortran-13-20220619 -c z1.f90
/tmp/cc97osCU.s: Assembler messages:
/tmp/cc97osCU.s:35: Error: junk `(intrinsic)_MOD_real' after expression


$ gfortran-13-20220619 -c z1.f90 -fsanitize=undefined
during RTL pass: expand
z1.f90:5:16:

    5 |       print *, y
      |                ^
internal compiler error: in ubsan_encode_value, at ubsan.cc:143
0xcf9ca2 ubsan_encode_value(tree_node*, ubsan_encode_value_phase)
        ../../gcc/ubsan.cc:143
0xcfe316 ubsan_build_overflow_builtin(tree_code, unsigned int, tree_node*,
tree_node*, tree_node*, tree_node**)
        ../../gcc/ubsan.cc:1562
0xa72326 expand_mul_overflow
        ../../gcc/internal-fn.cc:2270
0xa749c6 expand_UBSAN_CHECK_MUL
        ../../gcc/internal-fn.cc:2516
0x8820e7 expand_call_stmt
        ../../gcc/cfgexpand.cc:2737
0x8820e7 expand_gimple_stmt_1
        ../../gcc/cfgexpand.cc:3869
0x8820e7 expand_gimple_stmt
        ../../gcc/cfgexpand.cc:4033
0x887297 expand_gimple_basic_block
        ../../gcc/cfgexpand.cc:6085
0x889d5e execute
        ../../gcc/cfgexpand.cc:6811

---

gcc configured with --enable-checking=yes :

$ gfortran-13-20220619 -c z1.f90
z1.f90:1:9:

    1 | program p
      |         ^
Error: type mismatch in binary expression
integer(kind=4)

integer(kind=4) (*<T62d>) ()

integer(kind=4)

_1 = real * 2;
z1.f90:1:9: internal compiler error: 'verify_gimple' failed
0xed9e9d verify_gimple_in_seq(gimple*)
        ../../gcc/tree-cfg.cc:5217
0xb557b1 gimplify_body(tree_node*, bool)
        ../../gcc/gimplify.cc:16543
0xb55a55 gimplify_function_tree(tree_node*)
        ../../gcc/gimplify.cc:16659
0x964c47 cgraph_node::analyze()
        ../../gcc/cgraphunit.cc:676
0x967ef6 analyze_functions
        ../../gcc/cgraphunit.cc:1241
0x9690cd symbol_table::finalize_compilation_unit()
        ../../gcc/cgraphunit.cc:2501

             reply	other threads:[~2022-06-21 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 18:51 gscfq@t-online.de [this message]
2022-06-24 10:01 ` [Bug fortran/106048] " rguenth at gcc dot gnu.org
2022-06-27  8:54 ` marxin at gcc dot gnu.org
2022-06-28 10:49 ` jakub at gcc dot gnu.org
2022-12-02 13:21 ` jakub at gcc dot gnu.org
2023-06-02  8:55 ` [Bug fortran/106048] [10/11/12/13/14 " pault at gcc dot gnu.org
2023-06-02  8:55 ` pault 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-106048-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).