Opened 9 months ago

Closed 6 months ago

#19968 closed enhancement (fixed)

llvm-19.1.0

Reported by: Bruce Dubbs Owned by: Xi Ruoyao
Priority: normal Milestone: 12.3
Component: BOOK Version: git
Severity: trivial Keywords:
Cc:

Description (last modified by Xi Ruoyao)

New major version.

Change History (17)

comment:1 by Xi Ruoyao, 9 months ago

Severity: normaltrivial
  • [libcxx] Align __recommend() + 1 by __endian_factor
  • [libc++][NFC] Rewrite function call on two lines for clarity

We don't install libc++ so we can skip the release or just do a stat change.

Last edited 9 months ago by Xi Ruoyao (previous) (diff)

comment:2 by Bruce Dubbs, 9 months ago

Summary: llvm-18.1.8llvm-18.1.8 (Wait for next version)

comment:3 by Bruce Dubbs, 9 months ago

Milestone: 12.299-Waiting

comment:4 by Joe Locash, 8 months ago

Why not just update to .8? It doesn't need any changes and you could close 2 tickets? libclc being the other.

in reply to:  4 ; comment:5 by Bruce Dubbs, 8 months ago

Replying to Joe Locash:

Why not just update to .8? It doesn't need any changes and you could close 2 tickets? libclc being the other.

Because the odds of a newer version before we go into package freeze around August 15 is relatively high. If so, we would need to do it twice. If not then we still only need to do it once.

in reply to:  5 comment:6 by Joe Locash, 8 months ago

Replying to Bruce Dubbs:

Replying to Joe Locash:

Why not just update to .8? It doesn't need any changes and you could close 2 tickets? libclc being the other.

Because the odds of a newer version before we go into package freeze around August 15 is relatively high. If so, we would need to do it twice. If not then we still only need to do it once.

I don't understand? The only change would be to packages.ent That is updated daily.

We really need to test build it, run a few tests, update package.ent, changelog, and at least the md5sum in the llvm chapter. To me that cost in time is more than the benefit is worth.

Last edited 8 months ago by Bruce Dubbs (previous) (diff)

in reply to:  5 comment:7 by Joe Locash, 8 months ago

Replying to Bruce Dubbs:

Replying to Joe Locash:

Why not just update to .8? It doesn't need any changes and you could close 2 tickets? libclc being the other.

Because the odds of a newer version before we go into package freeze around August 15 is relatively high. If so, we would need to do it twice. If not then we still only need to do it once.

Hmm... The release date for llvm-19.1.0 is Sep 3.

comment:8 by Bruce Dubbs, 7 months ago

Milestone: 99-Waiting12.3

comment:9 by Bruce Dubbs, 7 months ago

Milestone: 12.399-Waiting

comment:10 by Xi Ruoyao, 6 months ago

Milestone: 99-Waiting12.3
Summary: llvm-18.1.8 (Wait for next version)llvm-19.1.0

comment:11 by Xi Ruoyao, 6 months ago

Owner: changed from blfs-book to Xi Ruoyao
Status: newassigned

comment:12 by Xi Ruoyao, 6 months ago

Description: modified (diff)

comment:14 by Xi Ruoyao, 6 months ago

As expected, rustc needs to be adapted:

warning: rustc_llvm@0.0.0: llvm-wrapper/RustWrapper.cpp: In function ‘LLVMOpaqueValue* LLVMRustGetInstrProfMCDCCondBitmapIntrinsic(LLVMModuleRef)’:
warning: rustc_llvm@0.0.0: llvm-wrapper/RustWrapper.cpp:1562:35: 错误:‘instrprof_mcdc_condbitmap_update’ is not a member of ‘llvm::Intrinsic’; did you mean ‘instrprof_mcdc_tvbitmap_update’?
warning: rustc_llvm@0.0.0:  1562 |       unwrap(M), llvm::Intrinsic::instrprof_mcdc_condbitmap_update));
warning: rustc_llvm@0.0.0:       |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
warning: rustc_llvm@0.0.0:       |                                   instrprof_mcdc_tvbitmap_update

error: failed to run custom build command for `rustc_llvm v0.0.0 (/home/xry111/sources/12.3/rustc-1.81.0-src/compiler/rustc_llvm)`

https://github.com/rust-lang/rust/pull/127513

Last edited 6 months ago by Xi Ruoyao (previous) (diff)

comment:15 by Xi Ruoyao, 6 months ago

To be tested:

  • SPIRV-LLVM-Translator-19.1.0
    • libclc-19.1.0
      • mesa-24.2.3 (NVK disabled)
  • Rustc-1.81.0
    • librsvg-2.58.4
    • spidermonkey-128.0
    • snapshot-47.0.1
    • ruby-3.3.5
    • cbindgen-0.27.0
      • firefox-128.2.0
      • thunderbird-128.2.0
      • seamonkey
    • rust-bindgen-0.70.1
      • mesa (NVK compile test)
Last edited 6 months ago by Xi Ruoyao (previous) (diff)

comment:16 by Xi Ruoyao, 6 months ago

New Clang does not like seamonkey:

 1:03.84 /home/xry111/sources/12.3/seamonkey-2.53.18.2/js/src/threading/ExclusiveData.h:124:33: error: reference to non-static member function must be called
 1:03.85   124 |       : lock_(mozilla::Move(rhs.lock))
 1:03.85       |                             ~~~~^~~~
 1:04.19 1 error generated.

With 2.53.19 it's slightly different but still rejected:

 1:29.35 /home/xry111/sources/12.3/seamonkey-2.53.19/js/src/threading/ExclusiveData.h:124:29: error: reference to non-static member function must be called
 1:29.35   124 |       : lock_(std::move(rhs.lock))
 1:29.35       |                         ~~~~^~~~

comment:17 by Xi Ruoyao, 6 months ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.