On Sun, Aug 6, 2017 at 9:40 PM, H.J. Lu wrote:
> When there is no stack access, there is no need to use frame pointer
> even if -fno-omit-frame-pointer is used.
>
> Tested on i686 and x86-64. OK for trunk?
>
> H.J.
> ---
> gcc/
>
> PR target/81736
> * config/i386/i386.c (ix86_fina
On Mon, Aug 7, 2017 at 3:26 AM, H.J. Lu wrote:
> The difference between Nehalem and Westmere is AES. We should set
> priority to P_AES for Westmere, not P_PROC_SSE4_2 which is for Nehalem.
> Otherwise, we will pick Nehalem implementation on Westmere. Tested on
> Westmere.
>
> OK for trunk?
>
> H
2017-08-05 Ryan Mounce
cherry picked from trunk r235362
2016-04-22 Szabolcs Nagy
* system.h (list, map, set, vector): Include conditionally.
* auto-profile.c (INCLUDE_MAP, INCLUDE_SET): Define.
* graphite-isl-ast-to-gimple.c (INCLUDE_MAP): Define.
2017-08-05 Ryan Mounce
cherry picked from trunk r235361
2016-04-22 Szabolcs Nagy
* auto-profile.c: Remove include.
* diagnostic.c: Remove include.
* genmatch.c: Likewise.
* pretty-print.c: Likewise.
* toplev.c: Likewise
* c/c
Fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81037
Bootstrap now succeeds using Xcode 9 toolchain.
Tested on macOS 10.13 beta, however same issue reported on macOS 10.12
with Xcode 9.
Ryan Mounce (2):
(header usage fix) remove unused system header includes
(header usage fix) include c+
The difference between Nehalem and Westmere is AES. We should set
priority to P_AES for Westmere, not P_PROC_SSE4_2 which is for Nehalem.
Otherwise, we will pick Nehalem implementation on Westmere. Tested on
Westmere.
OK for trunk?
H.J.
---
PR target/81743
* config/i386/i386.c (
On 08/03/2017 02:45 AM, Richard Biener wrote:
On Wed, Aug 2, 2017 at 7:10 PM, Jeff Law wrote:
On 08/01/2017 03:25 AM, Richard Biener wrote:
On Tue, Aug 1, 2017 at 11:23 AM, Richard Biener
wrote:
On Tue, Aug 1, 2017 at 4:27 AM, Martin Sebor wrote:
Richard,
in discussing this work Jeff ment
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Spanish team of translators. The file is available at:
http://translationproject.org/latest/gcc/es.po
(This file, 'gcc-7.1.0.es.po', has just
On 08/04/2017 04:04 PM, David Malcolm wrote:
This patch kit clearly isn't ready yet as-is (see e.g. the
"known unknowns" below), but I'm posting it now in the hope of
getting early feedback.
Summary
===
This patch kit provides an easy way to make integrate 3rd-party static
analysis tools in
Part 3 of the series contains the meat of the patch: the new
-Wstringop-truncation option, and enhancements to -Wstringop-
overflow, and -Wpointer-sizeof-memaccess to detect misuses of
strncpy and strncat.
Martin
PR c/81117 - Improve buffer overflow checking in strncpy
gcc/ChangeLog:
PR c/8111
For completeness, patch 4 are the (already preapproved) fixups
to GCC to let it compile with the -Wstringop-truncation option.
I will commit this patch shortly.
Martin
PR c/81117 - Improve buffer overflow checking in strncpy
gcc/ada/ChangeLog:
PR c/81117
* adadecode.c (__gnat_decode): Replace
The attached patch adds support for a new GCC format specifier,
G, that behaves like %K but accepts a gcall* argument. This
makes it possible to provide inlining context for "artificial"
inline functions like strncpy (with _FORTIFY_SOURCE) in
diagnostics issued from the middle end.
Martin
PR c/8
Part 2 of the series adds attribute nostring to annotate arrays
of and pointers to char with that are intended to store sequences
of characters that aren't necessarily valid (nul-terminated)
strings. In the subsequent patch the attribute is relied on to
avoid diagnosing strcncpy calls that trunca
On 08/02/2017 10:58 AM, Jeff Law wrote:
On 07/31/2017 01:42 PM, Martin Sebor wrote:
So I *think* TYPE_SIZE_UNIT isn't necessarily guaranteed to be a
INTEGER_CST, it could be a non-constant expression for the size. Are
the callers of compute_objsize prepared to handle that? Just to be
clear, I'
When there is no stack access, there is no need to use frame pointer
even if -fno-omit-frame-pointer is used.
Tested on i686 and x86-64. OK for trunk?
H.J.
---
gcc/
PR target/81736
* config/i386/i386.c (ix86_finalize_stack_realign_flags): Renamed
to ...
(ix86_fin
These testcase assume -mcpu=generic or -march=armv8.1-a so use those
options as needed.
Note gcc.target/aarch64/target_attr_3.c needs both as it depends on
scheduler to get the pattern needed for fix-cortex-a53-835769 to work.
Committed after testing on aarch64-linux-gnu with
--target_board=unix/\
Attached patch generates memory reference to a stack protector guard
value in a TLS block, using the correct address space. This reduces
number of stack protector patterns, since universal patterns are now
able to handle all memory references to stack protector guard value
(global or from TLS block
Hi,
This test fails if you supply a -mcpu= (or -march) option which
enables LSE (or when you default to having LSE turned on). This fixes
that by supplying -march=armv8.1-a+nolse and skips if you pass a -mcpu
option.
Committed as obvious after testing on aarch64-linux-gnu with
--target_board=un
Hi,
The gcc.target/aarch64/_Float16_*.c tests fail if we are testing with
-mcpu= option which is not an armv8.2-a processor. This is because
independent of the order -mcpu=/-march= options, -mcpu= overrides the
-march= option.
Committed as obvious after testing on aarch64-linux-gnu with
"--targe
Looks OK, thanks.
Jerry
On 08/04/2017 12:32 PM, Thomas Koenig wrote:
> Am 04.08.2017 um 14:09 schrieb Thomas Koenig:
>> Hello world,
>>
>> the attached patch
>
> This time, really attached, even with ChangeLog!
>
> Regards
>
> Thomas
>
> 2017-08-04 Thomas Koenig
>
> PR fortran
Hello!
CALL_PALL 0x81 that implements trap insn updates PC to point after the
insn before exception is raised. If the trap insn is the last insn in
the noreturn function, then updated PC actually points outside of
function boundaries. This confuses both, gdb and backtrace.
The solution is to emit
On 4 August 2017 at 00:23, Mike Stump wrote:
> On Jul 27, 2017, at 2:07 AM, Pierre-Marie de Rodat
> wrote:
>> On 07/27/2017 09:52 AM, Richard Biener wrote:
I'm fine with the direction if a reviewer wants to go in that
direction. I wish python didn't have a built-in speed penalty,
On BE/-m64:
FAIL: gcc.target/powerpc/loop_align.c scan-assembler .p2align 5,,31
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
On 08/04/2017 11:15 AM, Jan Hubicka wrote:
III.
I've written this patch to check for the missing probability more
consistently. I'm not certain if we can require that the probability
should always be set, so I'm just requiring that if it is set on one
outgoing edge, it needs to be set on all ou
Hi,
this patch adds missing edge probabilities in expand_oacc_for, for the
tile and element loops that are generated when the tile clause is used.
Committed.
Thanks,
- Tom
Add missing edge probabilities in expand_oacc_for, tile case
;; basic block 11, loop depth 2, freq 0, maybe hot
;;
Hi,
this patch adds missing edge probability in expand_oacc_for for the
chunk loop.
Committed.
Thanks,
- Tom
Add missing edge probability in expand_oacc_for
;; basic block 10, loop depth 1, freq 0, maybe hot
;;prev block 9, next block 19, flags: (NEW, REACHABLE)
;;pred: 18
Hi,
this patch requires effective target nonlocal_goto for test-case
gcc.dg/pr78582.c.
Committed.
Thanks,
- Tom
Require nonlocal_goto for gcc.dg/pr78582.c
2017-08-06 Tom de Vries
* gcc.dg/pr78582.c: Require effective target nonlocal_goto.
---
gcc/testsuite/gcc.dg/pr78582.c | 1 +
1 fi
On 06/23/2017 11:19 AM, Renlin Li wrote:
+__attribute__ ((used))
+void
+my_memmove (void *d, const void *s, size_t n)
+{
+ char *dst = (char *) d;
+ const char *src = (const char *) s;
+ if (src >= dst)
+while (n--)
+ *dst++ = *src++;
+ else
+{
+ dst += n;
+ src += n;
+
FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c (test for errors, line 18)
FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c (test for excess errors)
FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c (test for errors, line 18)
FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c (test for
Hi,
this fixes a call arguments mismatch in gcc.dg/torture/pr78218.c when
compiling for nvptx.
I've verified that the test-case is still failing when the patch for
PR81731 is reverted.
Committed.
Thanks,
- Tom
Fix call arguments mismatch in gcc.dg/torture/pr78218.c
2017-08-06 Tom de Vrie
30 matches
Mail list logo
