From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 0A1EC385780E; Thu, 26 Aug 2021 13:21:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0A1EC385780E
From: "tuliom at ascii dot art.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101865] _ARCH_PWR8 is not defined when using -mcpu=power8
Date: Thu, 26 Aug 2021 13:21:45 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 11.1.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tuliom at ascii dot art.br
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-101865-4-YeW8maAmMs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-101865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-101865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2021 13:21:46 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101865

--- Comment #10 from Tulio Magno Quites Machado Filho <tuliom at ascii dot =
art.br> ---
(In reply to HaoChen Gui from comment #9)
> For this example, let's suppose that we set mcpu=3Dpower8 and mno-vsx in =
the
> command line. Thus, _ARCH_PWR8 should be defined as mcpu=3Dpower8. But if=
 the
> Power8-specific codes contain VSX codes, could the asm be executed?

These macros should only be used to indicate if a code should be generated.
In my opinion, in order to generate a VSX instruction available on POWER8, =
it
would be required to test for both _ARCH_PWR8 and __VSX__.

For tests at execution time, it's required to validate what the kernel
supports, e.g. using __builtin_cpu_supports().=