public inbox for
 help / color / mirror / Atom feed
From: Alexandre Oliva <>
Subject: Re: [PATCH] Support multilib-aware target lib flags self-specs overriding
Date: Thu, 06 Oct 2022 05:24:38 -0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Alexandre Oliva's message of "Tue, 28 Jun 2022 10:32:54 -0300")

On Jun 28, 2022, Alexandre Oliva <> wrote:

> Support multilib-aware target lib flags self-specs overriding

> This patch introduces -fmultiflags, 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.

> Regstrapped on x86_64-linux-gnu.  Posted mainly FTR, but...  I wouldn't
> mind putting it in, so...  Ok to install?  ;-)

Since this patch didn't seem to gain much traction towards acceptance,
I've been thinking of other ways to accomplish its goal, namely, to
enable target libs to be built with additional flags, like setting
TFLAGS, but enabling different multilibs to be built with different

The other way that came to mind was to add settings to the multilib
target fragment configurations, say MULTILIB_TFLAGS, to map multilibs to
extra flags to use, and then adjust the target lib multilib flag build
machinery to extract and add these flags when configuring and building
each library.  Yuck.

I'd much rather we could use -fmultiflags, a far more elegant
arrangement IMHO, so...


> for  gcc/ChangeLog

> 	* common.opt (fmultiflags): New.
> 	* doc/invoke.texi: Document it.
> 	* (driver_self_specs): Discard it.
> 	* (common_handle_option): Ignore it in the driver.

Since this is kind of a build machinery feature, would anyone mind if I
self-approved this with my build machinery maintainer hat on?

Please raise your objection within one week if you do.


Alexandre Oliva, happy hacker      
   Free Software Activist                       GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <>

  reply	other threads:[~2022-10-06  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 19:13 Alexandre Oliva
2022-05-28  7:02 ` Alexandre Oliva
2022-06-01 22:00 ` Hans-Peter Nilsson
2022-06-03  7:15   ` Alexandre Oliva
2022-06-28 13:32     ` Alexandre Oliva
2022-10-06  8:24       ` Alexandre Oliva [this message]
2022-11-05  9:23         ` Alexandre Oliva

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).