[Bug target/86802] riscv port needs updating for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86802 Richard Earnshaw changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID

[Bug target/86802] riscv port needs updating for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86802 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |INVALID Status|NEW

[Bug target/86802] riscv port needs updating for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86802 Jeffrey A. Law changed: What|Removed |Added Assignee|law at gcc dot gnu.org |unassigned at gcc dot gnu.org -

[Bug target/86802] riscv port needs updating for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86802 Andrew Pinski changed: What|Removed |Added Assignee|wilson at gcc dot gnu.org |unassigned at gcc dot gnu.org

[Bug target/86802] riscv port needs updating for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86802 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug target/86802] riscv port needs updating for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86802 --- Comment #2 from Richard Earnshaw --- I think the best thing to do in that case is to leave the port unfixed until such time as you know what mitigation is appropriate. That way the compiler will not define __HAVE_SPECULATION_SAFE_VALUE and u

[Bug target/86802] riscv port needs updating for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86802 Jim Wilson changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|