public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103700] Incomplete type not causing constraints to fail
Date: Wed, 22 Dec 2021 21:17:38 +0000 [thread overview]
Message-ID: <bug-103700-4-y3AbbXlLP9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103700-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103700
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Patrick Palka from comment #4)
> Hmm, can't we just check COMPLETE_TYPE_P in pointer_int_sum directly? Patch
> to that effect posted at
> https://gcc.gnu.org/pipermail/gcc-patches/2021-December/587300.html.
Yes that will work too. I was just quickly looking into how to fix it when I
write that comment really.
next prev parent reply other threads:[~2021-12-22 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 0:01 [Bug c++/103700] New: " pinskia at gcc dot gnu.org
2021-12-14 0:04 ` [Bug c++/103700] " pinskia at gcc dot gnu.org
2021-12-14 0:13 ` pinskia at gcc dot gnu.org
2021-12-14 1:00 ` pinskia at gcc dot gnu.org
2021-12-22 16:51 ` ppalka at gcc dot gnu.org
2021-12-22 17:42 ` ppalka at gcc dot gnu.org
2021-12-22 21:17 ` pinskia at gcc dot gnu.org [this message]
2021-12-27 14:05 ` cvs-commit at gcc dot gnu.org
2021-12-27 14:49 ` ppalka 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-103700-4-y3AbbXlLP9@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).