public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefansf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/115261] [11/12/13/14/15 regression] FAIL: gcc.target/s390/vector/vec-abi-vararg-1.c Date: Mon, 24 Jun 2024 08:12:07 +0000 [thread overview] Message-ID: <bug-115261-4-OGSGU3Ly7f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115261-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115261 Stefan Schulze Frielinghaus <stefansf at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Stefan Schulze Frielinghaus <stefansf at gcc dot gnu.org> --- Fixed on mainline.
prev parent reply other threads:[~2024-06-24 8:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-28 14:49 [Bug rtl-optimization/115261] New: " stefansf at gcc dot gnu.org 2024-05-29 7:35 ` [Bug rtl-optimization/115261] [11/12/13/14/15 regression] " rguenth at gcc dot gnu.org 2024-05-29 10:40 ` stefansf at gcc dot gnu.org 2024-06-17 6:37 ` cvs-commit at gcc dot gnu.org 2024-06-24 8:12 ` stefansf at gcc dot gnu.org [this message]
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-115261-4-OGSGU3Ly7f@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).