[Bug 295823] lib/libc/string/strrchr2_test:values test failing in CI due to bug in riscv strrchr.S

[email protected] Wed, 03 Jun 2026 18:40:01 +0000
Newsgroups gmane.os.freebsd.devel.standards
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D295823

            Bug ID: 295823
           Summary: lib/libc/string/strrchr2_test:values test failing in
                    CI due to bug in riscv strrchr.S
           Product: Base System
           Version: 16.0-CURRENT
          Hardware: riscv
               URL: https://ci.freebsd.org/job/FreeBSD-main-riscv64-test/1
                    6612/testReport/lib.libc.string/strrchr2_test/values/
                OS: Any
            Status: New
          Keywords: regression
          Severity: Affects Only Me
          Priority: ---
         Component: tests
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected],
                    [email protected]

Created attachment 271451
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D271451&action=
=3Dedit
CI test report

The 'lib.libc.string/strrchr2_test/values' testcase is currently failing in=
 CI
on riscv64 (URL and report attached in this bug).

This is locally reproducible with Bricoler with this command:

bricoler freebsd-regression-test-suite --freebsd-src-git-checkout/url=3D/us=
r/src
--freebsd-src-git-checkout/branch=3D --freebsd-regression-test-suite/memory=
=3D3072
--freebsd-regression-test-suite/ncpus=3D2
--freebsd-regression-test-suite/parallelism=3D1
--freebsd-src-build/machine=3Driscv/riscv64
--freebsd-regression-test-suite/hypervisor=3Dqemu --freebsd-vm-image/packag=
es=3D
--freebsd-regression-test-suite/tests=3D'lib/libc/string/strrchr2_test:valu=
es'

fuz@, if I remove strrchr.S from MDSRCS in lib/libc/riscv/string/Makefile.i=
nc,
the test passes. This points to a bug in lib/libc/riscv/string/strrchr.S.
Please triage as necessary.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=