From: Satish Vasudeva <satish.vasudeva@cohesity.com>
To: Xi Ruoyao <xry111@mengyan1223.wang>
Cc: Florian Weimer <fweimer@redhat.com>,
Stefan Ring <stefanrin@gmail.com>,
Xi Ruoyao via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Libatomic 16B
Date: Fri, 25 Feb 2022 09:05:12 -0800 [thread overview]
Message-ID: <CABp-VvJ3jK1Nxc9x6tDu2cgeBcpzUCQJLD2ms8Ko4NSSQVHj1w@mail.gmail.com> (raw)
In-Reply-To: <313b0e6eca1846dd5e994fd4c9f5d77d000247a0.camel@mengyan1223.wang>
Thanks for a quick action on this.
I see that a patch has been posted.
I am new to this, can you please clarify what is the build option for new
and older Intel CPUs?
Satish
On Fri, Feb 25, 2022 at 6:25 AM Xi Ruoyao <xry111@mengyan1223.wang> wrote:
> On Fri, 2022-02-25 at 15:01 +0100, Florian Weimer wrote:
>
> > > It seems an addition in Dec 2021 revision:
> > > https://cdrdv2.intel.com/v1/dl/getContent/671294
> > >
> > > Create an issue in bugzilla then?
> >
> > Yes please. I should have read the whole thread first. 8-)
>
> Opened as https://gcc.gnu.org/PR104688
> --
> Xi Ruoyao <xry111@mengyan1223.wang>
> School of Aerospace Science and Technology, Xidian University
>
next prev parent reply other threads:[~2022-02-25 17:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 16:42 Satish Vasudeva
2022-02-24 16:42 ` Satish Vasudeva
2022-02-25 13:53 ` Florian Weimer
2022-02-24 19:09 ` Xi Ruoyao
2022-02-24 19:35 ` Satish Vasudeva
2022-02-24 20:05 ` Xi Ruoyao
2022-02-24 20:13 ` Segher Boessenkool
2022-02-24 20:38 ` Satish Vasudeva
2022-02-25 8:35 ` Stefan Ring
2022-02-25 8:48 ` Xi Ruoyao
2022-02-25 14:01 ` Florian Weimer
2022-02-25 14:10 ` Alexander Monakov
2022-02-25 14:16 ` Xi Ruoyao
2022-02-25 14:25 ` Xi Ruoyao
2022-02-25 17:05 ` Satish Vasudeva [this message]
2022-02-25 17:16 ` Xi Ruoyao
2022-02-25 17:25 ` Satish Vasudeva
2022-03-02 0:16 ` Satish Vasudeva
2022-03-02 5:55 ` Florian Weimer
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=CABp-VvJ3jK1Nxc9x6tDu2cgeBcpzUCQJLD2ms8Ko4NSSQVHj1w@mail.gmail.com \
--to=satish.vasudeva@cohesity.com \
--cc=fweimer@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=stefanrin@gmail.com \
--cc=xry111@mengyan1223.wang \
/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).