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/110766] [14 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: in gimple_phi_arg_def_from_edge, at gimple.h:4699
Date: Sat, 22 Jul 2023 16:36:20 +0000	[thread overview]
Message-ID: <bug-110766-4-OsWOiKRx7B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110766-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
Reduced C++ code seems to be:

template <int _Nw> struct _Base_bitset { 
  unsigned long _M_w[_Nw];
  unsigned long &_M_getword() { return _M_w[0]; }
};
struct bitset : _Base_bitset<0> { 
  int _Unchecked_set___val;
  void set() {
    long __trans_tmp_4;
    if (_Unchecked_set___val)
      _M_getword() |= __trans_tmp_4;
  }
  void reset() {
    long __trans_tmp_5, __trans_tmp_3;
    __trans_tmp_5 = 1 << __trans_tmp_3;
    _M_getword() &= __trans_tmp_5;
  }
};
using PlayBehaviourSet = bitset;
struct CSoundFile {
  PlayBehaviourSet m_playBehaviour;
  void UpgradeModule();
};
void CSoundFile::UpgradeModule() {
  for (int i = 0; i < 5; i++) {
    m_playBehaviour.set();
    m_playBehaviour.reset();
  }
}

cvise $ ~/gcc/results/bin/gcc -c -O2 bug943.cc
during GIMPLE pass: sccp
bug943.cc: In member function ‘void CSoundFile::UpgradeModule()’:
bug943.cc:23:6: internal compiler error: in gimple_phi_arg_def_from_edge, at
gimple.h:4699
   23 | void CSoundFile::UpgradeModule() {
      |      ^~~~~~~~~~
0x123f7dc final_value_replacement_loop(loop*)
        ../../trunk.year/gcc/tree-scalar-evolution.cc:0
0x12fdfb7 (anonymous namespace)::pass_scev_cprop::execute(function*)
        ../../trunk.year/gcc/tree-ssa-loop.cc:411
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
cvise $

  parent reply	other threads:[~2023-07-22 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 12:27 [Bug tree-optimization/110766] New: " zhendong.su at inf dot ethz.ch
2023-07-21 20:39 ` [Bug tree-optimization/110766] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-21 20:40 ` pinskia at gcc dot gnu.org
2023-07-22 14:20 ` dcb314 at hotmail dot com
2023-07-22 16:36 ` dcb314 at hotmail dot com [this message]
2023-07-24  6:31 ` rguenth at gcc dot gnu.org
2023-07-24  7:50 ` cvs-commit at gcc dot gnu.org
2023-07-24  7:51 ` [Bug tree-optimization/110766] [13 " rguenth at gcc dot gnu.org
2023-07-27 10:34 ` cvs-commit at gcc dot gnu.org
2023-07-27 10:38 ` 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-110766-4-OsWOiKRx7B@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).