public inbox for
 help / color / mirror / Atom feed
From: Eric Botcazou <>
To: Jonathan Wakely <>
Subject: Re: [committed] libstdc++: Fix test for std::atomic_ref
Date: Mon, 31 Oct 2022 18:03:21 +0100	[thread overview]
Message-ID: <8176183.NyiUUSuA9g@fomalhaut> (raw)
In-Reply-To: <>

> I suppose we could use memcmp on the as variable itself, to inspect
> the actual stored padding rather than the returned copy of it.

Yes, that's probably the only safe stance when optimization is enabled.

Eric Botcazou

  reply	other threads:[~2022-10-31 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 20:21 Jonathan Wakely
2022-10-31 15:34 ` Eric Botcazou
2022-10-31 15:37   ` Jonathan Wakely
2022-10-31 17:03     ` Eric Botcazou [this message]
2022-10-31 17:05       ` Jonathan Wakely
2022-11-01 13:53         ` Jonathan Wakely
2022-11-01 15:26           ` Eric Botcazou
2023-09-01 15:21   ` Jonathan Wakely
2023-09-01 18:14     ` Eric Botcazou

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8176183.NyiUUSuA9g@fomalhaut \ \ \ \ \

* 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).