public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113228] [14 Regression] ICE: recalculate_side_effects, at gimplify.cc:3347
Date: Thu, 04 Jan 2024 03:28:05 +0000	[thread overview]
Message-ID: <bug-113228-4-EchSvadhcX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113228-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
```
#6  0x0000000000d4594f in force_gimple_operand_gsi (gsi=0x7fffffffd3c0,
expr=0x7ffff79fe6e0, simple_p=true, var=0x0, before=true, m=GSI_SAME_STMT) at
../../gcc/gimplify-me.cc:141
141       return force_gimple_operand_gsi_1 (gsi, expr,
(gdb) p expr
$1 = (tree) 0x7ffff79fe6e0
(gdb) p debug_tree(expr)
 <ne_expr 0x7ffff79fe6e0
    type <boolean_type 0x7ffff7822b28 _Bool public unsigned QI
        size <integer_cst 0x7ffff7824048 constant 8>
        unit-size <integer_cst 0x7ffff7824060 constant 1>
        align:8 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff7822b28 precision:1 min <integer_cst 0x7ffff78242a0 0> max <integer_cst
0x7ffff78242d0 1>>

    arg:0 <ssa_name 0x7ffff79de510
        type <integer_type 0x7ffff78225e8 int sizes-gimplified public SI
            size <integer_cst 0x7ffff7824198 constant 32>
            unit-size <integer_cst 0x7ffff78241b0 constant 4>
            align:32 warn_if_not_align:0 symtab:0 alias-set 1 canonical-type
0x7ffff78225e8 precision:32 min <integer_cst 0x7ffff7824150 -2147483648> max
<integer_cst 0x7ffff7824168 2147483647>
            pointer_to_this <pointer_type 0x7ffff782ab28>>
        visited var <var_decl 0x7ffff79da480 k$0>
        def_stmt k$0_17 = PHI <_23(4), 0(3)>
        version:17
        ptr-info 0x7ffff79ed390>
    arg:1 <integer_cst 0x7ffff78242e8 type <integer_type 0x7ffff78225e8 int>
constant 0>
    t.c:15:21 start: t.c:15:16 finish: t.c:15:24>
$2 = void
(gdb) p debug_generic_expr(expr)
k$0_17 != 0

```

Exactly what I had expected. and yes it is exposed by that ...

  parent reply	other threads:[~2024-01-04  3:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04  2:42 [Bug middle-end/113228] New: " patrick at rivosinc dot com
2024-01-04  2:43 ` [Bug middle-end/113228] " patrick at rivosinc dot com
2024-01-04  2:51 ` pinskia at gcc dot gnu.org
2024-01-04  2:59 ` pinskia at gcc dot gnu.org
2024-01-04  3:02 ` pinskia at gcc dot gnu.org
2024-01-04  3:05 ` pinskia at gcc dot gnu.org
2024-01-04  3:28 ` pinskia at gcc dot gnu.org [this message]
2024-01-04  4:19 ` pinskia at gcc dot gnu.org
2024-01-04  5:48 ` pinskia at gcc dot gnu.org
2024-01-04 16:24 ` patrick at rivosinc dot com
2024-01-04 16:28 ` pinskia at gcc dot gnu.org
2024-01-04 16:33 ` patrick at rivosinc dot com
2024-01-05 11:31 ` [Bug middle-end/113228] [14 Regression] ICE: recalculate_side_effects, at gimplify.cc:3347 since r14-6420 jakub at gcc dot gnu.org
2024-01-05 12:06 ` jakub at gcc dot gnu.org
2024-01-05 12:38 ` jakub at gcc dot gnu.org
2024-01-05 22:29 ` pinskia at gcc dot gnu.org
2024-01-08 13:00 ` cvs-commit at gcc dot gnu.org
2024-01-08 13:01 ` 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-113228-4-EchSvadhcX@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).