From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) by sourceware.org (Postfix) with ESMTPS id 64567386182E for ; Mon, 26 Oct 2020 23:09:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 64567386182E Received: by mail-pg1-x52e.google.com with SMTP id n16so6899453pgv.13 for ; Mon, 26 Oct 2020 16:09:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=N0heOcnmFW7mOxpmkUdoIl5bJCxLd1oS1uHU1mcRqw0=; b=B8Oe6RY0wzz0bcePFHPlaFjyiSkNqzDh4exAZQHcvG+7TEgtBjGgW0JB6rLJbTDH6d FHpR4TYn6X5gtQqHpHP4Z6NCFKB6EBjhkidyz+LP52/7b6jvPU6x+geVBc4Kcvs+ir2v 5BFhX0HEoZUbJF5A+WPFwe1L6uMX36H6OLklMT0d08uHuvCoDdwEc7eDZ/o2I2H2GGUr zRSKH++KAQ2iCKZXefRFuSJfN6+xurrAU71sO4NdxcZLA30wo5ekyShA/LzB9QPbh/rx w/EUoH0mpSMgYkowBNyzzO1FlJH0yCxOMIBSGgGuHShHDcXhy8z2ku4TWWxgOY5JvpyR 02kw== X-Gm-Message-State: AOAM5326cfdl6Wmx0RBP4qlYpWlm4vMY3JfsQjrAq4NdFBhp983DAxhd FNBdXl8orTgra0BNsz5/o3ENLxSYy91QaA== X-Google-Smtp-Source: ABdhPJySFk6OHfJqZ3BjYVEHVtuW696w5U05zTzzOvssBE54KEDcKEard6JN+tUhuZ5AXpPz6ids1g== X-Received: by 2002:a63:4f02:: with SMTP id d2mr18927462pgb.46.1603753773118; Mon, 26 Oct 2020 16:09:33 -0700 (PDT) Received: from bubble.grove.modra.org (158.106.96.58.static.exetel.com.au. [58.96.106.158]) by smtp.gmail.com with ESMTPSA id q11sm11464955pgm.79.2020.10.26.16.09.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Oct 2020 16:09:32 -0700 (PDT) Received: by bubble.grove.modra.org (Postfix, from userid 1000) id 84D1A81508; Tue, 27 Oct 2020 09:39:28 +1030 (ACDT) Date: Tue, 27 Oct 2020 09:39:28 +1030 From: Alan Modra To: Segher Boessenkool Cc: gcc-patches@gcc.gnu.org, David Edelsohn Subject: Re: [RS6000] Tests that use int128_t and -m32 Message-ID: <20201026230928.GK15956@bubble.grove.modra.org> References: <20201025112001.GC15956@bubble.grove.modra.org> <20201026123349.GU2672@gate.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201026123349.GU2672@gate.crashing.org> User-Agent: Mutt/1.9.4 (2018-02-28) X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_NUMSUBJECT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2020 23:09:35 -0000 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