public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/26099] support for type traits is not available
Date: Sun, 27 Jan 2008 10:22:00 -0000	[thread overview]
Message-ID: <20080127051906.31787.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26099-3238@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from ghazi at gcc dot gnu dot org  2008-01-27 05:19 -------
>From the -fpic/-fPIC logfile:

has_nothrow_assign.exe: [...]/has_nothrow_assign.C:139: int main(): Assertion
`(__has_nothrow_assign(E) && f<E>() && My<E>().f() && My2<E>::trait &&
My3<E>().f())' failed.
FAIL: g++.dg/ext/has_nothrow_assign.C execution test

has_nothrow_constructor.exe: [...]/has_nothrow_constructor.C:100: int main():
Assertion `(__has_nothrow_constructor(E) && f<E>() && My<E>().f() &&
My2<E>::trait && My3<E>().f())' failed.
FAIL: g++.dg/ext/has_nothrow_constructor.C execution test

has_nothrow_copy.exe: [...]/has_nothrow_copy.C:129: int main(): Assertion
`(__has_nothrow_copy(E) && f<E>() && My<E>().f() && My2<E>::trait &&
My3<E>().f())' failed.
FAIL: g++.dg/ext/has_nothrow_copy.C execution test


-- 


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


  parent reply	other threads:[~2008-01-27  5:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-04 22:10 [Bug c++/26099] New: " stefaan dot deroeck at gmail dot com
2006-02-04 22:17 ` [Bug c++/26099] " pinskia at gcc dot gnu dot org
2006-02-04 23:14 ` stefaan dot deroeck at gmail dot com
2006-02-04 23:22 ` pinskia at gcc dot gnu dot org
2006-02-04 23:41 ` stefaan dot deroeck at gmail dot com
2006-02-04 23:41 ` pcarlini at suse dot de
2006-02-05  3:56 ` gdr at integrable-solutions dot net
2006-02-05 10:22 ` pcarlini at suse dot de
2006-11-21 18:38 ` pcarlini at suse dot de
2007-03-30 19:46 ` paolo at gcc dot gnu dot org
2008-01-27 10:09 ` ghazi at gcc dot gnu dot org
2008-01-27 10:22 ` ghazi at gcc dot gnu dot org [this message]
2008-01-27 12:36 ` pcarlini at suse dot de
2008-01-27 13:27 ` rguenth at gcc dot gnu dot org
2008-01-27 14:14 ` pcarlini at suse dot de
2008-01-27 19:21 ` ghazi at gcc dot gnu dot org
2008-01-27 19:28 ` pcarlini at suse dot de
2008-01-27 19:34 ` pcarlini at suse dot de
2008-01-27 20:48 ` ghazi at gcc dot gnu dot org
2008-01-27 21:10 ` ghazi at gcc dot gnu dot org
2008-01-27 21:11 ` pcarlini at suse dot de
2008-01-27 21:18 ` pcarlini at suse dot de
2008-01-27 21:33 ` pcarlini at suse dot de
2008-01-27 21:36 ` ghazi at gcc dot gnu dot org
2008-01-27 22:04 ` ghazi at gcc dot gnu dot org
2008-01-27 22:27 ` ghazi at gcc dot gnu dot org
2008-01-27 22:49 ` pcarlini at suse dot de
2008-01-27 22:56 ` ghazi at gcc dot gnu dot org
2008-01-27 22:57 ` pcarlini at suse dot de
2009-11-22 17:54 ` ghazi at gcc dot gnu dot org
2009-11-22 19:14 ` paolo dot carlini at oracle dot com
2009-11-22 19:14 ` paolo dot carlini at oracle dot com
     [not found] <bug-26099-4@http.gcc.gnu.org/bugzilla/>
2011-08-31 17:38 ` paolo.carlini at oracle dot com
2014-09-30 17:44 ` paolo.carlini at oracle dot com
2014-10-01  8:06 ` paolo.carlini at oracle dot com
2014-10-01  8:21 ` 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=20080127051906.31787.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).