Valentin Churavy comments

Results 1413 comments of


                                            Valentin Churavy

Revisiting representation of missing values

@johnmyleswhite Yes providing `sentinel` for each possible value would be getting annoying fast. Probably best would be to use a trait interface turning my example into. *I also noticed that...

Activate NewPM support

@nanosoldier `runtests(ALL, vs = ":master", configuration = (;buildflags=["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"]))`

Activate NewPM support

@nanosoldier `runbenchmarks(!"scalar", vs=":master")`

Malformed IR with cglobal call inside try/catch on master debug build

Yeah this is from `.pkg/select_artifacts.jl` where I see: ``` Expr(:call, Main.cglobal, Expr(:call, Core.tuple, :(:_ZN4llvm24DisableABIBreakingChecksE), Expr(:call, Base.libllvm_path)), Main.Cvoid)```

Malformed IR with cglobal call inside try/catch on master debug build

So yeah https://github.com/JuliaLang/julia/blob/956e0a3148dd42df102f8852be85cc12b876448c/base/compiler/validation.jl#L87 we do need to linearize them...

Update LLVM to 14.0.6+0

@nanosoldier `runtests(ALL, vs = ":master", buildflags=["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"], vs_buildflags=["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"])`

Update LLVM to 14.0.6+0

@nanosoldier `runbenchmarks(!"scalar", vs=":master")`

Update LLVM to 14.0.6+0

@nanosoldier `runtests(ALL, vs = ":master", configuration = (buildflags=["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"]))`

Heap snapshot

Closed in favor of #46862

Improve documentation for new allocation profiler

cc: @vilterp @NHDaly