I can confirm that gem5 can load a libtorch binary on v23.0.0.1. I was
able to run the binary on a Ubuntu 22.04.1.
Also, I've run git bisect to find the commit that fixes the bug. Here is
the git bisect log:
---
# old: [5fa484e2e02604ad3a5bf01f35ad1f97ca6d17b8] misc: Merge the v22.1
release
I tried to reproduce this for myself but I failed to do so (using v23.0.0.1, `build/ALL/gem5.opt`).. Attached is a tarball of the files i used. The steps I carried out can be found on the the "README.md" file. I'm not sure what I'm missing but my execution prints "Hello World" successfully.The
Hi,
Yes, the binary works correctly on my host. Also, I was able to load it
in an Ubuntu 18 FS simulation using gem5.
Before the panic condition is triggered, an exception is thrown, which
does not occur when running on host. I tried to debug gem5 by running it
on gdb and using "catch
For what it's worth, one of the students working with me (Marco, CC'd) is
having the same failure right now for the head of develop (plus this fix:
https://github.com/gem5/gem5/pull/99), except for a tiny GPU microbenchmark
that definitely is not using PyTorch or any higher level library.
We are
I’m afraid I don’t know exactly what’s causing this error, but just to make
sure, the binary you built and as a `CustomResource` executes on your host?
This looks like an error coming from PyTorch, not the simulator. That being
said, I don’t understand why "build/X86/sim/faults.cc:61: panic:
