public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebor at roguewave dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/27527] invalid types produced out of argument deduction (SFINAE bug)
Date: Fri, 12 May 2006 16:31:00 -0000	[thread overview]
Message-ID: <20060512163032.1307.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27527-1186@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from sebor at roguewave dot com  2006-05-12 16:30 -------
Created an attachment (id=11446)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11446&action=view)
Corrected test program exercising SFINAE.

After modifying the test program from comment #1 to correct these problems most
test cases still fail (with both gcc and EDG eccp).
The modified test program is in the attachment.

Here's a script I used to run the test program:

$ (c=1; \
   while [ $c -lt 17 ]; do \
       printf "%s: " "$c"; \
       gcc -DCASE=$c t.cpp 2>/dev/null; \
       if [ $? -eq 0 ]; then echo okay; else echo ERROR; fi; \
       c=`expr $c + 1`; \
   done) 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27527


  parent reply	other threads:[~2006-05-12 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 21:28 [Bug c++/27527] New: " sebor at roguewave dot com
2006-05-10  1:07 ` [Bug c++/27527] " sebor at roguewave dot com
2006-05-12 16:27 ` sebor at roguewave dot com
2006-05-12 16:31 ` sebor at roguewave dot com [this message]
2006-05-26 15:14 ` bangerth at dealii dot org
     [not found] <bug-27527-4@http.gcc.gnu.org/bugzilla/>
2011-09-27 22:20 ` paolo.carlini at oracle dot com
2011-09-28 19:38 ` jason at gcc dot gnu.org
2011-09-28 21:22 ` paolo.carlini at oracle dot com
2011-12-30 13:13 ` paolo.carlini at oracle dot com

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=20060512163032.1307.qmail@sourceware.org \
    --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).