On 2024-02-09 11:34, Richard Biener wrote:
On Fri, Feb 9, 2024 at 11:33 AM Torbjorn SVENSSON
wrote:
Hi,
Is it okay to backport 2f20d6296087cae51f55eeecb3efefe786191fd6 to
releases/gcc-13?
Yes.
Pushed as 5b3dcff46780192a2e526bc434d61c8626898050.
On Fri, Feb 9, 2024 at 11:33 AM Torbjorn SVENSSON
wrote:
>
> Hi,
>
> Is it okay to backport 2f20d6296087cae51f55eeecb3efefe786191fd6 to
> releases/gcc-13?
Yes.
> Without this backport, I see about 150 failures on arm-none-eabi, an
> example of them is:
>
> FAIL: gcc.dg/vect/tsvc/vect-tsvc-s000.c
Hi,
Is it okay to backport 2f20d6296087cae51f55eeecb3efefe786191fd6 to
releases/gcc-13?
Without this backport, I see about 150 failures on arm-none-eabi, an
example of them is:
FAIL: gcc.dg/vect/tsvc/vect-tsvc-s000.c (test for excess errors)
Kind regards,
Torbjörn
On 2023-05-24 11:02, Ri
On Wed, May 24, 2023 at 7:17 AM Alexandre Oliva via Gcc-patches
wrote:
>
>
> tsvc tests all fail on systems that don't offer a malloc.h, other than
> those that explicitly rule that out. Use the preprocessor to test for
> malloc.h's availability.
>
> tsvc.h also expects a definition for struct ti
tsvc tests all fail on systems that don't offer a malloc.h, other than
those that explicitly rule that out. Use the preprocessor to test for
malloc.h's availability.
tsvc.h also expects a definition for struct timeval, but it doesn't
include sys/time.h. Add a conditional include thereof.
Boot
