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

            Bug ID: 119465
           Summary: gcc.target/i386/pr55583.c FAILs with 32-bit-default
                    compiler
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: hjl.tools at gmail dot com
  Target Milestone: ---
            Target: i386-pc-solaris2.11, i686-pc-linux-gnu

Between 20241011 (aa4c55b13049cbd282cc0e043cc3e45423fdd6de) and 20241014
(fd1a2f63bcac14cbedb8c8b1790525b9642567d9),
the gcc.target/i386/pr55583.c test regressed for 32-bit

+FAIL: gcc.target/i386/pr55583.c scan-assembler-times (?n)shldl?[\\\\t
]*\\\\\$2 1
+FAIL: gcc.target/i386/pr55583.c scan-assembler-times (?n)shrdl?[\\\\t
]*\\\\\$2 2

This only happens for 32-bit compilation when using a 32-bit-default compiler.
Seen on both Solaris/x86 and Linux/i686.

The generated code differs massivly between a 32-bit-default gcc and a
64-bit-default gcc with -m64.

This is almost certainly an effect of

commit c1034d71a7f9ed446938b1c4ba7e7c95ba3a665f
Author: H.J. Lu <hjl.to...@gmail.com>
Date:   Sat Oct 12 06:15:28 2024 +0800

    gcc.target/i386/pr55583.c: Use long long for 64-bit integer

Reply via email to