** Description changed:

  ## FFE ##
  
  I'm filing this under llvm 22 due to a launchpad issue, but it applies
  to llvm 23
  
  [Rationale]
  
  * Having LLVM 23 in Stonking would dramatically simplify some ongoing
  work around the ROCm stack, and related packages. See, for example, the
  comments in this bug:
  https://bugs.launchpad.net/ubuntu/+source/ucc/+bug/2166379
  
- * Having the latest LLVM directly available in the archive is always a
- good thing.
+ * Providing the most recent LLVM in the distro enables users and developers
+   to work with the most recent LLVM version.  It also makes it easier to
+   get new subminor LLVM 23 releases accepted with SRUs.
  
  [ Scope ]
  
  * The large majority of the package is entirely new binary packages, and
  technically do not require an FFE.
  
- * The remaining packages which do require the FFE are libc++1,
- libc++abi1, libomp5, and llvm-libunwind1. These packages are backwards
- compatible and having new versions of them means we get fixes and
- improvements directly from upstream.
+ * The remaining packages which do require the FFE are libc++1, libc++abi1, 
libomp5, and llvm-libunwind1. All these library packages have symbols files,
+ only adding new symbols.  Starting with LLVM 20, there were no issues seen
+ with this approach, and these packages work with older LLVM versions.  
libc++1,
+ libc++abi1 and llvm-linunwind1 are not used by other packages, libomp5 is
+ used by a handful of packages.
  
  * This will not change the default version of LLVM in Stonking, which
  remains 22
  
  * > seeded-in-ubuntu llvm-toolchain-23
-   The source package 'llvm-toolchain-23' status Superseded not in 
(Pending,Published) in stonking for pockets Release, Security, Updates, 
Proposed with status in Pending, Published
+   The source package 'llvm-toolchain-23' status Superseded not in 
(Pending,Published) in stonking for pockets Release, Security, Updates, 
Proposed with status in Pending, Published
  
  [ Regression Potential ]
  
- * Regressions in the four common packages, listed above, are possible.
- However, if they introduce regressions, those will be directly caused by
- the upstream code. Since 23 is the currently maintained stable version,
- any regressions are likely to be fixed more actively by upstream
- directly.
+ * Regressions in the four common binary packages, listed above, are possible.
+ The presence of symbols files should mitigate these concerns.
  
  [ Testing ]
  
  * The autopkgtests for LLVM are thorough, and running them for this
  package, and for llvm-toolchain-22 will help us identify any
  regressions.
+ 
+ [ Upload ]
+ * Due to build time constraints, upload is planned as a binary copy from 
+ ppa:karljs/ubuntu/llvm-toolchain-23-stonking, once the package is built on all
+ architectures.
+ 
+ * There is another LLVM 22 upload prepared to stop building the four common
+   binary packages then built by LLVM 23.  If that cannot be done in time for
+   the stonking release, the LLVM 22 upload can also be done safely as a SRU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2168782

Title:
  [FFE] Please add llvm-toolchain-23 to Stonking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-22/+bug/2168782/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to