public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: David Malcolm <dmalcolm@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/7] Include new generated gcc/params.opt file.
Date: Wed, 20 Nov 2019 15:08:00 -0000	[thread overview]
Message-ID: <62ded737-e94e-c472-dc4a-240ad940e264@suse.cz> (raw)
In-Reply-To: <7ae0ed946407d7e8c5447c496a8ea36acec3b64e.camel@redhat.com>

On 11/20/19 4:02 PM, David Malcolm wrote:
> On Wed, 2019-11-20 at 15:51 +0100, Martin Liška wrote:
>> On 11/20/19 3:49 PM, David Malcolm wrote:
>>> On Wed, 2019-11-06 at 11:30 +0100, Martin Liska wrote:
>>>> gcc/ChangeLog:
>>>>
>>>> 2019-11-06  Martin Liska  <mliska@suse.cz>
>>>>
>>>> 	* Makefile.in: Include params.opt.
>>>> 	* flag-types.h (enum parloops_schedule_type): Add
>>>> 	parloops_schedule_type used in params.opt.
>>>> 	* params.opt: New file.
>>>> ---
>>>>    gcc/Makefile.in  |   2 +-
>>>>    gcc/flag-types.h |  11 +
>>>>    gcc/params.opt   | 967
>>>> +++++++++++++++++++++++++++++++++++++++++++++++
>>>>    3 files changed, 979 insertions(+), 1 deletion(-)
>>>>    create mode 100644 gcc/params.opt
>>>
>>> Is your params.def -> params.opt script available
>>> somewhere?  (sorry if
>>> I missed it, I didn't see it looking over the patch kit)
>>
>> Hi David.
>>
>>> (I'm rebasing my static analyzer patch kit and am about to convert
>>> my
>>> params.def additions to be params.opt additions, though I'm only
>>> adding
>>> 4 params, so hopefully doing it by hand will be trivial)
>>
>> No, it's not public. Please convert it by hand, it will be faster ;)
> 
> Fair enough.
> 
> Does this new machinery mean we can have per-frontend params (by
> putting the Param options in the pertinent .opt file) ?  (not sure what
> that will do to LTO)

I guess so. Note that now parameters are first class citizens same as options.
So that, having a per-FE should work fine.

Martin

> 
> Dave
> 

  reply	other threads:[~2019-11-20 15:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 12:33 [PATCH 0/7] Param conversion to option machinery Martin Liska
2019-11-07 12:33 ` [PATCH 1/7] Param to options conversion Martin Liska
2019-11-07 12:33 ` [PATCH 7/7] Fix test-suite fallout Martin Liska
2019-11-07 12:33 ` [PATCH 4/7] Remove gcc/params.* files Martin Liska
2019-11-12 21:17   ` Rainer Orth
2019-11-13  8:44     ` Martin Liška
2019-11-13  9:15       ` Rainer Orth
2019-11-07 12:33 ` [PATCH 6/7] Remove set_default_param_value from documentation Martin Liska
2019-11-07 12:33 ` [PATCH 5/7] Remove last leftover usage of params* files Martin Liska
2019-11-12 15:45   ` Harwath, Frederik
2019-11-12 19:33     ` Martin Liška
2019-11-07 12:33 ` [PATCH 2/7] Include new generated gcc/params.opt file Martin Liska
2019-11-20 14:51   ` David Malcolm
2019-11-20 14:53     ` Martin Liška
2019-11-20 15:03       ` David Malcolm
2019-11-20 15:08         ` Martin Liška [this message]
2019-11-20 21:32           ` David Malcolm
2019-11-21 13:05             ` Martin Liška
2019-11-07 12:34 ` [PATCH 3/7] Apply mechanical replacement (generated patch) Martin Liska
2019-11-11 14:39   ` Richard Biener
2019-11-12  9:20     ` Martin Liška
2019-11-12  9:52       ` Richard Biener
2019-11-12  9:22     ` [PATCH 8/9] Remove option_default_params and option_validate_param hooks Martin Liška
2019-11-12  9:44       ` Richard Biener
2019-11-11 14:06 ` [PATCH] Use more SET_OPTION_IF_UNSET Martin Liška
2019-11-12  9:19   ` Richard Biener
2019-11-11 14:50 ` [PATCH 0/7] Param conversion to option machinery Richard Biener
2019-11-12  9:24   ` Martin Liška
2019-11-12  9:45     ` 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=62ded737-e94e-c472-dc4a-240ad940e264@suse.cz \
    --to=mliska@suse.cz \
    --cc=dmalcolm@redhat.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).