Hi Iain
On 11/10/2023 09:30, Iain Sandoe wrote:
Hi François,
On 11 Oct 2023, at 05:49, François Dumont wrote:
On 08/10/2023 15:59, Iain Sandoe wrote:
On 23 Sep 2023, at 21:10, François Dumont wrote:
I'm eventually fixing those tests the same way we manage this problem in
li
On 08/10/2023 15:59, Iain Sandoe wrote:
Hi François,
On 23 Sep 2023, at 21:10, François Dumont wrote:
I'm eventually fixing those tests the same way we manage this problem in
libstdc++ testsuite.
testsuite: Add optional libstdc++ version namespace in expected diagnostic
Indeed ! Here is the right one.
On 03/10/2023 11:52, Jonathan Wakely wrote:
On Mon, 2 Oct 2023 at 18:07, François Dumont wrote:
Hi
Gentle reminder for this minor patch.
It looks like you attached the wrong patch.
Thanks
On 23/09/2023 22:10, François Dumont wrote:
I'm eventually f
Hi
Gentle reminder for this minor patch.
Thanks
On 23/09/2023 22:10, François Dumont wrote:
I'm eventually fixing those tests the same way we manage this problem
in libstdc++ testsuite.
testsuite: Add optional libstdc++ version namespace in expected
diagnostic
When libstdc
I'm eventually fixing those tests the same way we manage this problem in
libstdc++ testsuite.
testsuite: Add optional libstdc++ version namespace in expected
diagnostic
When libstdc++ is build with
--enable-symvers=gnu-versioned-namespace diagnostics are
showing this namespace, c
3 09:22, Thomas Schwinge wrote:
Hi!
On 2023-09-20T07:08:25+0200, François Dumont via Gcc wrote:
I've configured libstdc++ with --enable-symvers=gnu-versioned-namespace
I can't comment on that option...
and run make check-c++.
A number of failures are like this one:
/home/fdumont/de
I've configured libstdc++ with --enable-symvers=gnu-versioned-namespace
and run make check-c++.
A number of failures are like this one:
/home/fdumont/dev/gcc/git/gcc/testsuite/g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C:
In function 'coro1 f()':
/home/fdumont/dev/gcc/git/gcc/testsuite/g++
Hi
Do not hesitate to dig into library doc. Especially this page:
https://gcc.gnu.org/onlinedocs/gcc-8.1.0/libstdc++/manual/manual/test.html
You can also find it in your git clone in /libstdc++-v3/doc/html.
You'll see also how to run test in different std modes like --std=c++98
to catch the k
On 26/03/2023 04:01, Ken Matsui via Libstdc++ wrote:
On Sat, Mar 25, 2023 at 5:38 AM Marc Glisse wrote:
On Sat, 25 Mar 2023, Ken Matsui via Gcc wrote:
Built-in trait naming simply adds two underscores (__) to the original
trait name. However, the same names are already in use for some
built
and why applying the patch in the first place failed.
François
On 13/06/2018 15:24, Jonathan Wakely wrote:
On 13/06/18 13:42 +0200, Paolo Carlini wrote:
Hi,
On 13/06/2018 08:11, François Dumont wrote:
On 12/06/2018 23:26, Martin Sebor wrote:
Bootstrap fails in libstdc++ with the following er
Hi,
On 13/06/2018 08:11, François Dumont wrote:
On 12/06/2018 23:26, Martin Sebor wrote:
Bootstrap fails in libstdc++ with the following error.
I haven't investigated it much except to take a peek
at recent libstdc++ commits where r261525 looks like it
introduced __glibcxx_check_can_incremen
On 12/06/2018 23:26, Martin Sebor wrote:
Bootstrap fails in libstdc++ with the following error.
I haven't investigated it much except to take a peek
at recent libstdc++ commits where r261525 looks like it
introduced __glibcxx_check_can_increment_range, so it
seems like it might have something to
On 15/12/2017 03:20, Jonathan Wakely wrote:
FAIL: 23_containers/vector/cons/destructible_neg.cc (test for errors, line 35)
FAIL: 23_containers/vector/cons/destructible_neg.cc (test for errors, line 41)
I had a look at this remaining issue. The compilation result is:
In file included from
/h
Hello
There are at the moment several failures in the libstdc++ testsuite
when run in debug mode (_GLIBCXX_DEBUG). This is so because debug
assertions are not const expressions. Several debug assertions have been
removed because of this issue.
So is there a way to define a function as to
think that proposing a generalization of DR 1402 would be nice
to simplify code but I now realize that the core issue is a compiler
limitation. I add gcc mailing list just in case someone would like to react.
François
On 03/22/2013 09:36 PM, François Dumont wrote:
Hi
I completed my little st
Hi
While working on hashtable I have added this kind of expression to
decide to cache or not hash code:
template,
class _Pred = std::equal_to<_Value>,
class _Alloc = std::allocator<_Value>,
bool __cache_hash_code =
__not_<__and_,
Hi
My latest build finally succeeded, I have simply removed everything
reported by 'svn status' as unknown and done a re-configuration and build.
Thanks for your help and sorry for the noise.
François
On 11/05/2010 01:09 AM, Dave Korn wrote:
On 04/11/2010 23:27, Paolo Carlini wrote:
Thanks for your help.
I just try to clean all I could in the gcc folder but I still have the
same problem. Here is the way I configure with the result:
[...@localhost gcc]$ ./configure --prefix=/home/fdt --with-mpc=/home/fdt
--with-mpfr=/home/fdt --with-gmp=/home/fdt --enable-languages=c++
c
18 matches
Mail list logo
