public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/94295] use __builtin_operator_new and __builtin_operator_delete when available
Date: Tue, 20 Jul 2021 19:31:38 +0000 [thread overview]
Message-ID: <bug-94295-4-Cn5D72rrmI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94295-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94295
--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Richard Smith from comment #4)
> Yep, looks like GCC miscompiles direct calls to operator new / operator
> delete since that patch landed: https://godbolt.org/z/dK99Rz
Note that this is true only of GCC 10.x.
next prev parent reply other threads:[~2021-07-20 19:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 23:16 [Bug libstdc++/94295] New: " richard-gccbugzilla at metafoo dot co.uk
2020-03-24 7:04 ` [Bug libstdc++/94295] " glisse at gcc dot gnu.org
2020-03-24 20:26 ` richard-gccbugzilla at metafoo dot co.uk
2020-03-24 20:44 ` pinskia at gcc dot gnu.org
2020-03-24 21:04 ` richard-gccbugzilla at metafoo dot co.uk
2020-03-24 21:34 ` glisse at gcc dot gnu.org
2020-03-24 21:58 ` richard-gccbugzilla at metafoo dot co.uk
2020-03-26 20:08 ` glisse at gcc dot gnu.org
2021-07-19 16:06 ` redi at gcc dot gnu.org
2021-07-20 18:58 ` richard-gccbugzilla at metafoo dot co.uk
2021-07-20 19:00 ` redi at gcc dot gnu.org
2021-07-20 19:31 ` jason at gcc dot gnu.org [this message]
2021-07-20 19:44 ` redi at gcc dot gnu.org
2021-07-22 13:43 ` cvs-commit at gcc dot gnu.org
2021-07-22 13:44 ` redi 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-94295-4-Cn5D72rrmI@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).