Mastodon#llvm

Hmmmm I wonder what happened to the efforts to get p6 on llvm.

A good comment on the silliness of investing in SPEC numbers.

"And noone cares about trying to settle things down and produce a compiler one can trust (because version N+1 runs 3.14% faster in the loonystones benchmark which doesn't match any real life use case). Who cares? Tomorrow's compiler will generate code which will complete an infinite loop in less than 5 seconds; stay tuned for more accomplishments!"

marc.info/?l=openbsd-misc&m=13

Taming Undefined Behavior in LLVM, by John Regehr
blog.regehr.org/archives/1496

I want to talk about a new paper (cs.utah.edu/~regehr/papers/und) about undefined behavior in LLVM that’s going to be presented in June at PLDI 2017.
Its goal is to describe and try to fix some unintended consequences of the design of undefined behavior at the level of LLVM IR.

#llvm #ub

via "Lazy Reading for 2017/04/16" dragonflydigest.com/2017/04/16

M in LLVM stands for “Magic”

@fsf @dtluna an example of #stallman being impractical: https://quitter.se/attachment/2599877

i agree with #stallman on a lot of things, but i can't help but shake my head when he wastes effort on this nonsense.

that diagram is missing a lot of pieces. neither #gnu userspace or #linux constitute a fully featured operating system on their own. You need a whole collection of (non-gnu, but still free/open) software to have a productive system.

if you really need to be in control of the #brand, hire some professionals and put together a #brand that sells. at this point, #linux obviously has better #branding, because people actually remember the fucking name.

#arch #bitcoin #bluez #calibre #chromium #clamav #firefox #gmpc #ipfs #jack #koffice #linux #mpd #mutt #llvm #plasma #pulseaudio #runit #sbase #st #transmission #ubase #vim #wayland #zsh