From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30593 invoked by alias); 16 Nov 2019 11:45:50 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 30581 invoked by uid 89); 16 Nov 2019 11:45:50 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1386, HX-Received:Sat, interest X-HELO: mail-il1-f175.google.com Received: from mail-il1-f175.google.com (HELO mail-il1-f175.google.com) (209.85.166.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 16 Nov 2019 11:45:48 +0000 Received: by mail-il1-f175.google.com with SMTP id o18so11581548ils.12 for ; Sat, 16 Nov 2019 03:45:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=ZBO4+siU5eBWr+9Xw7VtGcwOwYaf9g0sG/zGkpW6Tko=; b=SqK5+qWjiVIj6ero1fG/eg2XAhQnCcGJL4NmB6sPZC+yYX8yYCfEBrEfa2y5Bi6p+/ 58GHLo0zUfklMj/I/pgSQhwoJM9diqxxcaJZ1mBPg1zVgA3KvRBS+8nP1KcnxWqHU8HK B3JuPMfYPoneQ4sHSix20PVPGQY+VUksKeYmVTNIQ3koY5N3vsFXvIXqGyO1zWX+MYDx HQvuuND3TW/xnjgbJjaMncFcskoexh5ZLzAUJfz9FDRWyt5SyYzK7dcYLe5aj2swXkI4 rjQ9j5STHAR89SLiaoeG0rjkbh3QvJXGlF/JbWED/5PuNa7KPPN54q0LUkUKIWJ7iH0v nXxg== MIME-Version: 1.0 References: <20191116112543.GY16031@gate.crashing.org> In-Reply-To: <20191116112543.GY16031@gate.crashing.org> Reply-To: noloader@gmail.com From: Jeffrey Walton Date: Sat, 16 Nov 2019 11:45:00 -0000 Message-ID: Subject: Re: GCC 7 on ppc64le does not recognize vec_xl_be? To: Segher Boessenkool Cc: gcc-help Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00046.txt.bz2 On Sat, Nov 16, 2019 at 6:25 AM Segher Boessenkool wrote: > > Hi Jeffrey, > > On Fri, Nov 15, 2019 at 08:05:57PM -0500, Jeffrey Walton wrote: > > g++ -DNDEBUG -g2 -O3 -mcpu=3Dpower9 -maltivec -c ppc_power9.cpp > > You forgot -Wall -Wextra, or at the very least -Wall. It probably will > help you find this problem., too. OK, thanks. I have a comprehensive test script that does things like -Wall -Wextra. It takes 4 to 6 hours to run. It is not suitable for Travis, though. GCC135 is Power9, but it only has GCC 4.8 and at12 compilers. The at12 compiler does not warn of anything of interest with elevated warnings. Just the standard unknown pragmas due to some OMP code paths. Do you know where to find a Power9 machine with GCC 7? > -g2 is the default, and -maltivec is implied by -mcpu=3Dpower9. > > Why do you disable assertions (-DNDEBUG)? > > > ppc_simd.h: In function =E2=80=98uint32x4_p VecLoadBE(const byte*)= =E2=80=99: > > ppc_simd.h:466:24: error: =E2=80=98vec_xl_be=E2=80=99 was not decla= red in this scope > > return (uint32x4_p)vec_xl_be(0, CONST_V8_CAST(src)); > > You didn't #include in this scope, or you have undefined > __VSX__, or undefined something else; it is impossible for us to tell. Yeah, I can't get a terminal so I can't do things like g++ -dM -E on Travis to see what is going on. Jeff