public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [RS6000] Tests that use int128_t and -m32
Date: Tue, 27 Oct 2020 09:39:28 +1030	[thread overview]
Message-ID: <20201026230928.GK15956@bubble.grove.modra.org> (raw)
In-Reply-To: <20201026123349.GU2672@gate.crashing.org>

On Mon, Oct 26, 2020 at 07:33:49AM -0500, Segher Boessenkool wrote:
> On Sun, Oct 25, 2020 at 09:50:01PM +1030, Alan Modra wrote:
> > All these tests fail with -m32 due to lack of int128 support,
> 
> Is there any good reason __int128 is not enabled for rs6000 -m32, btw?

Lack of addti3 and subti3 perhaps?

> > in some
> > cases with what I thought was not the best error message.  For example
> > vsx_mask-move-runnable.c:34:3: error: unknown type name 'vector'
> > is misleading.  The problem isn't "vector" but "vector __uint128_t".
> 
> Ouch, yes.  Do you see a simple way to fix that?

I haven't looked.  The only reason I commented on the error was in the
hope that someone who knows gcc intimately enough to fix this without
much effort would do so.  :-)

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2020-10-26 23:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 11:20 Alan Modra
2020-10-25 14:43 ` David Edelsohn
2020-10-26 12:04   ` Alan Modra
2020-10-26 12:35     ` Segher Boessenkool
2020-10-26 12:33 ` Segher Boessenkool
2020-10-26 23:09   ` Alan Modra [this message]
2020-10-27  0:57     ` [RS6000] Separate dg-require-effective-target options Alan Modra

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=20201026230928.GK15956@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).