public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/100407] New test cases attr-retain-*.c fail after their introduction in r11-7284 Date: Thu, 24 Feb 2022 22:07:10 +0000 [thread overview] Message-ID: <bug-100407-4-ktO45Ak3Bo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100407-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100407 pthaugen at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pthaugen at gcc dot gnu.org Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #15 from pthaugen at gcc dot gnu.org --- Fixed.
prev parent reply other threads:[~2022-02-24 22:07 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-04 1:21 [Bug testsuite/100407] New: " seurer at gcc dot gnu.org 2021-05-04 12:17 ` [Bug testsuite/100407] " hjl.tools at gmail dot com 2021-06-02 19:42 ` seurer at gcc dot gnu.org 2021-06-02 19:52 ` hjl.tools at gmail dot com 2021-06-02 23:38 ` seurer at gcc dot gnu.org 2021-06-03 1:15 ` hjl.tools at gmail dot com 2021-06-03 1:17 ` hjl.tools at gmail dot com 2021-06-03 1:19 ` hjl.tools at gmail dot com 2021-06-03 15:15 ` seurer at gcc dot gnu.org 2021-06-03 15:17 ` seurer at gcc dot gnu.org 2021-06-03 15:38 ` hjl.tools at gmail dot com 2021-06-08 16:58 ` bergner at gcc dot gnu.org 2021-06-08 19:43 ` segher at gcc dot gnu.org 2021-06-09 7:15 ` amodra at gmail dot com 2022-02-24 21:35 ` cvs-commit at gcc dot gnu.org 2022-02-24 22:07 ` pthaugen 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-100407-4-ktO45Ak3Bo@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).