On these platforms, one of the instances of the constructor generated in
test_strcpy_bounds_memarray_range is put into the constant pool so the strlen
pass cannot do its magic.
Tested on visium-elf, SPARC64 and x86-64/Linux, applied on the mainline.
2018-01-16 Eric Botcazou
* c-c++
This test fails on strict-alignment platforms because a call to memcpy is not
turned into a simple move and thus yields an additional warning:
warning: '__builtin_memcpy' writing 4 bytes into a region of size 0 overflows
the destination [-Wstringop-overflow=]
The attached patch tweaks the test
Hi!
On Tue, Jan 16, 2018 at 11:57:14AM -0800, Carl Love wrote:
> The following patch contains fixes for the stxvl and lxvl instructions
> and XL_LEN_R builtin that were found while adding additional Power 9
> test cases for the various load and store builtins. The new tests in
> builtins-5-p9-run
Like my recent patch for 83186, we were missing a build_non_dependent_expr.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 5c63951fe987acd133bf59532896a4b397f49f12
Author: Jason Merrill
Date: Tue Jan 16 17:19:22 2018 -0500
PR c++/83714 - ICE checking return in template.
This test fails on Visium because of 3 separate issues. The first one is
benign, it's a warning about a pointer mismatch between int32_t* and int*
(On most newlib targets, int32_t is long int instead of int) in the test.
The other 2 are in the code itself (but cancel each other on most targets):
On 01/16/2018 03:39 PM, Eric Botcazou wrote:
On these platforms, one of the instances of the constructor generated in
test_strcpy_bounds_memarray_range is put into the constant pool so the strlen
pass cannot do its magic.
Tested on visium-elf, SPARC64 and x86-64/Linux, applied on the mainline.
On 01/16/2018 03:54 PM, Eric Botcazou wrote:
This test fails on strict-alignment platforms because a call to memcpy is not
turned into a simple move and thus yields an additional warning:
warning: '__builtin_memcpy' writing 4 bytes into a region of size 0 overflows
the destination [-Wstringop-ov
On 01/16/2018 02:32 PM, Jakub Jelinek wrote:
On Tue, Jan 16, 2018 at 01:36:26PM -0700, Martin Sebor wrote:
--- gcc/gimple-ssa-warn-restrict.c (revision 256752)
+++ gcc/gimple-ssa-warn-restrict.c (working copy)
@@ -384,6 +384,12 @@ builtin_memref::builtin_memref (tree expr, tree si
.. regression testing actually completed successfully.
Paolo.
I misunderstood how the dist codes are handled in block type 1. I
also think'od the length of the codes for the default table. This
patch fixes these problems, along with a test case that exposes them.
Bootstrapped and ran libbacktrace tests on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
20
We need to apply CEIL to the case where mode != BLKmode.
Committed to trunk.
Dave
--
John David Anglin dave.ang...@bell.net
2018-01-16 John David Anglin
* config/pa/pa.c (pa_function_arg_size): Apply CEIL to GET_MODE_SIZE
return value.
Index: config/pa/pa.c
===
This shortens and simplifies a number of lines in ASM_DECLARE_FUNCTION_NAME.
Committed to trunk.
Dave
--
John David Anglin dave.ang...@bell.net
2018-01-16 John David Anglin
* config/pa/som.h (ASM_DECLARE_FUNCTION_NAME): Cleanup type and mode
variables.
Index: config/pa/so
When I defined MALLOC_ABI_ALIGNMENT, I inadvertently changed the default
alignment for
various hppa*-*-*bsd* targets. Nick Hudson is still maintaining the
netbsd target.
This patch corrects the default malloc alignment for 32-bit targest and
moves the linux special
case to its own file.
Com
On 17.01.2018 02:52, John David Anglin wrote:
> When I defined MALLOC_ABI_ALIGNMENT, I inadvertently changed the default
> alignment for
> various hppa*-*-*bsd* targets. Nick Hudson is still maintaining the
> netbsd target.
>
> This patch corrects the default malloc alignment for 32-bit targest a
The callee copies ABI used for 32-bit hppa causes no end of optimization
issues and problems with
OpenMP. The hppa target is only in Debian unstable and gentoo. In both
cases, packages are
rebuilt often. So, Helge and I decided that it was better to break the
ABI and accept whatever
problems
Hi,
This patch supercedes and extends
https://gcc.gnu.org/ml/gcc-patches/2018-01/msg01479.html,
adding the remaining big-endian support for -mno-speculate-indirect-jumps.
This includes 32-bit support for indirect calls and sibling calls, and
64-bit support for indirect calls. The endian-neutral
PR target/83862 pointed out a problem I put into the 128-bit floating point
type signbit optimization. The issue is we want to avoid doing a load to a
floating point/vector register and then a direct move to do signbit, so we
change the load to load the upper 64-bits of the floating point value to
101 - 117 of 117 matches
Mail list logo