Re: [PATCH] hurd: libgcc unwinding support over signal trampolines

2020-06-06 Thread Samuel Thibault
Hello, Any news on this? Samuel Samuel Thibault, le ven. 29 mai 2020 13:46:50 +0200, a ecrit: > Hello, > > libgcc is currently missing the support for unwinding over signal > trampolines on GNU/Hurd. The attached patch implements it. > > Samuel > hurd: libgcc unwinding support over signal tra

[PATCH 3/4] Adjust wait logic to limit spurious eval of wait predicate.

2020-06-06 Thread Thomas Rodgers
* include/bits/atomic_wait.h (__waiters::_M_do_wait): adjust wakeup logic. --- libstdc++-v3/include/bits/atomic_wait.h | 16 +++- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/libstdc++-v3/include/bits/atomic_wait.h b/libstdc++-v3/include/bits/atomic_

[PATCH] Remove binary_semaphore implementation from stop_token

2020-06-06 Thread Thomas Rodgers
* include/std/stop_token: Remove local binary_semaphore implementation. (_Stop_state_t::_M_do_try_lock): Use __thread_yield() from bits/atomic_wait.h. --- libstdc++-v3/include/std/stop_token | 40 ++--- 1 file changed, 2 insertions(+), 38 deletio

[PATCH] Add support for C++20 barriers

2020-06-06 Thread Thomas Rodgers
* include/Makefile.am (std_headers): Add new header. * include/Makefile.in: Regenerate. * include/std/barrier: New file. * testsuite/30_thread/barrier/1.cc: New test. * testsuite/30_thread/barrier/2.cc: Likewise. * testsuite/30_thread/barrier/arrive_a

[PATCH] Add C++2a synchronization support

2020-06-06 Thread Thomas Rodgers
Add support for - atomic wait/notify_one/notify_all counting_semaphore binary_semaphore latch * include/Makefile.am (bits_headers): Add new header. * include/Makefile.in: Regenerate. * include/bits/atomic_base.h (__atomic_base<_Itp>::wait): D

[PATCH] PR fortran/95091 - Buffer overflows with submodules and long symbols

2020-06-06 Thread Harald Anlauf
There's another case of buffer overflows when F2008 submodules are used. Buffer sizes are further increased, and checks for overflow are put into place. OK for master? I intend to backport to 10 and 9, since I believe the patch is safe. Thanks, Harald PR fortran/95091 - Buffer overflows with s

[PATCH] avoid -Wmaybe-uninitialized in reload_cse_simplify_operands (PR bootstrap/95555)

2020-06-06 Thread Martin Sebor via Gcc-patches
A recent enhancement to the uninitialized access coverage to include dynamically allocated objects, including alloca and VLAs, triggers an expected instance of -Wmaybe-uninitialized on powerpc64-linux in reload_cse_simplify_operands where an element of an XALLOCAVEC- allocated array is read before

Fix ICE in ODR enum streaming

2020-06-06 Thread Jan Hubicka
Hi, this fixes ICE when enum value does not fit HOST_WIDE_INT. Bootstrapped/retested x86_64-linux, comitted. gcc/ChangeLog: 2020-06-06 Jan Hubicka PR lto/95548 * ipa-devirt.c (struct odr_enum_val): Turn values to wide_int. (ipa_odr_summary_write): Update streaming.

Re: [PATCH] Libsanitizer: merge from master.

2020-06-06 Thread Andreas Schwab
nitizer_common/sanitizer_linux.cpp:1904:16: error: expected ':' before 'case' 1904 | case 0b00'101: // c.fsd |^ |: 1905 | case 0b10'101: // c.fsdsp | ../../../../libsanitizer/sanitizer_common/sanitizer_linux.cpp:1905:7: error

[committed] wwwdocs: Add markup to the GCC 11 -dump* and -aux* revamp.

2020-06-06 Thread Gerald Pfeifer
This is a little follow up to Alexandre's note for the GCC 11 release notes - we usually mark command-line options as . Pushed. Gerald --- htdocs/gcc-11/changes.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html i

[PATCH] x86: Improve expansion of __builtin_parity

2020-06-06 Thread Roger Sayle
This patch changes the way that __builtin_parity is expanded in i386.md. This changes the code generated for the function: int test(unsigned char a) { unsigned char x = a + 1; return __builtin_parity(x); } from this before the patch: test: addl$1, %edi movzb

Re: [PATCH RFA] tree-inline: Fix VLA handling [PR95552]

2020-06-06 Thread Eric Botcazou
> This patch fixes walk_tree_1 to call the function on the TYPE_DECL, as we do > for other decls of a DECL_EXPR. Where is that done exactly? The only case handled by DECL_EXPR is TYPE_DECL. The correct thing to do is clearly implied by the first line in your patch. -- Eric Botcazou