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 tree-optimization/109005] [13 Regression] ICE during GIMPLE pass: ifcvt
Date: Tue, 07 Mar 2023 07:25:48 +0000 [thread overview]
Message-ID: <bug-109005-4-8Ao64Np5ZV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109005-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109005
--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #10)
> with a debug build on darwin19:
> #2 0x000000010249e5a5 in make_ssa_name_fn (fn=0x11104b170, var=0x10771d1f8,
> stmt=0x0, version=0) at /src-local/gcc-master/gcc/tree-ssanames.cc:357
> 357 gcc_assert (VAR_P (var)
> (gdb) p debug_tree(var)
> <array_type 0x10771d1f8
> type <integer_type 0x10711c348 character public unsigned QI
> size <integer_cst 0x107102d38 constant 8>
> unit-size <integer_cst 0x107102d50 constant 1>
> align:8 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
> 0x10711c348 precision:8 min <integer_cst 0x107102d68 0> max <integer_cst
> 0x107102d08 255>
> pointer_to_this <pointer_type 0x107180c78>>
> QI size <integer_cst 0x107102d38 8> unit-size <integer_cst 0x107102d50 1>
^^
That proves my suspicion in comment#5 and the suggested fix should work fine.
next prev parent reply other threads:[~2023-03-07 7:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 11:51 [Bug ada/109005] New: " simon at pushface dot org
2023-03-03 11:53 ` [Bug ada/109005] " simon at pushface dot org
2023-03-03 11:59 ` simon at pushface dot org
2023-03-03 12:30 ` rguenth at gcc dot gnu.org
2023-03-03 12:53 ` simon at pushface dot org
2023-03-03 12:58 ` rguenth at gcc dot gnu.org
2023-03-06 10:56 ` [Bug tree-optimization/109005] " iains at gcc dot gnu.org
2023-03-06 11:11 ` avieira at gcc dot gnu.org
2023-03-06 11:12 ` avieira at gcc dot gnu.org
2023-03-06 11:14 ` iains at gcc dot gnu.org
2023-03-06 11:38 ` iains at gcc dot gnu.org
2023-03-06 21:17 ` simon at pushface dot org
2023-03-06 21:19 ` simon at pushface dot org
2023-03-06 21:19 ` simon at pushface dot org
2023-03-07 7:25 ` rguenth at gcc dot gnu.org [this message]
2023-03-07 10:10 ` avieira at gcc dot gnu.org
2023-03-07 10:44 ` dkm at gcc dot gnu.org
2023-03-07 10:48 ` dkm at gcc dot gnu.org
2023-03-07 10:59 ` iains at gcc dot gnu.org
2023-03-07 13:23 ` simon at pushface dot org
2023-03-07 14:09 ` avieira at gcc dot gnu.org
2023-03-07 14:22 ` avieira at gcc dot gnu.org
2023-03-07 14:25 ` rguenther at suse dot de
2023-03-07 16:31 ` ebotcazou at gcc dot gnu.org
2023-03-14 9:53 ` cvs-commit at gcc dot gnu.org
2023-03-14 10:01 ` rguenth at gcc dot gnu.org
2023-03-14 10:43 ` cvs-commit 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-109005-4-8Ao64Np5ZV@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).