public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66962] [concepts] overloaded function causing memory blow-up and ICE
Date: Tue, 28 Jul 2015 21:16:00 -0000	[thread overview]
Message-ID: <bug-66962-4-H0r0AOOPtD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66962-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66962

--- Comment #16 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #15)
> So, converting A || B to !(!A && !B) will avoid the explosion at the cost of
> limiting subsumption.

Or even !!(A || B).


  parent reply	other threads:[~2015-07-28 21:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 18:40 [Bug c++/66962] New: " eric.niebler at gmail dot com
2015-07-23 20:39 ` [Bug c++/66962] " eric.niebler at gmail dot com
2015-07-23 20:44 ` trippels at gcc dot gnu.org
2015-07-23 20:59 ` Casey at Carter dot net
2015-07-23 21:05 ` eric.niebler at gmail dot com
2015-07-23 21:20 ` Casey at Carter dot net
2015-07-23 23:17 ` jason at gcc dot gnu.org
2015-07-24  9:23 ` trippels at gcc dot gnu.org
2015-07-24 19:11 ` eric.niebler at gmail dot com
2015-07-24 19:26 ` trippels at gcc dot gnu.org
2015-07-25 15:09 ` andrew.n.sutton at gmail dot com
2015-07-28 21:04 ` jason at gcc dot gnu.org
2015-07-28 21:16 ` jason at gcc dot gnu.org [this message]
2015-08-04 15:30 ` jason at gcc dot gnu.org
2015-08-04 15:39 ` jason at gcc dot gnu.org
2015-08-04 15:39 ` jason 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-66962-4-H0r0AOOPtD@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).