public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98130] [11 regression] placement new fails on webkit-gtk-2.28.4 since r11-4745-g58c9de46541ade79
Date: Fri, 04 Dec 2020 12:37:37 +0000 [thread overview]
Message-ID: <bug-98130-4-p1t1zs2SQU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98130-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98130
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #8)
> Oops, yes, dunno why it didn't work for me before, confirmed now that it
> works with the patch and fails without.
>
> I think we want it even for the operator delete case, I believe the C++
> standard only constraints how the replaceable operators work, not arbitrary
> user operator new/delete/new[]/delete[] operators.
I bet it's pretty similar to what we have for -fallocation-dce:
valid_new_delete_pair_p?
next prev parent reply other threads:[~2020-12-04 12:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 20:45 [Bug c++/98130] New: [11 regression] placement new fails on webkit-gtk-2.28.4 slyfox at gcc dot gnu.org
2020-12-04 6:54 ` [Bug c++/98130] [11 regression] placement new fails on webkit-gtk-2.28.4 since r11-4745-g58c9de46541ade79 marxin at gcc dot gnu.org
2020-12-04 7:19 ` rguenth at gcc dot gnu.org
2020-12-04 11:27 ` jakub at gcc dot gnu.org
2020-12-04 11:37 ` jakub at gcc dot gnu.org
2020-12-04 11:59 ` hubicka at ucw dot cz
2020-12-04 12:21 ` rguenth at gcc dot gnu.org
2020-12-04 12:25 ` rguenth at gcc dot gnu.org
2020-12-04 12:33 ` jakub at gcc dot gnu.org
2020-12-04 12:37 ` marxin at gcc dot gnu.org [this message]
2020-12-04 12:48 ` jakub at gcc dot gnu.org
2020-12-04 13:33 ` rguenth at gcc dot gnu.org
2020-12-04 18:11 ` cvs-commit at gcc dot gnu.org
2020-12-04 18:12 ` jakub at gcc dot gnu.org
2020-12-04 19:49 ` slyfox at gcc dot gnu.org
2020-12-22 19:09 ` jason at gcc dot gnu.org
2021-01-19 11:59 ` 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-98130-4-p1t1zs2SQU@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).