On 05/11/2021 16.12, Olivier Hainque wrote:
>
>
>> On 5 Nov 2021, at 15:12, Rasmus Villemoes wrote:
> We happen to also have a few fixincludes hunks around. Some of
> them have been there for years now and I thought would be nice to
> propagate at some point.
>
> Do you use it?
Sort of, kind
> On 5 Nov 2021, at 15:12, Rasmus Villemoes wrote:
>
>> Yes, I think so. The builds you do used to work before
>> the change that introduced the ifdef,
>
> Well, apart from all the other fixups, some of which are not
> upstreamable, that I also need to apply :)
Sure. My comment was only mea
On 05/11/2021 15.08, Olivier Hainque wrote:
>
>
>> On 5 Nov 2021, at 09:48, Rasmus Villemoes wrote:
>> Applied to master and pushed - hope I've done it right.
>
> AFAICS, yes.
>
>> How about the gcc-11 branch, can it be applied there as well,
>
> Yes, I think so. The builds you do used to wor
> On 5 Nov 2021, at 09:48, Rasmus Villemoes wrote:
> Applied to master and pushed - hope I've done it right.
AFAICS, yes.
> How about the gcc-11 branch, can it be applied there as well,
Yes, I think so. The builds you do used to work before
the change that introduced the ifdef, IIUC, and the
On 05/11/2021 09.08, Olivier Hainque wrote:
> Hi Rasmus,
>
>> On 3 Nov 2021, at 14:18, Rasmus Villemoes wrote:
>>
>> The macro TARGET_VXWORKS7 is always defined (see vxworks-dummy.h).
>> Thus we need to test its value, not its definedness.
>>
>> Fixes aca124df (define NO_DOT_IN_LABEL only in vxwo
Hi Rasmus,
> On 3 Nov 2021, at 14:18, Rasmus Villemoes wrote:
>
> The macro TARGET_VXWORKS7 is always defined (see vxworks-dummy.h).
> Thus we need to test its value, not its definedness.
>
> Fixes aca124df (define NO_DOT_IN_LABEL only in vxworks6).
>
> gcc/ChangeLog:
>
> * config/vx-co
