From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Support multilib-aware target lib flags self-specs overriding
Date: Sat, 05 Nov 2022 06:23:40 -0300 [thread overview]
Message-ID: <or1qqh4uw3.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <orr0zltl4p.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Thu, 06 Oct 2022 05:24:38 -0300")
On Oct 6, 2022, Alexandre Oliva <oliva@adacore.com> wrote:
> I'd much rather we could use -fmultiflags, a far more elegant
> arrangement IMHO, so...
> Ping? https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597419.html
>> for gcc/ChangeLog
>> * common.opt (fmultiflags): New.
>> * doc/invoke.texi: Document it.
>> * gcc.cc (driver_self_specs): Discard it.
>> * opts.cc (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.
A month has gone by and no objections have been raised, so I'm finally
going ahead and checking it in.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
prev parent reply other threads:[~2022-11-05 9:23 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
2022-11-05 9:23 ` Alexandre Oliva [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=or1qqh4uw3.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).