On Wed, Mar 04, 2020 at 06:23:10PM +0100, Martin Liška wrote:
> On 3/4/20 4:25 PM, Egeyar Bagcioglu wrote:
> > Thanks Richard.
> >
> > I do not have write-access to the GCC repo. I'd be glad if someone commits
> > it for me.
>
> Can we please wait? I'm really convinced we do not want one another very
> similar
> functionality. I would definitely recommend to change the semantics
> of -frecord-gcc-switches to what the patchset does.
>
> That's why I added Nick as he's the author of the original implementation.
> Reasoning is provided in my previous email.
Also, what is the reason for storing the option in a file, rather than say
putting them into an environment variable from which the backend can pick it
up? I must say I don't really see advantages of this over
-grecord-gcc-switches, recording all options looks very bloaty and will
include mostly stuff you don't really care about (such as, e.g. the -I
options without knowing what was the current directory when the source file
has been compiled), on the other side will not record interesting options
that -grecord-gcc-switches records (say, if some code is compiled with
-march=native, this new option will record that, rather than what it really
is), but I won't stand in a way unless such an option would be on by
default.
Jakub
