public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "Jonathan Wakely" <jwakely@redhat.com>,
	"Daniel Krügler" <daniel.kruegler@gmail.com>,
	"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: New hashtable power 2 rehash policy
Date: Wed, 25 May 2016 10:58:00 -0000	[thread overview]
Message-ID: <mvm1t4q364y.fsf@hawking.suse.de> (raw)
In-Reply-To: <5744C0EE.9050105@gmail.com> (=?utf-8?Q?=22Fran=C3=A7ois?= Dumont"'s message of	"Tue, 24 May 2016 23:00:30 +0200")

François Dumont <frs.dumont@gmail.com> writes:

>     * include/bits/c++config (_GLIBCXX14_USE_CONSTEXPR): New.

FAIL: ext/profile/mutex_extensions_neg.cc  (test for errors, line 324)
FAIL: ext/profile/mutex_extensions_neg.cc (test for excess errors)
Excess errors:
/usr/local/gcc/gcc-20160525/Build/ia64-suse-linux/libstdc++-v3/include/ia64-suse-linux/bits/c++config.h:326:4: error: #error illegal use of multiple inlined namespaces

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2016-05-25  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-23  8:27 François Dumont
2016-04-28 10:22 ` Jonathan Wakely
2016-04-28 12:30   ` Jonathan Wakely
2016-05-14 16:14   ` François Dumont
2016-05-14 17:06     ` Daniel Krügler
2016-05-17 20:28       ` François Dumont
2016-05-23 11:31         ` Jonathan Wakely
2016-05-24 23:56           ` François Dumont
2016-05-25 10:58             ` Andreas Schwab [this message]
2016-05-25 11:39               ` Jonathan Wakely
2016-05-14 17:18     ` Jonathan Wakely

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=mvm1t4q364y.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=daniel.kruegler@gmail.com \
    --cc=frs.dumont@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@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).