Hardening mode for the compiler
https://discourse.llvm.org/t/rfc-hardening-mode-for-the-compiler/87660
New setup, who dis? It's that time again, but some changes:
The most significant change isn't the hardware. For the first time with MAME on Haiku, the build script uses #LLVM 20's lld
instead of GCC's ld
. I'm hoping this is going to dramatically reduce build time. We shall see!
forget u0, i1 is now my favorite integer type
My team at Apple is currently hiring for a role that focuses on compiler tools and infrastructure. If you’re interested in this opportunity, please take a look at the job posting here: https://jobs.apple.com/en-us/details/200613714/compiler-tools-engineer?team=SFTWR #llvm #swiftlang
Tính năng 'Phân tích An toàn Vòng đời' (Lifetime Safety Analysis) thử nghiệm ban đầu cho C++ đã được triển khai (-Wexpe). Điều này hứa hẹn sẽ giúp các lập trình viên C++ tránh được nhiều lỗi phổ biến liên quan đến quản lý bộ nhớ và con trỏ, làm cho mã nguồn an toàn và đáng tin cậy hơn.
#Cplusplus #Programming #Safety #SoftwareDevelopment #LLVM #Clang
#LậpTrình #NgônNgữCộngCộng #AnToànPhầnMềm #PhânTíchMã
https://discourse.llvm.org/t/announcing-the-lifetime-safety-breakout-group/87333
What I want vs what clang-format produces T_T
(No this can't be fixed, none of the 1000000 config options covers useful things, this is a whining post not a request for help. Unless you're a developer on clang-format you can't help me configure it, many have tried)
jank 程式語言 - Clojure/LLVM/C++
➤ Clojure 的高效能替代方案
✤ https://jank-lang.org/
jank 是一種通用程式語言,它結合了 Clojure 的互動式、值導向特性,並追求原生編譯和最小化運行時環境。jank 與 Clojure 具有高度相容性,並將自身視為 Clojure 的一種方言。它以 C++ 為主機,並基於 LLVM 的 JIT,提供 REPL 互動開發的優勢,並能與原生世界無縫整合,效能可與 JVM 相提並論。jank 採用函數式優先的設計,延續了 Clojure 豐富的持久化、不可變數據結構,並提供軟體事務記憶體和反應式代理系統來處理多線程設計。
+ 「這聽起來很有趣!Clojure 的優點加上原生效能,可能解決了我在大型專案中遇到的瓶頸。」
+ 「雖然聽起來很棒,但畢竟還在開發中,穩定性可能需要時間驗證。」
#程式語言 #Clojure #LLVM #C++ #開發
Introducing "Jank," the #programming #language that bravely reinvents the wheel by fusing #Clojure with the thrill of rollercoaster maintenance!
Under construction with features as solid as a ghost, it's the love child of Clojure and #LLVM that only a mother could love. Prepare your best "it's not a bug, it's a feature" face!
https://jank-lang.org/ #Jank #RollercoasterMaintenance #NotABug #HackerNews #ngated
Y'all wanna see an excessively cute trick LLVM's optimizer can do?
Swift String contains roughly this method:
```
func _fastCStringContents() -> UnsafePointer<UInt8> {
if isASCII {
return contentsPointer
}
return nil
}
```
Where `isASCII` is defined as `(flags & 0x8000_0000_0000_0000) != 0`
Would you expect this to generate (solution in reply)
Alas, looks like I’m going to have to switch from an LLVM to a GNU toolchain for this embedded ARM project, because LLVM doesn’t yet fully support the ARM FDPIC ABI—which is what supports multiple clients of a shared library with shared text and distinct read/write data on an MMUless system. (It works by making a loadable module’s globals relative to r9, just like the original PowerPC ABI made them relative to r2.) #llvm #embedded
@katyswain I din't think that #CCSS is good either, but the demands of #GPLv3 are not compatible with the (adnitteldy shitty) reality of how #IP, #Licensing and #Patents work and thus it kneecaps a lot of things.
GPLv3 caused #Apple to freeze their #bash version and divest into #LLVM and adopt #zsh.
As @landley showed, enforcing the #GPL(v2) resulted in exactly 0 code being committed to #BusyBox and it only made said project look toxic and litigatious.
Also i've yet to see anything happen re: #paywalled #SourceCodeAccess for #grsec & #RedHat #Linux. Maybe #GPLv4 will ban #paxwalling and force violators to work on #GNU / #HURD?
I chose #0BSD for _OS/1337 because as with any "intellectual labour", one cannot force others to collaborate and I'd rather have people join in out of the goodness of their hearts instead of just dumping some random git commit that is useless.
if you think ‘working with other people whose goals don’t 100% align with yours’ is a bad thing, please avoid LLVM.Well, to be fair, I try not only to avoid #LLVM but any #programming language based on it.