Conversation
|
Any idea why the compiler isn't working? I naively copied the x86_64 version and just replaced x86_64 with aarch64, not sure what other changes need to be made. |
|
@scottwittenburg any thoughts on this one? |
|
I think again here, you want to specify compiler and arch as part of a spec matrix. It seems by default the concretizer picked Also I noticed at least one of the pipeline generation jobs had |
|
It's working! Now to fix some package build issues... |
|
First up: intel-oneapi-tbb @rscohn2 does intel-oneapi-tbb not work on aarch64? If so I can add a conflict. |
|
Next: valgrind Tried adding a newer version of valgrind in #34436, if we're lucky that may help. If not, I'll just disable it in the PyTorch package. I'm guessing that's the only thing that needs it. |
|
py-tensorboard-data-server issues fixed in #34437 and tensorflow/tensorboard#6101 |
5cfe9b6 to
7f66edc
Compare
3268381 to
8d1759b
Compare
|
Next round of build failures. LLVM: |
|
PyTorch: Looks like the same issue as google/XNNPACK#1551 and https://discuss.pytorch.org/t/installation-from-source-on-aarch64-meet-march-armv8-2-a-fp16-dotprod-failure/162336/2. Solution is to use a newer compiler. Not really sure how to get a newer GCC on these images though... Update: easier solution is just to disable XNNPACK |
0650c39 to
1a2c300
Compare
1a2c300 to
076ce16
Compare
|
I could have sworn PyTorch was building before... New build issue: |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
6cf9c15 to
341b5bb
Compare
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
This is outdated after the CI refactor. I'll create a new PR when I get a chance. |
Copied our existing CI from x86_64 to aarch64