RIP, Dad. I can only hope your were happy in your life. May your next reincarnation perhaps be a higher one, or at least with a better life, whenever/wherever/whatever it is. Perhaps we may talk again, in my lifetime, even if only in an 'Astral' realm.
It took longer than i thought to get rid of this eyesore, but here we are at last! Even though the code has already been fuzz-clean for "eternity", actually having proper bounds checks on everything is a major milestone at last. @pixlsus@darktable_org https://t.co/wvE7DJ4DA1
An Early Look At #LLVM#Clang 13 Performance On @AMD#Zen3
-- This initial round of Clang 13 compiler benchmarking on a @Tyan @AMDServer#EPYC
https://t.co/6qFSCqoOb3
@pervognsen @matt_dz It is 4/7cy: https://t.co/5wBXRsk2c9 +1cy is coming from https://t.co/zHXEW0D4kT I didn't measure that particular number, it could be wrong, esp. since mov are 0cy. I'm not sure how to confirm this though. https://t.co/pMBZpavH0o measures @ 6.5cy/load+store. What's store latency?
@llvmorg@llvmweekly@phoronix@AMD@AMDRyzen
6 months for `-march=znver3` is better than 6 years it took for `-march=bdver2` :) Though, it actually only took me ~42 days since i started needing said sched model.
@johnregehr That transform was a fun one to come up with!
Gaining a way to actually prove it (and that was made possible about the same time) was perhaps even more awesome, thanks @vpshufb & others!
@pixlsus@darktable_org@llvmorg Now that https://t.co/6mtwTRABFb fixed #llvm to not prevent vectorization by hoisting common code into loop header, i've *finally* found some energy to rewrite #RawSpeed's Canon .CR2 decoding code, with good perf results https://t.co/tmJY3690Ki
@johnregehr Since there is already structure-aware LLVM IR fuzzing, the very obvious next step would be to integrate alive2 into instcombine fuzzer - having a way to tell if IR transformation is a miscompile or not is great, but it requires preexisting IR to function..
@johnregehr Circling back to this, increment/decrement support done too: https://t.co/al2vgn1atl
i think mostly only bit field handling is missing..
(did not check volatile/atomic/enum status)
More UB fun, with live miscompilations in-the-wild: applying non-zero (in C - any) offset to null pointer is undefined behavior in C++
https://t.co/gsL1nY1bN3 @johnregehr @kayseesee @Philip_Reames #llvm#clang#ubsan