From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 51C763851AB4; Mon, 5 Sep 2022 19:52:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 51C763851AB4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1662407566; bh=UsI9rM9IbdS8aLx00WG3trj65RY2Y+b5idTjiZuMHlM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qvNG5jGxgef1QdzLMHBPNAHnDXHg+puQcYz1JHGqqwZC+JoZpYbI3d8+SFoVtJ007 Six6KrTzozxadDttpiN8Ox+MnseXQZd/ZYrhumDyF7fBpRr969dx0K7PsjBiidY+xJ 6DomNCcCXy82Wo6inS0MEgmrdKEjlO0dFH8GFGxI= From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/106840] glibc master build failure on ppc64le-linux-gnu since r13-2212-geb4879ab905308 Date: Mon, 05 Sep 2022 19:52:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: preprocessor X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org 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: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106840 --- Comment #2 from Segher Boessenkool --- This is inside #ifdef __ASSEMBLER__ . Running assembler code (or anything = else that isn't C) through the C preprocessor is the subject of one of my "why w= ould you ever do that" rants: the assembler macro processor is strictly more cap= able already, and has much saner semantics (for assembler code).=