public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <botcazou@adacore.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [committed] libstdc++: Fix compare_exchange_padding.cc test for std::atomic_ref
Date: Tue, 01 Nov 2022 16:26:55 +0100	[thread overview]
Message-ID: <5617130.DvuYhMxLoT@fomalhaut> (raw)
In-Reply-To: <CACb0b4kRt=rjcKzFym8DZbHkZ1T5we8MiTQf6UMqgHWb5VWw1A@mail.gmail.com>

> Do those loads still get scalarized at -O0?

Presumably not at the GIMPLE level, but possibly at the RTL level.

-- 
Eric Botcazou



  reply	other threads:[~2022-11-01 15:26 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
2022-10-31 17:05       ` Jonathan Wakely
2022-11-01 13:53         ` Jonathan Wakely
2022-11-01 15:26           ` Eric Botcazou [this message]
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:
  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=5617130.DvuYhMxLoT@fomalhaut \
    --to=botcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@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).