1 files changed, 75 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/performance/1880722 b/results/classifier/zero-shot/118/performance/1880722
new file mode 100644
index 000000000..4c9170f0b
--- /dev/null
+++ b/results/classifier/zero-shot/118/performance/1880722
@@ -0,0 +1,75 @@
+performance: 0.864
+graphic: 0.686
+user-level: 0.535
+architecture: 0.526
+device: 0.511
+mistranslation: 0.499
+permissions: 0.458
+files: 0.450
+semantic: 0.449
+debug: 0.436
+hypervisor: 0.426
+register: 0.421
+PID: 0.416
+network: 0.405
+peripherals: 0.399
+virtual: 0.396
+risc-v: 0.378
+VMM: 0.378
+vnc: 0.359
+x86: 0.348
+TCG: 0.344
+i386: 0.340
+socket: 0.329
+ppc: 0.327
+KVM: 0.307
+kernel: 0.305
+assembly: 0.276
+arm: 0.260
+boot: 0.253
+
+Problems related to checking page crossing in use_goto_tb()
+
+The discussion that led to this bug discovery can be found in this 
+mailing list thread:
+https://lists.nongnu.org/archive/html/qemu-devel/2020-05/msg05426.html
+
+A workaround for this problem would be to check for page crossings for 
+both the user and system modes in the use_goto_tb() function across 
+targets. Some targets like "hppa" already implement this fix but others
+don't.
+
+To solve the root cause of this problem, the linux-user/mmap.c should 
+be fixed to do all the invalidations required. By doing so, up to 6.93% 
+performance improvements will be achieved.
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting older bugs to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" within the next 60 days (otherwise it will get
+closed as "Expired"). We will then eventually migrate the ticket auto-
+matically to the new system.
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+