Valentin Churavy
Valentin Churavy
@nanosoldier `runbenchmarks(!"scalar", vs=":vc/upgrade_llvm15")`
@nanosoldier `runbenchmarks(!"scalar", vs=":master")`
@nanosoldier `runbenchmarks(!"scalar", vs=":vc/upgrade_llvm15")`
Will this need to be backported to 1.9 since it's a bugfix to the effect system?
Rebased in #589
As said on discourse: https://discourse.julialang.org/t/floop-threading-and-juliacall-produce-segmentation-fault/100717/11?u=vchuravy Julia intentionally causes segmentation faults as part of the GC safepoint mechanism. This MPI.jl issue is somewhat related https://github.com/JuliaParallel/MPI.jl/issues/725 PythonCall starts Julia with `--handle-signals=no` https://github.com/cjdoris/PythonCall.jl/blob/e374e2503b7b843c457d30596a2428ebfc26bb0b/pysrc/juliacall/__init__.py#L132...
Yes, changing it from no to yes will at least no longer cause faults due to GC (and it looks like most of the recorded issues here worked around it...
Hangs could come about from one thread wanting to stop the world and another executing Python code? The code would need to manually transition to GC safe before calling into...
So there are a couple of interactions here: 1. Julia uses signals internally for multiple purposes, starting Julia with signal handlers off and multi-threading on is an unsupported configuration (I...
I don't know that anyone is working on signal chaining.