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
* 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
* 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
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):
* 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.
*
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
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
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.
dsp
|^
|:
1906 | #endif
1907 | return SignalContext::WRITE;
| ~~
make[4]: *** [Makefile:614: sanitizer_linux.lo] Error 1
make[4]: Leaving directory
'/daten/riscv64/gcc/gcc-20200606/Build/riscv64-suse-linux/libsanitizer/sanitizer_common'
make[3]: *** [Makefile:
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
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
> 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
On June 6, 2020 6:17:49 AM GMT+02:00, Jason Merrill via Gcc-patches
wrote:
>The problem in this testcase comes from cloning the constructor into
>complete and base variants. When we clone the body the first time,
>walk_tree_1 calls copy_tree_body_r on the type of the artificial
>TYPE_DECL
>we
On June 5, 2020 6:38:10 PM GMT+02:00, Eric Botcazou
wrote:
>> I've installed it on trunk but will give it quite a while there
>before
>> backporting. I'm still somewhat worried about the
>>
>> /* ??? If we end up with a constant or a descriptor do not
>> record a MEM_EXPR. */
14 matches
Mail list logo