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: Thu, 23 Jul 2015 23:17:00 -0000 [thread overview]
Message-ID: <bug-66962-4-73zbEVwoeS@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
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-07-23
Ever confirmed|0 |1
--- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Casey Carter from comment #5)
> (In reply to Markus Trippelsdorf from comment #2)
> > /usr/local/gcc-concepts/include/c++/6.0.0/initializer_list:47:11: fatal
> > error: definition of std::initializer_list does not match #include
> > <initializer_list>
>
> This is because the definition of std::initializer_list in the preprocessed
> source doesn't agree with your compiler's - or mine - notion of what
> std::initializer_list should be.
The issue is just 32-bit vs 64-bit size_t. I'm able to reproduce the bug with
the original testcase using the -m32 flag.
The testcase in comment #7 has different requirements on iter_swap2, so it
doesn't run into this bug. It was crashing because my recent patch needed an
additional NULL check, which I have now added.
The problem in Eric's testcases seems to be that decompose_assumptions is
consuming an extreme amount of memory, I think because left_disjunction causes
the process to have quadratic complexity. So I think we need an algorithmic
change here. Andrew?
next prev parent reply other threads:[~2015-07-23 23:17 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 [this message]
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
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-73zbEVwoeS@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).