From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from arjuna.pair.com (arjuna.pair.com [209.68.5.131]) by sourceware.org (Postfix) with ESMTPS id A81DB38344F9 for ; Wed, 1 Jun 2022 22:00:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A81DB38344F9 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=bitrange.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=bitrange.com Received: by arjuna.pair.com (Postfix, from userid 3006) id 233FB8A59C; Wed, 1 Jun 2022 18:00:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by arjuna.pair.com (Postfix) with ESMTP id 22B318A591; Wed, 1 Jun 2022 18:00:05 -0400 (EDT) Date: Wed, 1 Jun 2022 18:00:05 -0400 (EDT) From: Hans-Peter Nilsson X-X-Sender: hp@arjuna.pair.com To: Alexandre Oliva cc: gcc-patches@gcc.gnu.org Subject: Re: [PATCH] Support multilib-aware target lib flags self-specs overriding In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20.16 (BSF 172 2016-09-29) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) 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: Wed, 01 Jun 2022 22:00:06 -0000 On Fri, 20 May 2022, Alexandre Oliva via Gcc-patches wrote: > > This patch introduces -multiflags, short for multilib TFLAGS, as an > option that does nothing by default, but that can be added to TFLAGS > and mapped to useful options by driver self-specs. > > I realize -m is reserved for machine-specific flags, which this option > sort-of isn't, but its intended use is indeed to stand for > machine-specific flags, so it's kind of ok. But that's just my > official excuse, the reason I couldn't help picking it up is that it > is a portmanteau of multi[lib] and TFLAGS. Ooh, a bikeshedding opportunity! Not liking the "-m"-space infringement: -frob-multiflags? -forward-multiflags? or why not just -fmultiflags? brgds, H-P