On Tue, May 25, 2021 at 11:18:55AM +0200, Richard Biener via Gcc-patches wrote:
> On Tue, May 25, 2021 at 11:15 AM Jakub Jelinek via Gcc-patches
> wrote:
> >
> > Hi!
> >
> > This TU uses exit, but doesn't include or and relies
> > on some other header to include it indirectly, which apparently d
On Tue, May 25, 2021 at 11:15 AM Jakub Jelinek via Gcc-patches
wrote:
>
> Hi!
>
> This TU uses exit, but doesn't include or and relies
> on some other header to include it indirectly, which apparently doesn't
> happen on reporter's host.
>
> The other headers aren't guarded either and we rely o
On 25/05/21 10:37 +0200, Jakub Jelinek wrote:
Hi!
This TU uses exit, but doesn't include or and relies
on some other header to include it indirectly, which apparently doesn't
happen on reporter's host.
The other headers aren't guarded either and we rely on a compiler
capable of C++11, so may
Hi!
This TU uses exit, but doesn't include or and relies
on some other header to include it indirectly, which apparently doesn't
happen on reporter's host.
The other headers aren't guarded either and we rely on a compiler
capable of C++11, so maybe we can rely on being around
unconditionally.