public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104826] [11/12 Regression] ICE in gimple_range_global, at value-query.cc:424
Date: Tue, 08 Mar 2022 07:22:11 +0000	[thread overview]
Message-ID: <bug-104826-4-7nSgOoBspl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104826-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-03-08
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Target Milestone|---                         |11.3
           Priority|P3                          |P2
           Keywords|                            |ice-on-valid-code
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think we have a duplicate of this (but it was fixed already?!)

(gdb) p name
$1 = <ssa_name 0x7ffff651f990 2>
(gdb) p debug_tree (name)
 <ssa_name 0x7ffff651f990
    type <integer_type 0x7ffff652f738 integer(kind=8) public DI
        size <integer_cst 0x7ffff6517c00 constant 64>
        unit-size <integer_cst 0x7ffff6517c18 constant 8>
        align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff652f738 precision:64 min <integer_cst 0x7ffff6517e88
-9223372036854775808> max <integer_cst 0x7ffff6517ea0 9223372036854775807>
        pointer_to_this <pointer_type 0x7ffff6564738>>

    def_stmt 
    version:2>
$2 = void
(gdb) bt
#0  0x0000000000dd69e4 in is_a_helper<gphi*>::test<gimple> (gs=<gimple 0x0>)
    at /home/rguenther/src/gcc3/gcc/gimple.h:1243
#1  0x0000000000dd8f50 in is_a<gphi*, gimple> (p=<gimple 0x0>)
    at /home/rguenther/src/gcc3/gcc/is-a.h:232
#2  0x0000000001967e67 in gimple_range_global (
    name=<ssa_name 0x7ffff651f990 2>)
    at /home/rguenther/src/gcc3/gcc/value-query.cc:424
#3  0x00000000029eadda in ranger_cache::get_global_range (this=0x413c508, 
    r=..., name=<ssa_name 0x7ffff651f990 2>)
    at /home/rguenther/src/gcc3/gcc/gimple-range-cache.cc:923
#4  0x00000000029e778f in gimple_ranger::export_global_ranges (this=0x413c4e0)
    at /home/rguenther/src/gcc3/gcc/gimple-range.cc:474
#5  0x0000000002a40694 in pass_walloca::execute (this=0x411c290, 
    fun=0x7ffff670c000)
    at /home/rguenther/src/gcc3/gcc/gimple-ssa-warn-alloca.cc:381
#6  0x00000000013b4749 in execute_one_pass (
    pass=<opt_pass* 0x411c290 "walloca"(23)>)
    at /home/rguenther/src/gcc3/gcc/passes.cc:2637

  reply	other threads:[~2022-03-08  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 18:02 [Bug fortran/104826] New: " gscfq@t-online.de
2022-03-08  7:22 ` rguenth at gcc dot gnu.org [this message]
2022-03-08  8:28 ` [Bug fortran/104826] " jakub at gcc dot gnu.org
2022-04-21  7:51 ` rguenth at gcc dot gnu.org
2023-02-20  8:44 ` [Bug fortran/104826] [11/12/13 Regression] ICE in gimple_range_global, at value-query.cc:424 – with deferred-length character variable burnus at gcc dot gnu.org
2023-05-29 10:06 ` [Bug fortran/104826] [11/12/13/14 " jakub 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-104826-4-7nSgOoBspl@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).