public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84774] [meta-bug] bogus/missing -Wrestrict
Date: Fri, 27 May 2022 08:41:35 +0000 [thread overview]
Message-ID: <bug-84774-4-5pdms1xoS2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-84774-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84774
Bug 84774 depends on bug 93519, which changed state.
Bug 93519 Summary: [9 Regression] bogus -Wrestrict for strcpy(d, s) call guarded by d != s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93519
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
next prev parent reply other threads:[~2022-05-27 8:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-84774-4@http.gcc.gnu.org/bugzilla/>
2020-03-15 3:20 ` egallager at gcc dot gnu.org
2020-03-20 9:53 ` rguenth at gcc dot gnu.org
2020-04-28 14:18 ` msebor at gcc dot gnu.org
2020-04-28 15:02 ` vincent.riviere at freesbee dot fr
2020-04-28 16:58 ` msebor at gcc dot gnu.org
2021-01-06 11:15 ` ebotcazou at gcc dot gnu.org
2021-09-18 22:48 ` msebor at gcc dot gnu.org
2021-10-26 23:03 ` msebor at gcc dot gnu.org
2021-11-23 10:16 ` pinskia at gcc dot gnu.org
2022-05-02 12:45 ` rguenth at gcc dot gnu.org
2022-05-25 16:31 ` msebor at gcc dot gnu.org
2022-05-27 8:41 ` rguenth at gcc dot gnu.org [this message]
2022-09-29 15:20 ` msebor at gcc dot gnu.org
2023-04-20 4:44 ` pinskia 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-84774-4-5pdms1xoS2@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: link
Be 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).