On 10/25/23 01:02, Neal Frager wrote:
The MICROBLAZE_VERSION_COMPARE was incorrectly using strcasecmp
instead of strverscmp to check the mcpu version against feature
options.  By simply changing the define to use strverscmp,
the new version 10.0 is treated correctly as a higher version
than previous versions.

Signed-off-by: Neal Frager <neal.fra...@amd.com>
---
V1->V2:
  - No need to create a new microblaze specific version check
    routine as strverscmp is the correct solution.
V2->V3:
  - Changed mcpu define for microblaze isa testsuite examples.
---
  gcc/config/microblaze/microblaze.cc                        | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/bshift.c           | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/div.c              | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/fcmp1.c            | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/fcmp2.c            | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/fcmp3.c            | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/fcmp4.c            | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/fcvt.c             | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/float.c            | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/fsqrt.c            | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/mul-bshift-pcmp.c  | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/mul-bshift.c       | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/mul.c              | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/mulh-bshift-pcmp.c | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/mulh.c             | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/nofcmp.c           | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/nofloat.c          | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/pcmp.c             | 2 +-
  gcc/testsuite/gcc.target/microblaze/isa/vanilla.c          | 2 +-
  gcc/testsuite/gcc.target/microblaze/microblaze.exp         | 2 +-
  20 files changed, 20 insertions(+), 20 deletions(-)

Only two test cases actually test this fix.

Please add a ChangeLog update for these changes.

--
Michael Eager

Reply via email to