From: Jakub Jelinek <jakub@redhat.com>
To: Mason <slash.tmp@free.fr>
Cc: Uros Bizjak <ubizjak@gmail.com>,
gcc-help@gcc.gnu.org, Jeffrey Walton <noloader@gmail.com>,
Marc Glisse <marc.glisse@inria.fr>
Subject: Re: Use-case for _addcarryx_u64() wrapper
Date: Sat, 3 Jun 2023 13:49:49 +0200 [thread overview]
Message-ID: <ZHso3QMRyLaa38EB@tucnak> (raw)
In-Reply-To: <e48c036c-736f-6419-5016-c948c6f45759@free.fr>
On Sat, Jun 03, 2023 at 01:37:53PM +0200, Mason wrote:
> On 01/06/2023 09:42, Mason wrote:
>
> > As far as I can tell, intrinsics _addcarry_u64() and _addcarryx_u64() are
> > plain wrappers around the same __builtin_ia32_addcarryx_u64() function.
> >
> > https://github.com/gcc-mirror/gcc/blob/master/gcc/config/i386/adxintrin.h
>
> Hello Uros, Jakub,
>
> I want to report a missed-optimization bug with _addcarry_u64().
> (I can file an issue on Bugzilla, if you deem it appropriate.)
Filing this in bugzilla is the right way to go.
I think we'll need to do something about this stuff urgently on
most of the arches anyway, see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989#c56
But what your testcase shows is a separate issue, so should be
filed separately.
Thanks.
Jakub
prev parent reply other threads:[~2023-06-03 11:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 7:42 Mason
2023-06-01 8:40 ` Uros Bizjak
2023-06-02 12:45 ` Mason
2023-06-02 12:50 ` Jeffrey Walton
2023-06-03 9:10 ` Mason
2023-06-02 12:59 ` Jakub Jelinek
2023-06-02 22:53 ` Gabriel Ravier
2023-06-03 8:53 ` Mason
2023-06-03 9:09 ` Jakub Jelinek
2023-06-03 11:37 ` Mason
2023-06-03 11:49 ` Jakub Jelinek [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=ZHso3QMRyLaa38EB@tucnak \
--to=jakub@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=marc.glisse@inria.fr \
--cc=noloader@gmail.com \
--cc=slash.tmp@free.fr \
--cc=ubizjak@gmail.com \
/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).