On Tue, Jan 21, 2020 at 12:22 AM Jakub Jelinek wrote:
> I only see one spot where it has been added and then
> 2019-06-06 Florian Weimer
>
> * sysdeps/unix/sysv/linux/riscv/flush-icache.c: Do not use
> internal GCC preprocessor identifier __has_include__.
> which corrected it to
On 1/20/20 9:01 PM, Jim Wilson wrote:
On Mon, Jan 20, 2020 at 5:44 AM Nathan Sidwell wrote:
I've pushed this to master, to address 80005
__has_include is funky in that it is macro-like from the POV of #ifdef
...
With this patch, __has_include__ no longer works. There is a use of
this in the
On Mon, Jan 20, 2020 at 06:01:27PM -0800, Jim Wilson wrote:
> On Mon, Jan 20, 2020 at 5:44 AM Nathan Sidwell wrote:
> > I've pushed this to master, to address 80005
> >
> > __has_include is funky in that it is macro-like from the POV of #ifdef
> > ...
>
> With this patch, __has_include__ no longe
On Mon, Jan 20, 2020 at 5:44 AM Nathan Sidwell wrote:
> I've pushed this to master, to address 80005
>
> __has_include is funky in that it is macro-like from the POV of #ifdef
> ...
With this patch, __has_include__ no longer works. There is a use of
this in the RISC-V glibc port. I see the docs
I've pushed this to master, to address 80005
__has_include is funky in that it is macro-like from the POV of #ifdef
and friends, but lexes its parenthesize argument #include-like. We were
failing the second part of that, because we used a forwarding macro to
an internal name, and hence always