public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yufeng at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46003] cond5.C fails for ARM EABI tests.
Date: Thu, 09 Jun 2011 17:16:00 -0000	[thread overview]
Message-ID: <bug-46003-4-YaoHw7S5Uh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46003-4@http.gcc.gnu.org/bugzilla/>

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

Yufeng Zhang <yufeng at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|yufeng.zhang at arm dot com |

--- Comment #8 from Yufeng Zhang <yufeng at gcc dot gnu.org> 2011-06-09 17:15:14 UTC ---
(In reply to comment #6)
> Shouldn't this be fixed by the commit of  PR c++/49134 ?

(In reply to comment #7)
> Test g++.dg/template/cond5.C starts passing for arm-none-linux-gnueabi with
> r174682, the fix for PR49134 mentioned in comment 6.

Thanks for pointing out the related bug fix. The test case
g++.dg/template/cond5.C indeed starts 'passing' now, as the fix for PR
c++/49134 has essentially loosened the same checking where assertion had blown
up. I'll spend some more time looking into the underlying issue and put more
information here later. If it turns out to be necessary, I'll close this
bugzilla and open a new one for it.


  parent reply	other threads:[~2011-06-09 17:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 11:48 [Bug c++/46003] New: " ramana at gcc dot gnu.org
2010-12-03  9:32 ` [Bug c++/46003] " ramana at gcc dot gnu.org
2011-01-25 21:28 ` yufeng.zhang at arm dot com
2011-02-10 17:36 ` yufeng.zhang at arm dot com
2011-05-26  2:13 ` janis at gcc dot gnu.org
2011-06-03 10:49 ` yufeng at gcc dot gnu.org
2011-06-08 10:43 ` dodji at gcc dot gnu.org
2011-06-08 15:49 ` janis at gcc dot gnu.org
2011-06-09 17:16 ` yufeng at gcc dot gnu.org [this message]
2012-12-11 17:53 ` ramana 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-46003-4-YaoHw7S5Uh@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).