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 middle-end/95021] [10 Regression] Bogus -Wclobbered warning
Date: Thu, 14 Jan 2021 12:19:05 +0000 [thread overview]
Message-ID: <bug-95021-4-QMGbKHMHsB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95021-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95021
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |98676
--- Comment #16 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #15)
> > --- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
> > (In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #13)
> >> The failures reported in Comment 11 still exist on master, though.
> >> Maybe it's too early to remove 11 from the regression list?
> >
> > But that seems to be a new issue with the added testcases. Can you open a
> > separate PR for this?
>
> Done now as PR testsuite/98676. I was just a bit worried that the patch
> would be backported to the gcc-10 branch as is, together with the (so
> far ignored) failures.
Sure. We have dependencies to track this.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98676
[Bug 98676] gcc.target/i386/pr95021-1.c etc. FAIL
next prev parent reply other threads:[~2021-01-14 12:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 16:14 [Bug middle-end/95021] New: [10/11 " hjl.tools at gmail dot com
2020-05-09 19:19 ` [Bug middle-end/95021] " hjl.tools at gmail dot com
2020-05-11 1:26 ` hjl.tools at gmail dot com
2020-05-11 6:44 ` rguenth at gcc dot gnu.org
2020-05-12 13:08 ` hjl.tools at gmail dot com
2020-05-12 13:34 ` hjl.tools at gmail dot com
2020-05-12 13:50 ` rguenther at suse dot de
2020-05-12 20:08 ` hjl.tools at gmail dot com
2020-05-13 13:28 ` hjl.tools at gmail dot com
2020-05-17 17:13 ` cvs-commit at gcc dot gnu.org
2020-05-17 17:14 ` hjl.tools at gmail dot com
2020-05-18 19:01 ` ro at gcc dot gnu.org
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2021-01-14 8:43 ` [Bug middle-end/95021] [10 " rguenth at gcc dot gnu.org
2021-01-14 9:27 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-14 10:12 ` rguenth at gcc dot gnu.org
2021-01-14 11:56 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-14 12:19 ` rguenth at gcc dot gnu.org [this message]
2021-01-14 15:05 ` cvs-commit at gcc dot gnu.org
2021-01-14 15:46 ` hjl.tools at gmail dot com
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2023-07-07 8:50 ` 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-95021-4-QMGbKHMHsB@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).