Mastodon#llvm

Does anyone know why on #OpenBSD

l = strtol("0xquux", &rest, 16);

produce
l=0 and rest=0xquux

and on #Linux (at least)
l=0 and rest=xquux

Is there any #C99 gurus who can tell if there is a defined behaviour?

#gcc #llvm #stdlib #clang #programming #unix

It'd be cool if #LLVM was ported to #Plan9 but I don't want C++ to invade it.

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