https://gcc.gnu.org/bugzilla/show_bug.cgi?id=128809

            Bug ID: 128809
           Summary: Many additional x86 testsuite failures with
                    --with-arch-32=i586
           Product: gcc
           Version: 17.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: ubizjak at gmail dot com
  Target Milestone: ---
            Target: x86_64-*-*, i?86-*-*

When building on an x86 target with --with-arch-32=i586 (which matches the
default
on several BSDs), quite a number of 32-bit tests FAIL:

* A large number is similar to

UNRESOLVED: g++.dg/cet-notrack-1.C  -std=gnu++20  scan-assembler
endbr32|endbr64
UNRESOLVED: g++.dg/cet-notrack-1.C  -std=gnu++20  scan-assembler-times \\tcall[
\\t]+_?puts 2
UNRESOLVED: g++.dg/cet-notrack-1.C  -std=gnu++20  scan-assembler-times notrack
call[ \\t]+ 1
FAIL: g++.dg/cet-notrack-1.C  -std=gnu++20 (test for excess errors)

Excess errors:
cc1plus: error: '-fcf-protection' is not compatible with this target

  The tests unconditionally use -fcf-protection, which works with the i686
  default on e.g. Linux and Solaris, but not with the i586 (or lower) defaults
  on the BSDs.

  I guess the best solution is to introduce a cf_protection effective target,
  checking if unadorned -fcf-protection works in a trivial test.

* Besides, there are several others:

FAIL: g++.target/i386/pr103973-17.C   scan-assembler-times \\tfcom 2

g++.target/i386/pr103973-17.C  : \tfcom found 1 times

g++.target/i386/pr103973-18.C
g++.target/i386/pr103973-19.C
g++.target/i386/pr103973-20.C

similar

FAIL: g++.target/i386/pr116896-1.C  -std=gnu++20  scan-assembler-times \tjp\t 1

g++.target/i386/pr116896-1.C  -std=gnu++20 : \tjp\t found 2 times

FAIL: gcc.dg/ifcvt-4.c scan-rtl-dump ce1 "2 true changes made"

FAIL: gcc.dg/loop-invariant.c scan-rtl-dump loop2_invariant "Decided to move
invariant"

FAIL: gcc.target/i386/cf_check-6.c scan-assembler-times \\mendbr 1

gcc.target/i386/cf_check-6.c: \\mendbr found 0 times

FAIL: gcc.target/i386/minmax-10.c scan-assembler-times test 6

gcc.target/i386/minmax-10.c: test found 4 times

FAIL: gcc.target/i386/minmax-11.c scan-assembler-not 12345

FAIL: gcc.target/i386/minmax-8.c scan-assembler-times 12345 1

gcc.target/i386/minmax-8.c: 12345 found 2 times

FAIL: gcc.target/i386/pr103973-17.c scan-assembler-times \tfcom 4 

gcc.target/i386/pr103973-17.c: \tfcom found 3 times

FAIL: gcc.target/i386/pr103973-18.c scan-assembler-times \tfcom 4 

gcc.target/i386/pr103973-18.c: \tfcom found 3 times

FAIL: gcc.target/i386/pr103973-19.c scan-assembler-times \tfcom 4 

gcc.target/i386/pr103973-19.c: \tfcom found 3 times

FAIL: gcc.target/i386/pr103973-20.c scan-assembler-times \tfcom 4 

gcc.target/i386/pr103973-20.c: \tfcom found 3 times

FAIL: gcc.target/i386/pr116896.c scan-assembler-times \tjp\t 2

gcc.target/i386/pr116896.c: \tjp\t found 4 times

XPASS: gcc.target/i386/pr70465-2.c scan-assembler-not fxch\\t%st.1

  I've not yet looked how best to address those.

Reply via email to