public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugs at sehe dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51829] decltype() deduces non-const but only in a template
Date: Sun, 13 May 2012 03:38:00 -0000 [thread overview]
Message-ID: <bug-51829-4-ZtbwJXAzjh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51829-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51829
--- Comment #5 from Seth Heeren <bugs at sehe dot nl> 2012-05-13 00:05:00 UTC ---
On 13-05-12 00:46, paolo.carlini at oracle dot com wrote:
> Still waiting.
Really. Well, to be honest, I can't afford to spend even more time
minimizing that any further. I have to pick priorities.
For quick win, of course, you could check whether the problem still
exists with GCC 4.7 or dev versions. It might have been fixed in the
process of other development/fixes.
God knows I had spent over 6 hours trying to minimize that by manually
decimating the preprocessed sources even before initially posting the
report. And it wasn't even my own bug; it was a support call on the
[spirit-general] list.
I don't think it is worth my time to **learn** how to further reduce the
testcase further, since that seems to be a highly specialized craft
and, tools could do a good job.
I'd be rather surprised if the GCC team didn't have just such tools, as
well as people skilled and experienced in using them.
All of the above would require a lot of time on my side, and sadly I
don't have it.
Regards
Seth
next prev parent reply other threads:[~2012-05-13 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 21:30 [Bug c++/51829] New: " bugs at sehe dot nl
2012-01-11 21:32 ` [Bug c++/51829] " bugs at sehe dot nl
2012-01-12 0:30 ` bugs at sehe dot nl
2012-01-13 12:05 ` paolo.carlini at oracle dot com
2012-05-12 23:04 ` paolo.carlini at oracle dot com
2012-05-13 3:38 ` bugs at sehe dot nl [this message]
2012-05-13 9:37 ` glisse at gcc dot gnu.org
2012-10-14 15:49 ` paolo.carlini at oracle dot com
2012-10-15 21:14 ` bugs at sehe dot nl
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-51829-4-ZtbwJXAzjh@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).