From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3168739878F5; Tue, 22 Sep 2020 16:54:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3168739878F5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1600793644; bh=Sl+QYGvvlN5yGRcFsJzsi8KY5GT4vArnOm8qYyctTH0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZNSt4gmdjVsm9MAzk9xgeNxhknO6N0oJ2HpQmMT1tVB1sPUM5d9A7CSNCi+a+DqHk hAEjREQOlji4YjhbkZGteeIRlzHy8RuUFS0got8rSyLBcFJFAf+MhU6QECUUch3jNl 05FAe9sztarDBRW20bh+MnihQCuP9JNqYbwUNezI= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/97163] Build error with -mcpu=power9 on ppc64 Date: Tue, 22 Sep 2020 16:54:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 10.2.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2020 16:54:04 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97163 --- Comment #4 from Jakub Jelinek --- Well, libcpp isn't using the standard Altivec intrinsics, but their gcc underlying implementation. Looking at clang altivec.h, I see they use vect= or keyword everywhere and not sure what exactly they map it to under the hood,= but clearly not to altivec attribute, and they have different __builtin_* calls= to implement e.g. vsx_ld and the like.=