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 c++/97268] Segfault on 11.0.0 20200930
Date: Fri, 02 Oct 2020 06:55:49 +0000	[thread overview]
Message-ID: <bug-97268-4-Oe4r3MrUsP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97268-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2020-10-02
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 10 says

t.C: In instantiation of 'BetterObject<CACHED>::BetterObject(const char*, int,
Handle&) [with bool CACHED = true]':
t.C:61:31:   required from here
t.C:53:45: error: use of deleted function 'Handle::Handle(const Handle&)'
   53 |             , BetterObjectBase(lc_, ln_, env) {}
      |                                             ^
t.C:9:5: note: declared here
    9 |     Handle(const Handle &) = delete;
      |     ^~~~~~

and GCC 11 doesn't crash for me, but you didn't tell us the exact compile
options or the target you are using.  So GCC 11 accepts the testcase for me.

  reply	other threads:[~2020-10-02  6:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  5:48 [Bug c++/97268] New: " ext-gcc at burakarslan dot com
2020-10-02  6:55 ` rguenth at gcc dot gnu.org [this message]
2020-10-02  7:01 ` [Bug c++/97268] " ext-gcc at burakarslan dot com
2020-10-02  7:03 ` ext-gcc at burakarslan dot com
2020-10-02  7:08 ` [Bug c++/97268] 11 Regression] " rguenth at gcc dot gnu.org
2020-10-02  7:16 ` [Bug c++/97268] [11 Regression] ICE in maybe_warn_pass_by_reference at gcc/tree-ssa-uninit.c:514 since r11-1763-g27aebb7d6cf14175 marxin at gcc dot gnu.org
2020-10-02 12:06 ` marxin at gcc dot gnu.org
2020-10-02 16:56 ` nathan 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-97268-4-Oe4r3MrUsP@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).