public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/77691] [10/11/12/13 regression] experimental/memory_resource/resource_adaptor.cc FAILs Date: Thu, 12 Jan 2023 20:59:34 +0000 [thread overview] Message-ID: <bug-77691-4-qe1zDoOwmD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-77691-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77691 --- Comment #57 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:f629f63d2d9d7ad2c43f8e451f0f6e32b5f4d06a commit r13-5127-gf629f63d2d9d7ad2c43f8e451f0f6e32b5f4d06a Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Jan 12 10:58:13 2023 +0000 libstdc++: Extend max_align_t special case to 64-bit HP-UX [PR77691] GCC's std::max_align_t doesn't agree with the system malloc on HP-UX, so generalize the current hack for Solaris to apply to that target too. libstdc++-v3/ChangeLog: PR libstdc++/77691 * include/experimental/memory_resource (_GLIBCXX_MAX_ALIGN_MATCHES_MALLOC): Define. (do_allocate, do_deallocate): Check it. * testsuite/experimental/memory_resource/new_delete_resource.cc: Relax expected behaviour for 64-bit hppa-hp-hpux11.11.
next prev parent reply other threads:[~2023-01-12 20:59 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-77691-4@http.gcc.gnu.org/bugzilla/> 2020-05-13 7:51 ` [Bug libstdc++/77691] [8/9/10/11 " cvs-commit at gcc dot gnu.org 2020-05-26 10:15 ` cvs-commit at gcc dot gnu.org 2020-10-31 21:16 ` redi at gcc dot gnu.org 2021-02-17 16:30 ` danglin at gcc dot gnu.org 2021-02-17 16:46 ` redi at gcc dot gnu.org 2021-02-17 16:58 ` dave.anglin at bell dot net 2021-03-25 15:13 ` seurer at gcc dot gnu.org 2021-05-14 9:48 ` [Bug libstdc++/77691] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:08 ` rguenth at gcc dot gnu.org 2022-05-27 9:36 ` [Bug libstdc++/77691] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:32 ` jakub at gcc dot gnu.org 2023-01-05 21:26 ` danglin at gcc dot gnu.org 2023-01-08 23:10 ` danglin at gcc dot gnu.org 2023-01-09 11:20 ` redi at gcc dot gnu.org 2023-01-09 22:14 ` dave.anglin at bell dot net 2023-01-12 20:59 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-07 10:31 ` [Bug libstdc++/77691] [11/12/13/14 " 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-77691-4-qe1zDoOwmD@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: linkBe 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).