github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
nwc10 good *, #moarvm 06:33
Geth MoarVM: 23dfde978c | (Patrick Böker)++ | build/setup.pm
Explicitly state we use gnu99 on GCC

This fixes building on older versions of GCC (< 5.0) that default to gnu89. Using `-std=c99` instead of `-std=gnu99` breaks the build of libuv because some pthread declarations are then left out. So it seems sensible to go with the GCC default of using the `gnu99` variant instead of the `c99` variant. ... (7 more lines)		 11:09
MoarVM: bf6af07dee | (Patrick Böker)++ (committed using GitHub Web editor) | build/setup.pm
Merge pull request #1318 from patrickbkr/fix-gcc4

Explicitly state we use gnu99 on GCC
lizmat I guess we need a bump now? 11:23
Altai-man_ lizmat, can try to see if the issue resolved.
lizmat ok, will do 11:24
dogbert17 oh, it's brrt, hello there 12:29
nwc10 good *, brrt 12:30
good *, dogbert17
dogbert17 hello nwc10, what's the state of your beer fridge? 12:31
dogbert17 temperature is slowly creeping towards 30 degrees centigrade here 12:32
dogbert17 could use a beer but don't have any atm :( 12:33
nwc10 it has beer. Although I realised last night that most of the beer was in the crate near it, and not enough in the fridge itself 12:35
timotimo hewwo bwwt 12:36
dogbert17 so it's not very cold then :)
hello timotimo
timotimo temperature is like 28 centigrade, will be 30 the next two days
dogbert17 Yeah, just picked up a cheap fan which I can use if things get out of hand 12:38
my apartment is on the top floor and can get uncomfartably hot during the summer 12:40
timotimo oh no
top floor is terrible
dogbert17 almost 30 degrees inside atm
timotimo disgusting
dogbert17 yes indeed
timotimo i am maybe too sensitive to heat, but damn, it just kills me
dogbert17 I don't like it either 12:41
I mean what's wrong with say 22-24 degrees 12:42
timotimo aye 12:44
brrt hi nwc10, dogbeter, timotimo 12:50
*dogbert17
dogbert17 brrt, is it extremely hot where you live as well today? 12:55
lizmat: stresstest looks fine 12:57
lizmat dogbert17: any opinions about performance of the match-refactor branch in stresstest ? 17:12
brrt dogbert17: it's nearly 30 degrees C, which is warm, but not nearly as warm as last year 17:27
which still might happen, midn
brrt on the topic of bombshells.... www.perl.com/article/announcing-perl-7/ 19:02
[Coke] I don't know about "bombshell", I mean we pretty much set them up for that. 19:05
... that said, first I heard was post-sawyer presention
brrt hehe true 19:07
I read it and I *think* it is all sane and good 19:08
preferable to sticking with perl5.xxxxx
nwc10 it was a very well kept secret. In that, it remained an unknown unknown
timotimo i wonder what the next step for the jit currently is 20:21
nwc10 ARM. Ready for next year's macs? 20:22
<ducks> 20:23
jnthn Teach the expression JIT about dispatch :P 20:24
timotimo wouldn't spesh be code-genning most stuff so the jit would just see guards and simple ops? 20:40
jnthn Only in the case the callsite was linked... 20:42
Or rewritable
Dunno if we'll have some that ain't 20:43
(other than unlinked, of course)
That said, one option for handling a dispatch that was never linked is to always turn it into a deopt
That way, you get rid of unreachable codepaths
uh, unreached
timotimo so we cut every instruction after the unconditional deopt and end up with a shorter frame instead? 20:51
jnthn Yeah 21:01

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!