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/106126] [12 Regression] tree check fail in useless_type_conversion_p, at gimple-expr.cc:87 since r13-1184-g57424087e82db140
Date: Thu, 30 Jun 2022 19:52:11 +0000	[thread overview]
Message-ID: <bug-106126-4-Xfe3XXIekR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106126-4@http.gcc.gnu.org/bugzilla/>

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

David Binderman <dcb314 at hotmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcb314 at hotmail dot com

--- Comment #15 from David Binderman <dcb314 at hotmail dot com> ---
Created attachment 53230
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53230&action=edit
gzipped C++ source code


Please find attached an additional C++ test case. -O3 required this time:

$ /home/dcb/gcc/results/bin/g++ -c -O3 q1.ii
during GIMPLE pass: iftoswitch
../src/common/uri.cpp: In member function ‘const char*
wxURI::ParseUserInfo(const char*)’:
../src/common/uri.cpp:1086:1: internal compiler error: Segmentation fault
0x10ba099 crash_signal(int)
        ../../trunk.git/gcc/toplev.cc:322
0x134244a gimple_nop_p(gimple const*)
        ../../trunk.git/gcc/gimple.h:6747
0x134244a verify_use(basic_block_def*, basic_block_def*, ssa_use_operand_t*,
gimple*, bool, bitmap_head*)
        ../../trunk.git/gcc/tree-ssa.cc:880

  parent reply	other threads:[~2022-06-30 19:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 17:46 [Bug c/106126] New: tree check fail in useless_type_conversion_p, at gimple-expr.cc:87 dcb314 at hotmail dot com
2022-06-28 17:51 ` [Bug tree-optimization/106126] " dcb314 at hotmail dot com
2022-06-28 17:59 ` dcb314 at hotmail dot com
2022-06-28 20:06 ` dcb314 at hotmail dot com
2022-06-28 20:46 ` dcb314 at hotmail dot com
2022-06-28 21:33 ` dcb314 at hotmail dot com
2022-06-29  9:47 ` rguenth at gcc dot gnu.org
2022-06-29 11:45 ` dcb314 at hotmail dot com
2022-06-29 11:53 ` dcb314 at hotmail dot com
2022-06-29 11:59 ` [Bug tree-optimization/106126] [12 Regression] tree check fail in useless_type_conversion_p, at gimple-expr.cc:87 since r13-1184-g57424087e82db140 marxin at gcc dot gnu.org
2022-06-29 12:00 ` marxin at gcc dot gnu.org
2022-06-30  2:21 ` luoxhu at gcc dot gnu.org
2022-06-30  2:37 ` luoxhu at gcc dot gnu.org
2022-06-30  3:34 ` luoxhu at gcc dot gnu.org
2022-06-30 13:03 ` marxin at gcc dot gnu.org
2022-06-30 19:52 ` dcb314 at hotmail dot com [this message]
2022-07-01  6:48 ` cvs-commit at gcc dot gnu.org
2022-07-01  6:48 ` [Bug tree-optimization/106126] [13 " marxin at gcc dot gnu.org
2022-07-01  6:54 ` marxin at gcc dot gnu.org
2022-07-01  7:16 ` dcb314 at hotmail dot com
2022-07-01 17:48 ` dcb314 at hotmail dot com
2022-07-04 11:33 ` marxin 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-106126-4-Xfe3XXIekR@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).