public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65147] alignment of std::atomic object is not correct Date: Fri, 20 Feb 2015 22:11:00 -0000 [thread overview] Message-ID: <bug-65147-4-6HMSGjYu4M@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65147-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65147 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- On Fri, 20 Feb 2015, alexey.lapshin at oracle dot com wrote: > According to the documentation - > https://gcc.gnu.org/wiki/Atomic/GCCMM/UnalignedPolicy alignment of atomic > object should match it`s size. > Alignment in the test case below does not match with documentation. Not in itself a bug to fail to follow preliminary plans. *But*: > This behavior also differs from gcc. Gcc aligns 8-bytes objects to 8-bytes. Differences between C and C++ atomics might be a bug - there may be intent for them to be ABI-compatible (although that didn't get implemented), unlike other aspects of the early plans you point to where intent changed over the course of implementation.
next prev parent reply other threads:[~2015-02-20 21:19 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-20 20:01 [Bug c++/65147] New: " alexey.lapshin at oracle dot com 2015-02-20 22:11 ` joseph at codesourcery dot com [this message] 2015-03-20 22:15 ` [Bug libstdc++/65147] " jason at gcc dot gnu.org 2015-03-23 18:07 ` alexey.lapshin at oracle dot com 2015-03-23 18:36 ` redi at gcc dot gnu.org 2015-03-26 19:59 ` redi at gcc dot gnu.org 2015-03-26 20:24 ` redi at gcc dot gnu.org 2015-03-27 15:58 ` alexey.lapshin at oracle dot com 2015-03-27 19:15 ` redi at gcc dot gnu.org 2015-03-28 10:29 ` redi at gcc dot gnu.org 2015-03-30 11:42 ` redi at gcc dot gnu.org 2015-04-09 11:16 ` redi at gcc dot gnu.org 2015-04-09 11:18 ` redi at gcc dot gnu.org 2015-04-10 14:46 ` alexey.lapshin at oracle dot com 2015-04-22 12:02 ` jakub at gcc dot gnu.org 2015-04-22 12:59 ` 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-65147-4-6HMSGjYu4M@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).