Re: [PATCH] testsuite: Only run test if alarm is available

2025-01-23 Thread Torbjorn SVENSSON
On 2025-01-22 22:15, Mike Stump wrote: On Jan 19, 2025, at 12:47 PM, Torbjorn SVENSSON wrote: On 2025-01-19 21:20, Andrew Pinski wrote: On Sun, Jan 19, 2025 at 12:17 PM Torbjörn SVENSSON wrote: Ok for trunk? -- Most baremetal toolchains will not have an implementation for alarm and s

Re: [PATCH] testsuite: Only run test if alarm is available

2025-01-22 Thread Mike Stump
On Jan 19, 2025, at 12:47 PM, Torbjorn SVENSSON wrote: > > On 2025-01-19 21:20, Andrew Pinski wrote: >> On Sun, Jan 19, 2025 at 12:17 PM Torbjörn SVENSSON >> wrote: >>> >>> Ok for trunk? >>> >>> -- >>> >>> Most baremetal toolchains will not have an implementation for alarm and >>> sigaction

Re: [PATCH] testsuite: Only run test if alarm is available

2025-01-19 Thread Torbjorn SVENSSON
On 2025-01-19 21:20, Andrew Pinski wrote: On Sun, Jan 19, 2025 at 12:17 PM Torbjörn SVENSSON wrote: Ok for trunk? -- Most baremetal toolchains will not have an implementation for alarm and sigaction as they are target specific. For arm-none-eabi with newlib, function signatures are expose

Re: [PATCH] testsuite: Only run test if alarm is available

2025-01-19 Thread Andrew Pinski
On Sun, Jan 19, 2025 at 12:17 PM Torbjörn SVENSSON wrote: > > Ok for trunk? > > -- > > Most baremetal toolchains will not have an implementation for alarm and > sigaction as they are target specific. > For arm-none-eabi with newlib, function signatures are exposed, but > there is no implmentation

[PATCH] testsuite: Only run test if alarm is available

2025-01-19 Thread Torbjörn SVENSSON
Ok for trunk? -- Most baremetal toolchains will not have an implementation for alarm and sigaction as they are target specific. For arm-none-eabi with newlib, function signatures are exposed, but there is no implmentation and thus the test cases causes a undefined symbol link error. gcc/testsuit