diff options
Diffstat (limited to 'results/classifier/118/none/1623')
| -rw-r--r-- | results/classifier/118/none/1623 | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/results/classifier/118/none/1623 b/results/classifier/118/none/1623 new file mode 100644 index 000000000..adca5a18f --- /dev/null +++ b/results/classifier/118/none/1623 @@ -0,0 +1,39 @@ +graphic: 0.247 +device: 0.222 +semantic: 0.109 +socket: 0.060 +mistranslation: 0.047 +architecture: 0.041 +boot: 0.037 +arm: 0.035 +debug: 0.033 +kernel: 0.033 +PID: 0.030 +network: 0.027 +performance: 0.026 +permissions: 0.025 +risc-v: 0.024 +virtual: 0.023 +i386: 0.018 +x86: 0.017 +register: 0.016 +vnc: 0.016 +ppc: 0.015 +user-level: 0.014 +files: 0.013 +TCG: 0.010 +peripherals: 0.007 +VMM: 0.007 +hypervisor: 0.004 +assembly: 0.002 +KVM: 0.002 + +vec_lde and vec_expte semi-randomly produce the wrong results +Description of problem: +I found that while implementing the Altivec support for the rust [stdarch](https://github.com/rust-lang/stdarch). +Steps to reproduce: +1. Install rust nightly (e.g. using https://rustup.rs/) +2. `git clone https://github.com/rust-lang/stdarch` +3. You need to either cross compile or compile and run the tests for `crates/core_arch`. +Additional information: +Both `valgrind` and running on power9 produce the correct results |