From: Eric Botcazou <botcazou@adacore.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Simon Richter <Simon.Richter@hogyros.de>,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>,
gcc@gcc.gnu.org
Subject: Re: POWER __builtin_add_overflow/__builtin_mul_overflow with u64
Date: Tue, 14 Feb 2023 10:26:14 +0100 [thread overview]
Message-ID: <1843696.tdWV9SEqCh@fomalhaut> (raw)
In-Reply-To: <Y+tFG7lMckrx7zGF@tucnak>
> rs6000 indeed doesn't implement {,u}{add,sub,mul}v4_optab for
> any mode and thus leaves it to the generic code.
https://gcc.gnu.org/pipermail/gcc-patches/2016-October/460209.html
--
Eric Botcazou
next prev parent reply other threads:[~2023-02-14 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 3:48 Simon Richter
2023-02-14 8:23 ` Jakub Jelinek
2023-02-14 9:26 ` Eric Botcazou [this message]
2023-02-15 9:43 ` Segher Boessenkool
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=1843696.tdWV9SEqCh@fomalhaut \
--to=botcazou@adacore.com \
--cc=Simon.Richter@hogyros.de \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=segher@kernel.crashing.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).