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++/99552] FAIL: 29_atomics/atomic/wait_notify/bool.cc (test for excess errors)
Date: Thu, 11 Mar 2021 16:08:57 +0000	[thread overview]
Message-ID: <bug-99552-4-57yEeVEqzx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99552-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99552

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That's useful to know, thanks.

The current header-based implementation is experimental and those aligned
objects will be moved into the library at some point, where we can probably
control their placement and alignment more precisely.

In the meantime, I think we want a macro in config/os/*/os_defines.h that says
whether we should try to over-align them. If we don't do it, performance will
suffer because of false sharing, but it won't affect correctness.

      parent reply	other threads:[~2021-03-11 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 14:34 [Bug libstdc++/99552] New: " danglin at gcc dot gnu.org
2021-03-11 15:08 ` [Bug libstdc++/99552] " redi at gcc dot gnu.org
2021-03-11 15:37 ` dave.anglin at bell dot net
2021-03-11 15:52 ` dave.anglin at bell dot net
2021-03-11 16:08 ` redi at gcc dot gnu.org [this message]

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-99552-4-57yEeVEqzx@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).