Re: Analyzer failure due to missing header

2023-08-30 Thread David Malcolm via Gcc
On Wed, 2023-08-30 at 23:24 +0200, FX Coudert wrote: > > std::max and std::min, introduced by d99d73c77d1e and 2bad0eeb5573, > > are not available because is not included. > > I originally thought this was only seen in cross-compilers, but it > actually broke bootstrap on darwin. > Attached patch

Re: Analyzer failure due to missing header

2023-08-30 Thread FX Coudert via Gcc
> std::max and std::min, introduced by d99d73c77d1e and 2bad0eeb5573, are not > available because is not included. I originally thought this was only seen in cross-compilers, but it actually broke bootstrap on darwin. Attached patch restores it, OK to commit? FX 0001-Analyzer-include-algori

Re: Analyzer failure due to missing header

2023-08-30 Thread Jakub Jelinek via Gcc
On Wed, Aug 30, 2023 at 11:10:57AM +0200, FX Coudert via Gcc wrote: > std::max and std::min, introduced by d99d73c77d1e and 2bad0eeb5573, are not > available because is not included. The following patch fixes the > build for me: > > diff --git a/gcc/analyzer/region-model.cc b/gcc/analyzer/regio

Analyzer failure due to missing header

2023-08-30 Thread FX Coudert via Gcc
Hi David, I’m seeing the following failures on building GCC with Apple’s clang: > /Users/fx/devel/gcc/gcc-repo-write/gcc/analyzer/region-model.cc:3426:16: > error: unexpected type name 'byte_size_t': expected expression >std::max (bytes.m_size_in_bytes, >