On 21/10/16 21:21 +0200, François Dumont wrote:
Hi
I configured libstdc++ to use gnu-version-namespace and there are
a number of failures, see below. But none of them related to this
patch so is it ok to commit ?
Yes, OK to commit - it doesn't make the test results any worse than
they wer
Some quick comments before I go offline ...
On 21/10/16 21:21 +0200, François Dumont wrote:
Hi
I configured libstdc++ to use gnu-version-namespace and there are
a number of failures, see below. But none of them related to this
patch so is it ok to commit ?
The results:
FAIL: libstdc++
Hi
I configured libstdc++ to use gnu-version-namespace and there are a
number of failures, see below. But none of them related to this patch so
is it ok to commit ?
The results:
FAIL: libstdc++-abi/abi_check
3709 symbols reported as added. I don't know what to think about
it. I see
On 01/10/16 14:22 +0200, François Dumont wrote:
On 30/09/2016 17:40, Jonathan Wakely wrote:
On 29/09/16 21:59 +0200, François Dumont wrote:
Hi
I think _GLIBCXX_BEGIN_NAMESPACE_ALGO should default to
_GLIBCXX_BEGIN_NAMESPACE_VERSION when parallel mode is not active.
Same for _GLIBCXX_BEGIN_
On 30/09/2016 17:40, Jonathan Wakely wrote:
On 29/09/16 21:59 +0200, François Dumont wrote:
Hi
I think _GLIBCXX_BEGIN_NAMESPACE_ALGO should default to
_GLIBCXX_BEGIN_NAMESPACE_VERSION when parallel mode is not active.
Same for _GLIBCXX_BEGIN_NAMESPACE_CONTAINER, no ?
Hmm, yes, I think th
On 29/09/16 21:59 +0200, François Dumont wrote:
Hi
I think _GLIBCXX_BEGIN_NAMESPACE_ALGO should default to
_GLIBCXX_BEGIN_NAMESPACE_VERSION when parallel mode is not active.
Same for _GLIBCXX_BEGIN_NAMESPACE_CONTAINER, no ?
Hmm, yes, I think this is correct, otherwise we're missing the VE
