public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109741] alignas(64) in libstdc++-v3/src/c++11/shared_ptr.cc Date: Thu, 04 May 2023 20:18:03 +0000 [thread overview] Message-ID: <bug-109741-4-n77XNf7B0e@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109741-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109741 --- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> --- Libstdc++ doesn't work on "every possible architecture", just the ones GCC supports. I am 100% confident that alignas(void*) is wrong for every architecture GCC supports, and I'm pretty confident alignof(max_align_t) is wrong for all of them too (since that's either 8 or 16). I'm also confident that 64 is a good choice for nearly all targets GCC supports. 64 is much less wrong than any of your suggestions, and is right for most GCC targets.
next prev parent reply other threads:[~2023-05-04 20:18 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-04 17:30 [Bug libstdc++/109741] New: " janezz55 at gmail dot com 2023-05-04 17:38 ` [Bug libstdc++/109741] " janezz55 at gmail dot com 2023-05-04 17:39 ` pinskia at gcc dot gnu.org 2023-05-04 17:40 ` pinskia at gcc dot gnu.org 2023-05-04 17:42 ` pinskia at gcc dot gnu.org 2023-05-04 17:58 ` janezz55 at gmail dot com 2023-05-04 18:02 ` pinskia at gcc dot gnu.org 2023-05-04 18:05 ` pinskia at gcc dot gnu.org 2023-05-04 18:10 ` janezz55 at gmail dot com 2023-05-04 18:14 ` jakub at gcc dot gnu.org 2023-05-04 18:17 ` redi at gcc dot gnu.org 2023-05-04 18:19 ` redi at gcc dot gnu.org 2023-05-04 18:31 ` jakub at gcc dot gnu.org 2023-05-04 19:30 ` janezz55 at gmail dot com 2023-05-04 20:18 ` redi at gcc dot gnu.org [this message] 2023-05-16 17:31 ` cvs-commit at gcc dot gnu.org 2023-05-16 17:33 ` redi at gcc dot gnu.org 2023-05-16 17:33 ` redi at gcc dot gnu.org 2023-06-29 23:01 ` cvs-commit 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-109741-4-n77XNf7B0e@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).