public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug middle-end/97840] [11 regression] Bogus -Wmaybe-uninitialized
Date: Mon, 16 Nov 2020 21:37:04 +0100 [thread overview]
Message-ID: <20201116203704.GA88143@kam.mff.cuni.cz> (raw)
In-Reply-To: <bug-97840-4-FBJy9iz2UF@http.gcc.gnu.org/bugzilla/>
> I agree we should just rename default_is_empty_type to is_empty_type, export
> it, declare in tree.h and use it instead that complicated test. TYPE_EMPTY_P
> isn't something tree-ssa-uninit.c should care about, that is just whether the
> backend decided it will not be passed at all.
OK, perhaps I can realize this plan and commit tonight so we do not keep
boostrap blocked since it is a free day tomorrow (I will be hacking, but
perhaps Martin is not?).
Honza
next prev parent reply other threads:[~2020-11-16 20:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 16:14 [Bug middle-end/97840] New: " schwab@linux-m68k.org
2020-11-15 17:15 ` [Bug middle-end/97840] " hubicka at gcc dot gnu.org
2020-11-15 17:31 ` hubicka at gcc dot gnu.org
2020-11-15 17:57 ` hubicka at gcc dot gnu.org
2020-11-15 18:03 ` hubicka at gcc dot gnu.org
2020-11-16 1:22 ` msebor at gcc dot gnu.org
2020-11-16 7:27 ` rguenth at gcc dot gnu.org
2020-11-16 7:34 ` hubicka at gcc dot gnu.org
2020-11-16 15:32 ` cvs-commit at gcc dot gnu.org
2020-11-16 16:43 ` schwab@linux-m68k.org
2020-11-16 18:18 ` hubicka at gcc dot gnu.org
2020-11-16 20:11 ` jakub at gcc dot gnu.org
2020-11-16 20:18 ` Jan Hubicka
2020-11-16 20:18 ` hubicka at ucw dot cz
2020-11-16 20:30 ` jakub at gcc dot gnu.org
2020-11-16 20:37 ` Jan Hubicka [this message]
2020-11-16 20:37 ` hubicka at ucw dot cz
2020-11-16 21:54 ` msebor at gcc dot gnu.org
2020-11-16 22:01 ` Jan Hubicka
2020-11-16 22:01 ` hubicka at ucw dot cz
2020-11-17 3:02 ` cvs-commit at gcc dot gnu.org
2020-11-24 0:35 ` msebor 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=20201116203704.GA88143@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-bugzilla@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).