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 c++/101219] New: ice in perform_or_defer_access_check
Date: Sat, 26 Jun 2021 08:57:35 +0000	[thread overview]
Message-ID: <bug-101219-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101219
           Summary: ice in perform_or_defer_access_check
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 51061
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51061&action=edit
gzipped C++ source code

For the attached C++ code, recent gcc trunk with flag -Wall does this:

/home/dcb/gcc/results.20210626/bin/g++
mednafen/pce_fast/psg.cpp: In member function ‘void
PCEFast_PSG::RunChannel(int, int32)’:
mednafen/pce_fast/psg.cpp:367:50: internal compiler error: Segmentation fault
0xfd9219 crash_signal(int)
        ../../trunk.git/gcc/toplev.c:327
0x912bc8 perform_or_defer_access_check(tree_node*, tree_node*, tree_node*, int,
access_failure_info*)
        ../../trunk.git/gcc/cp/semantics.c:490

Code compiled fine with git hash 7dcf139a2b8e1c53, dated two days ago,
and goes wrong with 607c558804f70af2, dated yesterday.

             reply	other threads:[~2021-06-26  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-26  8:57 dcb314 at hotmail dot com [this message]
2021-06-26  9:01 ` [Bug c++/101219] " dcb314 at hotmail dot com
2021-06-28  7:25 ` [Bug c++/101219] [12 Regression] ice in perform_or_defer_access_check since r12-1804-g65870e75616ee435 marxin at gcc dot gnu.org
2021-06-28 20:00 ` msebor at gcc dot gnu.org
2021-07-19 21:26 ` slyfox at gcc dot gnu.org
2021-07-19 21:47 ` slyfox at gcc dot gnu.org
2021-07-20 23:16 ` slyfox at gcc dot gnu.org
2021-07-21  0:06 ` msebor at gcc dot gnu.org
2021-07-22 23:20 ` slyfox at gcc dot gnu.org
2021-08-12 18:44 ` cvs-commit at gcc dot gnu.org
2021-08-12 18:46 ` slyfox at gcc dot gnu.org
2021-11-03 18:53 ` ppalka 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-101219-4@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).