LLVM 3.6 Is Branched, Trunk Code Is Now For LLVM 3.7
Following last month's LLVM 3.6 plans, the mainline code of LLVM was branched for preparing the 3.6 release so now the master/trunk code is for LLVM 3.7.
The change was made on Wednesday that LLVM trunk is now for v3.7 and the LLVM 3.6 code is branched. The branched code is in the release_36 branch per their usual naming scheme.
The official LLVM 3.6.0 release will likely come several weeks down the road and is being managed by Google's Hans Wennborg. LLVM Clang 3.6 enables C11 mode by default, LLVM has many AMD GPU back-end improvements, there's LLVM Go bindings, and a wide variety of fixes. Now that LLVM 3.6 is shifting to bug-fixes over feature developer, there will be an LLVM 3.6 feature overview on Phoronix in the near future.
LLVM's 3.6 branching comes just days after GCC 5 ended feature development for a likely GCC 5 release in March or April.
The change was made on Wednesday that LLVM trunk is now for v3.7 and the LLVM 3.6 code is branched. The branched code is in the release_36 branch per their usual naming scheme.
The official LLVM 3.6.0 release will likely come several weeks down the road and is being managed by Google's Hans Wennborg. LLVM Clang 3.6 enables C11 mode by default, LLVM has many AMD GPU back-end improvements, there's LLVM Go bindings, and a wide variety of fixes. Now that LLVM 3.6 is shifting to bug-fixes over feature developer, there will be an LLVM 3.6 feature overview on Phoronix in the near future.
LLVM's 3.6 branching comes just days after GCC 5 ended feature development for a likely GCC 5 release in March or April.
1 Comment