Version 0.7.0-rc1.0, permutedims crash with Illegal inttoptr #28388
Assignees
Labels
Milestone
Comments
|
Same on Linux; full stacktrace: Looks related to Keno's recent LLVM fixes? Edit: julia> versioninfo()
Julia Version 0.7.0-rc1.4
Commit 0ef8826 (2018-08-01 00:52 UTC)
Platform Info:
OS: Linux (x86_64-linux-gnu)
CPU: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.0 (ORCJIT, skylake) |
fredrikekre
changed the title
|
Probably dup of #28379? |
|
If it is a dup, better to close #28379 as this is a much better MWE. |
|
I cannot reproduce this on 0.7.0-rc1.5, Ubuntu 16.04 |
|
I get it on rc1.4: _
_ _ _(_)_ | A fresh approach to technical computing
(_) | (_) (_) | Documentation: https://docs.julialang.org
_ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
| | | | | | |/ _` | |
| | |_| | | | (_| | | Version 0.7.0-rc1.4 (2018-08-01 00:52 UTC)
_/ |\__'_|_|_|\__'_| | Commit 0ef882679f (0 days old master)
|__/ | x86_64-apple-darwin17.7.0
julia> x = rand(4,3,2)
4×3×2 Array{Float64,3}:
[:, :, 1] =
0.547093 0.681695 0.259469
0.450266 0.939295 0.590317
0.925171 0.85919 0.548892
0.182937 0.288661 0.0223785
[:, :, 2] =
0.151585 0.0777777 0.167315
0.333083 0.595943 0.748375
0.00221635 0.153361 0.20937
0.613113 0.0917188 0.383782
julia> y = permutedims(x,[3,1,2])
Illegal inttoptr
%49 = ptrtoint double addrspace(13)* %48 to i64
Illegal inttoptr
%104 = inttoptr i64 %103 to i8 addrspace(13)*
signal (6): Abort trap: 6
in expression starting at no file:0
__pthread_kill at /usr/lib/system/libsystem_kernel.dylib (unknown line)
Allocations: 5956874 (Pool: 5955405; Big: 1469); GC: 12
Abort trap: 6 |
|
Just FYI, I don't on what is basically the same (it has one more commit, #28386): |
|
For those of you who do not get this failure, have you rebuilt llvm after Keno's patches? (i.e. |
|
llvm was rebuilt today but I did not have to |
|
I do not get this failure on two different machines, both 0.7.0-rc1.5 on Fedora. I did versioninfo() |
|
That sounds like #28377 fixed this occurrence. Recent LLVM patches have not caused a recompilation of LLVM due to a sticky patch at the end, now they should retrigger a compilation when they get applied. |
|
I can still reproduce this after patches, so I'll take a look. |
|
@fredrikekre I got this error when trying to build After building from a fresh checkout, the MWE works as intended here: Julia Version 0.7.0-rc1.4
Commit 0ef8826 (2018-08-01 00:52 UTC)
Platform Info:
OS: Linux (x86_64-linux-gnu)
CPU: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.0 (ORCJIT, broadwell)
Environment:
JULIA_SHELL = /bin/bash |
|
On a machine where I did is fine, after a recompile with a partial rebuild of llvm it is still fine |
|
Looks like this one is architecture dependent. Reduced testcase ( |
|
Candidate patch at https://reviews.llvm.org/D50167. |
Keno
added a commit
that referenced
this issue
Aug 2, 2018
Keno
added a commit
that referenced
this issue
Aug 2, 2018
Keno
added a commit
that referenced
this issue
Aug 2, 2018
KristofferC
pushed a commit
that referenced
this issue
Feb 11, 2019
|
I had the same issue today on a fresh install (couple of weeks ago) of julia 1.4.1, on Ubuntu. Shouldn't this have already been corrected with the patch you mentioned? Or do I have to manually take some action? Here is the error message: |
|
The problem was that I was using the julia version provided by apt, which is apparently quite buggy. I switched to the version provided in julialang.org; it now works as expected. |
|
This was a LLVM bug so it was fixed in LLVM and not julia. This particular one is fixed on LLVM 9 but in general there are many other LLVM bugs that we are affected by requiring the use of our patched version of LLVM. You need to use a LLVM version with our patches and if you don't have that from your distro then you need to use the prebuilt binary from julialang.org. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This crashes Version 0.7.0-rc1.0, Win64
The text was updated successfully, but these errors were encountered: