Closed rohel01 closed 9 months ago
I have just found out the GDB disassemble
command
The illegal instruction is:
=> 0x0000000000404358 <+104>: aesd v1.16b, v2.16b
Ok, adding the following to my cargo config file solve the issue. Sorry for the noise!
[target.aarch64-unknown-linux-gnu]
rustflags = [
#...
"-C",
"target-feature=-aes",
#...
]
Hello,
I am cross compiling a bevy application for a ARMA53 CPU using the
aarch64-unknown-linux-gnu
target. Since I am only targeting that HW, I tried to refine the build arguments for my specific needs. If I add "target-cpu=cortex-a53" to my cargo config, the resulting executable no longer runs on the target.Looking at the backtrace in GDB, it crashes when executing hashbrown functions. I narrowed it down to this simple program
I do not understand this issue. Can you help?
I am using cargo
1.72.0-nightly (4cebd130e 2023-06-21)
My
.cargo/config.toml
is:I am linking with a Yocto generated SDK.