Re: [patch] Silence warning in LTO mode on VxWorks

2020-05-05 Thread Richard Biener via Gcc-patches
On Tue, May 5, 2020 at 11:16 AM Eric Botcazou wrote: > > > I know it's hidden but can we make the plugin option more specific, > > like -linker-output-auto-notlo-rel? There's also no documentation for > > the lto-plugin switches, I think a good place is a comment before > > > > + else if (strcmp

Re: [patch] Silence warning in LTO mode on VxWorks

2020-05-05 Thread Eric Botcazou
> I know it's hidden but can we make the plugin option more specific, > like -linker-output-auto-notlo-rel? There's also no documentation for > the lto-plugin switches, I think a good place is a comment before > > + else if (strcmp (option, "-linker-output-no-warning") == 0) > +linker_output

Re: [patch] Silence warning in LTO mode on VxWorks

2020-05-05 Thread Richard Biener via Gcc-patches
On Tue, May 5, 2020 at 10:36 AM Eric Botcazou wrote: > > Hi, > > the link phase is always partial (-r) for VxWorks in kernel mode, which means > that it uses incremental LTO linking by default (-flinker-output=rel). But in > this mode the LTO plugin outputs a warning if one of the object files in

[patch] Silence warning in LTO mode on VxWorks

2020-05-05 Thread Eric Botcazou
Hi, the link phase is always partial (-r) for VxWorks in kernel mode, which means that it uses incremental LTO linking by default (-flinker-output=rel). But in this mode the LTO plugin outputs a warning if one of the object files involved in the link does not contain LTO bytecode, before switc