public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/94906] memory corruption in std::pmr::memory_buffer_resource
Date: Fri, 01 May 2020 18:46:36 +0000 [thread overview]
Message-ID: <bug-94906-4-Q038uUdRCA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94906-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94906
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Better would be:
size_t __size = (((size_t)1) << __ch->_M_size);
As long could be 32bits (windows)
next prev parent reply other threads:[~2020-05-01 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 17:42 [Bug libstdc++/94906] New: " arnaud02 at users dot sourceforge.net
2020-05-01 18:19 ` [Bug libstdc++/94906] " redi at gcc dot gnu.org
2020-05-01 18:46 ` pinskia at gcc dot gnu.org [this message]
2020-05-04 21:48 ` [Bug libstdc++/94906] memory corruption in std::pmr::monotonic_buffer_resource cvs-commit at gcc dot gnu.org
2020-05-05 16:18 ` redi at gcc dot gnu.org
2020-05-12 8:55 ` cvs-commit at gcc dot gnu.org
2020-05-12 19:41 ` cvs-commit at gcc dot gnu.org
2020-05-12 19:42 ` 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-94906-4-Q038uUdRCA@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).