public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110461] [14 regression] ICE when building openh264 with new vector_type checking
Date: Thu, 29 Jun 2023 07:43:15 +0000	[thread overview]
Message-ID: <bug-110461-4-NFYtN6aNQT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110461-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from David Binderman <dcb314 at hotmail dot com> ---
Here is a test case which seems to demonstrate the problem:

$ /home/dcb38/gcc/results/bin/gcc -c -w -O1 -march=znver1 bug935.c
during GIMPLE pass: fre
bug935.c: In function ‘func_63’:
bug935.c:5:6: internal compiler error: tree check: expected none of
vector_type,
 have vector_type in gimple_simplify_144, at gimple-match-3.cc:1027
    5 | void func_63() {
      |      ^~~~~~~
0x11656f9 tree_not_check_failed(tree_node const*, char const*, int, char
const*,
 ...)
        ../../trunk.year/gcc/tree.cc:8936
0x1dc7c8b gimple_simplify_144(gimple_match_op*, gimple**, tree_node*
(*)(tree_no
de*), tree_node*, tree_node**, tree_code)
        /home/dcb38/gcc/working/gcc/gimple-match-3.cc:1027
0x1db5e1a gimple_simplify_BIT_AND_EXPR(gimple_match_op*, gimple**, tree_node*
(*
)(tree_node*), code_helper, tree_node*, tree_node*, tree_node*)
        /home/dcb38/gcc/working/gcc/gimple-match-2.cc:16999

  parent reply	other threads:[~2023-06-29  7:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 16:46 [Bug tree-optimization/110461] New: " sjames at gcc dot gnu.org
2023-06-28 16:51 ` [Bug tree-optimization/110461] " pinskia at gcc dot gnu.org
2023-06-28 16:51 ` pinskia at gcc dot gnu.org
2023-06-28 17:29 ` sjames at gcc dot gnu.org
2023-06-28 17:39 ` pinskia at gcc dot gnu.org
2023-06-28 17:44 ` pinskia at gcc dot gnu.org
2023-06-28 17:51 ` pinskia at gcc dot gnu.org
2023-06-28 19:07 ` pinskia at gcc dot gnu.org
2023-06-28 22:16 ` dcb314 at hotmail dot com
2023-06-28 22:19 ` pinskia at gcc dot gnu.org
2023-06-28 22:20 ` seurer at gcc dot gnu.org
2023-06-29  4:03 ` pinskia at gcc dot gnu.org
2023-06-29  7:13 ` rguenth at gcc dot gnu.org
2023-06-29  7:13 ` rguenth at gcc dot gnu.org
2023-06-29  7:43 ` dcb314 at hotmail dot com [this message]
2023-06-29  8:14 ` cvs-commit at gcc dot gnu.org
2023-06-29  8:14 ` rguenth 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-110461-4-NFYtN6aNQT@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).