public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/107196] New: [13 Regression] llvm-14.0.6 is miscompiles by gcc-13 in -O3: hangs llvm testsuite (inliner seems to break it)
Date: Sun, 09 Oct 2022 18:32:14 +0000	[thread overview]
Message-ID: <bug-107196-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107196
           Summary: [13 Regression] llvm-14.0.6 is miscompiles by gcc-13
                    in -O3: hangs llvm testsuite (inliner seems to break
                    it)
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: slyfox at gcc dot gnu.org
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

It's not a self-contained bug and requires full llvm build to trigger it. My
apologies. In my defense I have a few small clues to share!

The heavyweight reproducer: download llvm, build it with this week's gcc and
run one test that hangs. The bug started happening about 2 weeks ago.

The reproducer steps:

$ export CC=gcc-13
$ export CXX=g++-13

$ wget -c
https://github.com/llvm/llvm-project/releases/download/llvmorg-14.0.6/llvm-project-14.0.6.src.tar.xz
$ tar xf llvm-project-14.0.6.src.tar.xz
$ mkdir build
$ cd build

# We will build only 'llc' and run only one minimal haning test.

$ cmake ../llvm-project-14.0.6.src/llvm -DCMAKE_BUILD_TYPE=Release
-DLLVM_TARGETS_TO_BUILD=RISCV -DLLVM_ENABLE_PROJECTS='llvm'
$ make -j $(nproc) llc

$ cat >bug.ll <<EOF
    ; NOTE: Assertions have been autogenerated by
utils/update_llc_test_checks.py
    ; RUN: llc -mtriple=riscv32 -target-abi=ilp32d
-mattr=+v,+zfh,+experimental-zvfh,+f,+d -riscv-v-vector-bits-min=128
-riscv-v-fixed-length-vector-lmul-max=1 -verify-machineinstrs < %s | FileCheck
%s --check-prefixes=CHECK,LMULMAX1

    define void @ui2fp_v8i64_v8f16(<8 x i64>* %x, <8 x half>* %y) {
    ; LMULMAX1-LABEL: ui2fp_v8i64_v8f16:
    ; LMULMAX1:       # %bb.0:
      %a = load <8 x i64>, <8 x i64>* %x
      %d = uitofp <8 x i64> %a to <8 x half>
      store <8 x half> %d, <8 x half>* %y
      ret void
    }
EOF

$ timeout 10 bin/llc -mtriple=riscv32 -target-abi=ilp32d
-mattr=+v,+zfh,+experimental-zvfh,+f,+d -riscv-v-vector-bits-min=128
-riscv-v-fixed-length-vector-lmul-max=1 -verify-machineinstrs ./bug.ll && echo
FINISHED || echo TIMED OUT

'+experimental-zvfh' is not a recognized feature for this target (ignoring
feature)
'+experimental-zvfh' is not a recognized feature for this target (ignoring
feature)
'+experimental-zvfh' is not a recognized feature for this target (ignoring
feature)
TIMED OUT

$ LANG=C $CC -v |& unnix
Using built-in specs.
COLLECT_GCC=/<<NIX>>/gcc-13.0.0/bin/gcc
COLLECT_LTO_WRAPPER=/<<NIX>>/gcc-13.0.0/libexec/gcc/x86_64-unknown-linux-gnu/13.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with:
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20221002 (experimental) (GCC)

             reply	other threads:[~2022-10-09 18:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 18:32 slyfox at gcc dot gnu.org [this message]
2022-10-09 18:34 ` [Bug ipa/107196] " pinskia at gcc dot gnu.org
2022-10-09 18:34 ` pinskia at gcc dot gnu.org
2022-10-09 18:38 ` slyfox at gcc dot gnu.org
2022-10-09 18:47 ` pinskia at gcc dot gnu.org
2022-10-09 19:25 ` slyfox at gcc dot gnu.org
2022-10-09 20:02 ` slyfox at gcc dot gnu.org
2022-10-10  7:25 ` rguenth at gcc dot gnu.org
2022-10-20 17:28 ` pinskia at gcc dot gnu.org
2022-10-21  6:26 ` slyfox at gcc dot gnu.org
2022-10-21  6:28 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107196-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).