On Sun, 2021-11-21 at 00:47 -0300, Alexandre Oliva wrote:
> Hello, Giuliano, thanks for turning my suggestion into a patch!
>
> On Nov 19, 2021, Richard Biener wrote:
>
> > > +/* { dg-options "-fdump-ipa-clones -o /dev/null" } */
>
> May I suggest actually checking that the ipa-clones dump
Hello, Giuliano, thanks for turning my suggestion into a patch!
On Nov 19, 2021, Richard Biener wrote:
>> +/* { dg-options "-fdump-ipa-clones -o /dev/null" } */
May I suggest actually checking that the ipa-clones dump file is created
with the same name and the location it would without -o
On Fri, 19 Nov 2021 15:12:35 +0100 (CET)
Richard Biener via Gcc-patches wrote:
> On Fri, 19 Nov 2021, Giuliano Belinassi wrote:
> > -It defaults to the location of the output file; options
> > +It defaults to the location of the output file, unless the output
> > +file is a special file like
On Fri, 19 Nov 2021, Giuliano Belinassi wrote:
> The `configure` scripts generated with autoconf often tests compiler
> features by setting output to `/dev/null`, which then sets the dump
> folder as being /dev/* and the compilation halts with an error because
> GCC cannot create files in /dev/.
The `configure` scripts generated with autoconf often tests compiler
features by setting output to `/dev/null`, which then sets the dump
folder as being /dev/* and the compilation halts with an error because
GCC cannot create files in /dev/. This is a problem when configure is
testing for compiler
