On 5/9/22 14:26, Richard Biener wrote:
> On Mon, May 9, 2022 at 2:16 PM Martin Liška wrote:
>>
>> On 5/9/22 13:58, Richard Biener wrote:
>>> The patch would have been a lot smaller if you kept it Joined only?
>>
>> Yes, but the langspec rules append a space for some reason:
>>
>> $ ./xgcc -B. /tmp
On Mon, May 9, 2022 at 2:16 PM Martin Liška wrote:
>
> On 5/9/22 13:58, Richard Biener wrote:
> > The patch would have been a lot smaller if you kept it Joined only?
>
> Yes, but the langspec rules append a space for some reason:
>
> $ ./xgcc -B. /tmp/1.h -ox.h.pch --save-temps --verbose
> ...
> .
On 5/9/22 13:58, Richard Biener wrote:
> The patch would have been a lot smaller if you kept it Joined only?
Yes, but the langspec rules append a space for some reason:
$ ./xgcc -B. /tmp/1.h -ox.h.pch --save-temps --verbose
...
./cc1 -fpreprocessed x.h.pch-1.i ... --output-pch= x.h.pch
Martin
On Mon, May 9, 2022 at 10:58 AM Martin Liška wrote:
>
> Do not allow strange option format:
> -msmall-data-limit= 11.
>
> For -output-pch we need to use Separate syntax as lang spec
> rules automatically append a space.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
>
Do not allow strange option format:
-msmall-data-limit= 11.
For -output-pch we need to use Separate syntax as lang spec
rules automatically append a space.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
PR target/105355
gcc/