-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Julia 1.9 RC1 segfaults with this code #49203
Milestone
Comments
giordano
added
the
kind:regression
Regression in behavior compared to a previous version
label
Mar 31, 2023
Bisected to 7ad0e3d. cc @JeffBezanson |
Reduced example with no deps: struct A{T} end
const B{N} = A(Val(N)) |
Just for reference, on 1.8 this errors with julia> struct A{T} end
julia> const B{N} = A(Val(N))
ERROR: UndefVarError: x not defined
Stacktrace:
[1] Val{N}()
@ Base ./essentials.jl:712
[2] Val(x::TypeVar)
@ Base ./essentials.jl:714
[3] top-level scope
@ REPL[2]:1 |
vtjnash
removed
the
kind:regression
Regression in behavior compared to a previous version
label
Mar 31, 2023
Calling |
It did use to error before and now it segfaults, so I would say this is a regression. The segfault is because we call a broken tuple. |
vtjnash
added a commit
that referenced
this issue
Apr 5, 2023
We generally hit the runtime in pretty specific places when allocations look funky (because they are missing a typevar bound, so inference is not too willing to deal with it). Try to throw an error in those cases before those can get allocated and cause problems later from being non-concrete objects. Fix #49203
vtjnash
added a commit
that referenced
this issue
Apr 7, 2023
We generally hit the runtime in pretty specific places when allocations look funky (because they are missing a typevar bound, so inference is not too willing to deal with it). Try to throw an error in those cases before those can get allocated and cause problems later from being non-concrete objects. Fix #49203
KristofferC
pushed a commit
that referenced
this issue
Apr 9, 2023
We generally hit the runtime in pretty specific places when allocations look funky (because they are missing a typevar bound, so inference is not too willing to deal with it). Try to throw an error in those cases before those can get allocated and cause problems later from being non-concrete objects. Fix #49203 (cherry picked from commit a1013e7)
Xnartharax
pushed a commit
to Xnartharax/julia
that referenced
this issue
Apr 19, 2023
We generally hit the runtime in pretty specific places when allocations look funky (because they are missing a typevar bound, so inference is not too willing to deal with it). Try to throw an error in those cases before those can get allocated and cause problems later from being non-concrete objects. Fix JuliaLang#49203
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: