Re: [PATCH 1/2] gcc: make Valgrind errors fatal during bootstrap

2024-10-05 Thread Mark Wielaard
Hi (adding Philippe to CC who knows a bit more about Valgrind vs Ada), On Sat, Oct 05, 2024 at 06:07:27AM +0100, Sam James wrote: > Jeff Law writes: > > > On 10/2/24 8:39 PM, Sam James wrote: > >> Valgrind doesn't error out by default which means bootstrap issues like > >> in PR116945 can easily

Re: [PATCH 1/2] gcc: make Valgrind errors fatal during bootstrap

2024-10-04 Thread Sam James
Jeff Law writes: > On 10/2/24 8:39 PM, Sam James wrote: >> Valgrind doesn't error out by default which means bootstrap issues like >> in PR116945 can easily be missed: pass --exit-errorcode=1 to handle this. >> While here, also set --trace-children=yes to cover child processes >> of tools invoked

Re: [PATCH 1/2] gcc: make Valgrind errors fatal during bootstrap

2024-10-04 Thread Jeff Law
On 10/2/24 8:39 PM, Sam James wrote: Valgrind doesn't error out by default which means bootstrap issues like in PR116945 can easily be missed: pass --exit-errorcode=1 to handle this. While here, also set --trace-children=yes to cover child processes of tools invoked during the build. Note th

[PATCH 1/2] gcc: make Valgrind errors fatal during bootstrap

2024-10-02 Thread Sam James
Valgrind doesn't error out by default which means bootstrap issues like in PR116945 can easily be missed: pass --exit-errorcode=1 to handle this. While here, also set --trace-children=yes to cover child processes of tools invoked during the build. Note that this only handles tools invoke during t