public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/87763] [9/10/11 Regression] aarch64 target testcases fail after r265398 Date: Fri, 09 Apr 2021 12:59:56 +0000 [thread overview] Message-ID: <bug-87763-4-Slk59jruJd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87763 rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|9.4 |12.0 Assignee|rsandifo at gcc dot gnu.org |unassigned at gcc dot gnu.org Status|ASSIGNED |NEW --- Comment #70 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- I've XFAILed the remaining two regressions for now, on the basis that this PR is open and tracking the problem. The bug is very much still there though, so the PR shouldn't be closed.
next prev parent reply other threads:[~2021-04-09 12:59 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-87763-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 11:58 ` [Bug rtl-optimization/87763] [9/10 " jakub at gcc dot gnu.org 2020-04-04 17:24 ` pinskia at gcc dot gnu.org 2021-04-09 12:43 ` [Bug rtl-optimization/87763] [9/10/11 " cvs-commit at gcc dot gnu.org 2021-04-09 12:59 ` rsandifo at gcc dot gnu.org [this message] 2022-05-06 8:30 ` [Bug rtl-optimization/87763] [9/10/11/12/13 " jakub at gcc dot gnu.org 2023-05-08 12:21 ` [Bug rtl-optimization/87763] [10/11/12/13/14 Regression] aarch64 target testcases fail after r265398 (gcc.target/aarch64/insv_1.c left) rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-87763-4-Slk59jruJd@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).