Hi gcc-patches mailing list,
Saurabh Jha <[email protected]> has requested that the following 
forgejo pull request
be published on the mailing list.

Created on: 2026-03-10 11:09:56+00:00
Latest update: 2026-03-10 14:41:48+00:00
Changes: 1 changed files, 15 additions, 14 deletions
Head revision: saurabh.jha/gcc-TEST ref mingw-regtest commit 
027ac4093712058f893297ae749e602c96ee9b53
Base revision: gcc/gcc-TEST ref trunk commit 
7ab4f9cc72b48b341ce52da099ee38112647d644 r16-7958-g7ab4f9cc72b48b
Merge base: 7ab4f9cc72b48b341ce52da099ee38112647d644
Full diff url: https://forge.sourceware.org/gcc/gcc-TEST/pulls/142.diff
Discussion:  https://forge.sourceware.org/gcc/gcc-TEST/pulls/142
Requested Reviewers: rearnsha

This test started failing after this commit:
b67918fddab42c434c10bedff6c210c55ed907a0

It is fixed by adding more predictability to code generation of the test
by using the option "-mcmodel=tiny".

gcc/testsuite/ChangeLog:

        * gcc.target/aarch64/mingw/variadic_hva.c: Use -mcmodel=tiny
        compile option to make code generation more predictable.

        ---
        Hey,

        Regression tested on aarch64-linux-gnu and tested the specific
        tests in gcc.target/aarch64/mingw directory for
        aarch64-w64-mingw32 target.

        Ok for gcc-16?

        Thanks,
        Saurabh

Changed files:
- M: gcc/testsuite/gcc.target/aarch64/mingw/variadic_hva.c


Saurabh Jha (1):
  aarch64: mingw: Fix a failing test variadic_hva.c

 .../gcc.target/aarch64/mingw/variadic_hva.c   | 29 ++++++++++---------
 1 file changed, 15 insertions(+), 14 deletions(-)

Range-diff against v1:
1:  1c6c0044176e ! 1:  027ac4093712 aarch64: mingw: Fix a failing test 
variadic_hva.c
    @@ Commit message
     
         gcc/testsuite/ChangeLog:
     
    -            * gcc.target/aarch64/mingw/variadic_hva.c: Fix.
    +            * gcc.target/aarch64/mingw/variadic_hva.c: Use -mcmodel=tiny
    +            compile option to make code generation more predictable.
     
                 ---
                 Hey,
-- 
2.52.0

Reply via email to