Created attachment 921069 [details] a lot of files in a lzip-tarball in attached lzip tarball: emerge_--info.txt /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/{build-info/,files/,temp/,work/**.log} /var/lib/portage/ /etc/portage/*(not gnupg) /var/log/portage/elog/llvm-core/llvm-21.0.0_pre20250311:20250317-204718.log from build.log: ``` ******************** TEST 'LLVM :: CodeGen/M68k/Control/setcc.ll' FAILED ******************** Exit Code: 1 Command Output (stderr): -- RUN: at line 2: /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm_build-abi_x86_32.x86/bin/llc < /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm/test/CodeGen/M68k/Control/setcc.ll -mtriple=m68k-linux -verify-machineinstrs | /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm_build-abi_x86_32.x86/bin/FileCheck /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm/test/CodeGen/M68k/Control/setcc.ll + /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm_build-abi_x86_32.x86/bin/llc -mtriple=m68k-linux -verify-machineinstrs + /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm_build-abi_x86_32.x86/bin/FileCheck /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm/test/CodeGen/M68k/Control/setcc.ll /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm/test/CodeGen/M68k/Control/setcc.ll:12:15: error: CHECK-NEXT: expected string not found in input ; CHECK-NEXT: shi %d0 ^ <stdin>:10:16: note: scanning from here sub.l #26, %d0 ^ <stdin>:13:8: note: possible intended match here moveq #0, %d0 ^ /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm/test/CodeGen/M68k/Control/setcc.ll:28:15: error: CHECK-NEXT: expected string not found in input ; CHECK-NEXT: scs %d0 ^ <stdin>:28:16: note: scanning from here sub.l #26, %d0 ^ <stdin>:31:8: note: possible intended match here moveq #0, %d0 ^ /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm/test/CodeGen/M68k/Control/setcc.ll:43:15: error: CHECK-NEXT: expected string not found in input ; CHECK-NEXT: moveq #0, %d2 ^ <stdin>:45:44: note: scanning from here movem.l %d2, (0,%sp) ; 8-byte Folded Spill ^ <stdin>:47:2: note: possible intended match here moveq #0, %d0 ^ Input file: <stdin> Check file: /var/tmp/portage/llvm-core/llvm-21.0.0_pre20250311/work/llvm/test/CodeGen/M68k/Control/setcc.ll -dump-input=help explains the following input dump. Input was: <<<<<< . . . 5: .type t1,@function 6: t1: ; @t1 7: ; %bb.0: ; %entry 8: move.w (6,%sp), %d0 9: and.l #65535, %d0 10: sub.l #26, %d0 next:12'0 X error: no match found 11: bhi .LBB0_1 next:12'0 ~~~~~~~~~~~~~ 12: ; %bb.2: ; %entry next:12'0 ~~~~~~~~~~~~~~~~~~ 13: moveq #0, %d0 next:12'0 ~~~~~~~~~~~~~~~ next:12'1 ? possible intended match 14: rts next:12'0 ~~~~~ 15: .LBB0_1: next:12'0 ~~~~~~~~~ 16: moveq #32, %d0 next:12'0 ~~~~~~~~~~~~~~~~ 17: rts next:12'0 ~~~~~ 18: .Lfunc_end0: next:12'0 ~~~~~~~~~~~~~ . . . 23: .type t2,@function next:12'0 ~~~~~~~~~~~~~~~~~~~~ 24: t2: ; @t2 next:12'0 ~~~ 25: ; %bb.0: ; %entry 26: move.w (6,%sp), %d0 27: and.l #65535, %d0 28: sub.l #26, %d0 next:28'0 X error: no match found 29: bcs .LBB1_1 next:28'0 ~~~~~~~~~~~~~ 30: ; %bb.2: ; %entry next:28'0 ~~~~~~~~~~~~~~~~~~ 31: moveq #0, %d0 next:28'0 ~~~~~~~~~~~~~~~ next:28'1 ? possible intended match 32: rts next:28'0 ~~~~~ 33: .LBB1_1: next:28'0 ~~~~~~~~~ 34: moveq #32, %d0 next:28'0 ~~~~~~~~~~~~~~~~ 35: rts next:28'0 ~~~~~ 36: .Lfunc_end1: next:28'0 ~~~~~~~~~~~~~ . . . 40: .p2align 1 next:28'0 ~~~~~~~~~~~~ 41: .type t3,@function next:28'0 ~~~~~~~~~~~~~~~~~~~~ 42: t3: ; @t3 next:28'0 ~~~ 43: ; %bb.0: ; %entry 44: suba.l #4, %sp 45: movem.l %d2, (0,%sp) ; 8-byte Folded Spill next:43'0 X error: no match found 46: move.l %d0, %d2 next:43'0 ~~~~~~~~~~~~~~~~~ 47: moveq #0, %d0 next:43'0 ~~~~~~~~~~~~~~~ next:43'1 ? possible intended match 48: sub.l #18, %d1 next:43'0 ~~~~~~~~~~~~~~~~ 49: subx.l %d0, %d2 next:43'0 ~~~~~~~~~~~~~~~~~ 50: scs %d1 next:43'0 ~~~~~~~~~ 51: cmpi.b #0, %d1 next:43'0 ~~~~~~~~~~~~~~~~ 52: bne .LBB2_1 next:43'0 ~~~~~~~~~~~~~ . . . >>>>>> -- ******************** ```
I think I'd remarked on this before, but for pre-releases, I'd generally say to do some investigation and report directly upstream. Start by reproducing manually (building LLVM manually) and then reducing *FLAGS and CMake options needed. (It could easily be fixed in a week in LLVM, for example.)
Already fixed upstream: https://github.com/llvm/llvm-project/issues/130754
(In reply to Michał Górny from comment #2) > Already fixed upstream: > https://github.com/llvm/llvm-project/issues/130754 Great ! Thank you for reporting upstream! (In reply to Sam James from comment #1) > I think I'd remarked on this before, but for pre-releases, I'd generally say > to do some investigation and report directly upstream. > > Start by reproducing manually (building LLVM manually) and then reducing > *FLAGS and CMake options needed. > > (It could easily be fixed in a week in LLVM, for example.) Sorry for doing almost nothing except just emerging and thanks for info about need of investigation in such cases. I'll consider doing this at next similar issues with snapshots of llvm.
(In reply to Arniii from comment #3) > > Sorry for doing almost nothing except just emerging and thanks for info > about need of investigation in such cases. I'll consider doing this at next > similar issues with snapshots of llvm. You don't need to apologise -- I'm just explaining that it's not likely to get movement.
