On Feb 22, 2023, at 12:04 PM, Alexandre Oliva wrote:
>
> That would change what gets tested with clang, I suppose, but I hope
> that's for the better. I wondered what to do at the #else above, and
> decided to spell it a little differently. Retested on x86_64-linux-gnu
> (trunk) and arm-vxworks
On Feb 17, 2023, Iain Sandoe wrote:
> As a matter of interest, do you know of any other compiler claiming
> “__clang__” (I have
> treated that as safe so far).
We've had (or found it more convenient, not sure) to do that to gcc on
some recent combinations of version and target of vxworks, for o
Hi,
> On 17 Feb 2023, at 06:42, Alexandre Oliva via Gcc-patches
> wrote:
>
>
> The test is compatible with clang as well as gcc, but ISTM that
> testing for the __clang__ macro is just as potentially error-prone as
> macros that used to be GCC-specific are now defined in compilers that
> aim f
