|
01:27
Voldenet left
01:29
Woodi left
01:30
Woodi joined
02:01
Voldenet joined
09:30
sena_kun joined
10:01
sena_kun left
10:05
finanalyst89 joined
10:32
finanalyst89 left
10:36
finanalyst joined
11:08
finanalyst left
14:03
rba left
14:05
rba joined
14:22
Geth joined
14:26
lizmat_ left,
lizmat joined
14:49
[Coke] left
19:10
sena_kun joined
|
|||
| Geth | MoarVM: patrickbkr++ created pull request #1859: Fix longjmp on Windows |
20:04 | |
| patrickb | timo: Can you have a look at this? ^ | 20:05 | |
|
23:17
sena_kun left
|
|||
| timo | i would say for now leave out changes to setjmp/longjmp on places where we don't have a jit, maybe even when we build without jit? | 23:39 | |
| and a comment in the source near where the magic happens would also be appreciated | |||
| do you think we can build a check for the build system that can check if a longjmp through a jitted frame would explode with the default setjmp/longjmp? and maybe something that verifies that using setjmp/longjmp like this doesn't cause trouble due to changes on the windows side of things? not sure we're relying on something that is in any way guaranteed | 23:40 | ||