[committed][RISC-V] Adjust recently added test

[Jeff Law]

The recently added zbb-sext test includes stdint.h and explicitly asks 
for the lp64 abi (not lp64d!).

This will fail on a native riscv system as the system headers don't 
support lp64 -- they assume "d" is included.

It looks like most tests are including stdint-gcc instead of stdint. 
Not a fan of that, but it seems to be how we've been handling this kind 
of issue to-date.

Pushing to the trunk.

jeff
commit 477868c59ed6d8192d16661c17b94201153cb88c
Author: Jeff Law <j...@ventanamicro.com>
Date:   Sat Sep 6 08:34:03 2025 -0600

    [RISC-V] Adjust recently added test
    
    The recently added zbb-sext test includes stdint.h and explicitly asks for 
the
    lp64 abi (not lp64d!).
    
    This will fail on a native riscv system as the system headers don't support
    lp64 -- they assume "d" is included.
    
    It looks like most tests are including stdint-gcc instead of stdint.  Not a 
fan
    of that, but it seems to be how we've been handling this kind of issue 
to-date.
    
    gcc/testsuite
            * gcc.target/riscv/zbb-sext.c: Include stdint-gcc.h instead of
            stdint.h.

diff --git a/gcc/testsuite/gcc.target/riscv/zbb-sext.c 
b/gcc/testsuite/gcc.target/riscv/zbb-sext.c
index 1ad3e714371..bcab8140468 100644
--- a/gcc/testsuite/gcc.target/riscv/zbb-sext.c
+++ b/gcc/testsuite/gcc.target/riscv/zbb-sext.c
@@ -1,7 +1,7 @@
 /* { dg-do compile } */
 /* { dg-options "-O2 -march=rv64gc_zbb -mabi=lp64" } */
 
-#include<stdint.h>
+#include <stdint-gcc.h>
 
 int8_t foo1(uint8_t a) {
     return a;