[patch, doc] fix some typos

I noticed some repeated typos ("isntructions") in the ARM options section of invoke.texi when I was skimming it looking for something else. Then I looked around and found a few other typos elsewhere. I've checked in this correction. -Sandra 2017-12-16 Sandra Loosemore

Re: [Patch combine] Don't create vector mode ZERO_EXTEND from subregs

Hi! On Mon, Dec 11, 2017 at 02:18:53PM +, James Greenhalgh wrote: > > In simplify_set we try transforming the paradoxical subreg expression: > > (set FOO (subreg:M (mem:N BAR) 0)) > > in to: > > (set FOO (zero_extend:M (mem:N BAR))) > > However, this code does not consider the case

[PATCH 15/14] Use fold_for_warn in get_atomic_generic_size

I rebased the v2 patchkit; here's an extra patch to fix an issue with it uncovered by a recently-added testcase (in r254990). With the patch kit, but without this patch, g++'s c-c++-common/pr83059.c fails to emit the "invalid memory model argument 6" warning. Successfully bootstrapped on

Re: [PATCH] libgo: Add support for sh

On 12/16/2017 10:24 AM, John Paul Adrian Glaubitz wrote: > I'm not sure whether all the definitions in libgo/configure.ac are > correct for SuperH. I made the assumptions that the values are similar > for ARM 32-bit and SuperH as these architectures are comparable, except > that SH has always

[PATCH] rtlanal: dead_or_set_regno_p should handle CLOBBER (PR83424)

In PR83424 combine's move_deaths puts a REG_DEAD not in the wrong place because dead_or_set_regno_p does not account for CLOBBER insns. This fixes it. Bootstrapped and tested on powerpc64-linux {-m32,-m64} and on x86_64-linux. Is this okay for trunk? Segher 2017-12-16 Segher Boessenkool

Re: [PATCH] C++: handle locations wrappers when calling warn_for_memset

On 12/16/2017 06:12 AM, David Malcolm wrote: On Mon, 2017-12-11 at 18:36 -0500, Jason Merrill wrote: On 11/10/2017 04:45 PM, David Malcolm wrote: We need to strip away location wrappers in tree.c predicates like integer_zerop, otherwise they fail when they're called on wrapped INTEGER_CST; an

Re: [patch, libgfortran] Bug 81937 - stack-buffer-overflow on memcpy

On Sat, Dec 16, 2017 at 6:26 PM, Jerry DeLisle wrote: > Hi all, > > This problem was found with -fsanitize=address. > > Turns out we are not correctly tracking the bytes left in the internal unit > string and we were reading memory past the end. I am sure the problem exists

Re: [Patch, testcase] PR82767 Fix scan-assembler patterns in i386/pr71321.c

> On 11/06/2017 12:11 AM, Uros Bizjak wrote: > > On Mon, Nov 6, 2017 at 12:19 AM, Peryt, Sebastian > > wrote: > >>> On Sun, Nov 5, 2017 at 12:14 PM, Peryt, Sebastian > >>> > >>> wrote: > Hi, > > After r253934

Re: [PATCH] set range for strlen(array) to avoid spurious -Wstringop-overflow (PR 83373 , PR 78450)

On 12/15/2017 10:29 AM, Martin Sebor wrote: On 12/15/2017 09:17 AM, Richard Biener wrote: On December 15, 2017 4:58:14 PM GMT+01:00, Martin Sebor wrote: On 12/15/2017 01:48 AM, Richard Biener wrote: On Thu, Dec 14, 2017 at 5:01 PM, Martin Sebor wrote:

[patch, libgfortran] Bug 81937 - stack-buffer-overflow on memcpy

Hi all, This problem was found with -fsanitize=address. Turns out we are not correctly tracking the bytes left in the internal unit string and we were reading memory past the end. I am sure the problem exists in gcc 7 and I will examine gcc 6 as well and fix this in all cases I see. The function

Re: [Patch, testcase] PR82767 Fix scan-assembler patterns in i386/pr71321.c

On 11/06/2017 12:11 AM, Uros Bizjak wrote: > On Mon, Nov 6, 2017 at 12:19 AM, Peryt, Sebastian > wrote: >>> On Sun, Nov 5, 2017 at 12:14 PM, Peryt, Sebastian >>> >>> wrote: Hi, After r253934 gcc.target/i386/pr71321.c started

Re: [Patch combine] Don't create vector mode ZERO_EXTEND from subregs

I was happily going to close PR 55549, but it looks like we are trying the same transformation in a second place in that file :-( On Mon, 11 Dec 2017, James Greenhalgh wrote: Hi, In simplify_set we try transforming the paradoxical subreg expression: (set FOO (subreg:M (mem:N BAR) 0)) in

[PATCH] C++: handle locations wrappers when calling warn_for_memset

On Mon, 2017-12-11 at 18:36 -0500, Jason Merrill wrote: > On 11/10/2017 04:45 PM, David Malcolm wrote: > > We need to strip away location wrappers in tree.c predicates like > > integer_zerop, otherwise they fail when they're called on > > wrapped INTEGER_CST; an example can be seen for > >

Re: [PATCH] libgo: Add support for sh

On 12/16/2017 10:24 AM, John Paul Adrian Glaubitz wrote: > The attached patch adds the necessary definitions to enable libgo > to build on sh (Hitachi SuperH). Forgot to mention: I can compile Go programs for SH with the patched gcc-7 which work fine on my Renesas SH7785LCR evaluation board

[v3 PATCH] PR libstdc++/68430

The compiler-powered is_constructible that we have in gcc 8 is powerful enough to give the right answer to an is_constructible question that would be hard for a pure-library implementation to get right in a well-formed fashion. This is just adding a test for it. Tested on Linux-PPC64, OK for

[PATCH] libgo: Add support for sh

Hello! The attached patch adds the necessary definitions to enable libgo to build on sh (Hitachi SuperH). Two remarks: 1. I'm not sure whether all the definitions in libgo/configure.ac are correct for SuperH. I made the assumptions that the values are similar for ARM 32-bit and SuperH as these