Re: [PATCH] plugins: Allow plugins to handle global_options changes

2020-11-18 Thread Joseph Myers
On Wed, 18 Nov 2020, Jakub Jelinek via Gcc-patches wrote: > On Wed, Nov 18, 2020 at 10:39:46AM +0100, Richard Biener wrote: > > We already have --{enable,disable}-plugin, so could remove it when > > those are not enabled. > > Here is a variant that does that: > > 2020-11-18 Jakub Jelinek > >

Re: [PATCH] plugins: Allow plugins to handle global_options changes

2020-11-18 Thread Jakub Jelinek via Gcc-patches
On Wed, Nov 18, 2020 at 10:39:46AM +0100, Richard Biener wrote: > We already have --{enable,disable}-plugin, so could remove it when > those are not enabled. Here is a variant that does that: 2020-11-18 Jakub Jelinek * opts.h (struct cl_var): New type. (cl_vars): Declare.

Re: [PATCH] plugins: Allow plugins to handle global_options changes

2020-11-18 Thread Richard Biener via Gcc-patches
On Wed, Nov 18, 2020 at 10:14 AM Jakub Jelinek via Gcc-patches wrote: > > Hi! > > Reposting with self-contained description per Joseph's request: > > Any time somebody adds or removes an option in some *.opt file (which e.g. > on the 10 branch after branching off 11 happened 7 times already), many

[PATCH] plugins: Allow plugins to handle global_options changes

2020-11-18 Thread Jakub Jelinek via Gcc-patches
Hi! Reposting with self-contained description per Joseph's request: Any time somebody adds or removes an option in some *.opt file (which e.g. on the 10 branch after branching off 11 happened 7 times already), many offsets in global_options variable change and so plugins that ever access GCC opti