From: Jeff Law <jeffreyalaw@gmail.com>
To: "Thomas Schwinge" <thomas@codesourcery.com>,
"Martin Liška" <mliska@suse.cz>,
gcc-patches@gcc.gnu.org
Cc: hubicka@ucw.cz
Subject: Re: [PATCH 2/3] Add lto-dump tool.
Date: Fri, 28 Oct 2022 21:22:01 -0600 [thread overview]
Message-ID: <b9bf457b-b511-74aa-1471-d7314b597e46@gmail.com> (raw)
In-Reply-To: <878rl0tfv9.fsf@euler.schwinge.homeip.net>
On 10/28/22 04:14, Thomas Schwinge wrote:
> Hi!
>
> This minor clean-up had fallen out of me working on something else in
> GCC's options machinery, several months ago:
>
> On 2019-03-12T18:14:04+0100, marxin <mliska@suse.cz> wrote:
>> gcc/lto/ChangeLog:
>> * lang.opt: Add new language LTODump and options related
>> to LTO dump tool.
> As this new "Language" 'LTODump' does not share any options with 'LTO'
> proper, it makes sense, in my opinion, to also make that obvious in
> 'gcc/lto/lang.opt', which your Subversion r270897 (Git
> commit 66d62d9f2e6b059be6a018397fba555147133a9a) "Add lto-dump tool"
> almost ;-) did:
>
>> --- a/gcc/lto/lang.opt
>> +++ b/gcc/lto/lang.opt
>> @@ -24,6 +24,9 @@
>> Language
>> LTO
>>
>> +Language
>> +LTODump
>> +
>> Enum
>> Name(lto_linker_output) Type(enum lto_linker_output) UnknownError(unknown linker output %qs)
>>
>> @@ -66,6 +69,65 @@ fwpa=
>> LTO Driver RejectNegative Joined Var(flag_wpa)
>> Whole program analysis (WPA) mode with number of parallel jobs specified.
>>
>> +
>> +[LTODump option records]
>> +
>> +
>> fresolution=
>> LTO Joined
>> The resolution file.
> OK to push the attached
> "Better separate 'LTO' vs. 'LTODump' in 'gcc/lto/lang.opt'"?
OK.
jeff
next prev parent reply other threads:[~2022-10-29 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 14:00 [PATCH 0/3][stage1] [PATCH v2] LTO dump tool marxin
2019-03-14 14:00 ` [PATCH 2/3] Add lto-dump tool marxin
2019-04-26 13:14 ` Richard Biener
2022-10-28 10:14 ` Thomas Schwinge
2022-10-29 3:22 ` Jeff Law [this message]
2019-03-14 14:00 ` [PATCH 3/3] Fix GNU coding style in lto-common.c marxin
2019-04-29 19:43 ` Jeff Law
2019-03-14 14:06 ` [PATCH 1/3] Split part of functionality from lto.c to lto-common.c marxin
2019-04-26 12:47 ` Richard Biener
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=b9bf457b-b511-74aa-1471-d7314b597e46@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mliska@suse.cz \
--cc=thomas@codesourcery.com \
/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).