[C++ PATCH] Add test for c++/77747

This was fixed by r241765 but we didn't have an explicit test that tests if we detect the error of inheriting constructors from an indirect base. Tested on x86_64-linux, applying to trunk. 2019-06-07 Marek Polacek PR c++/77747 * g++.dg/cpp0x/inh-ctor33.C: New test. diff

[committed]: Add pattern for hppa*-*-linux* to dg-function-on-line

As a result of moving the function label position on hppa-linux, we need a new pattern for hppa*-*-linux* in dg-function-on-line. Tested on hppa-unknown-linux-gnu and hppa2.0w-hp-hpux11.11. Committed to trunk, gcc-9 and gcc-8. Dave -- John David Anglin dave.ang...@bell.net 2019-06-07 John

[committed] hppa: Fix support for -fpatchtable-function-entry on hppa-linux

Sven Schnelle has implemented dynamic ftrace support for parisc linux: https://lore.kernel.org/linux-parisc/20190605203222.6194-1-sv...@stackframe.org/T/#t It uses -fpatchtable-function-entry to allocate a set of nops before each function. This patch fixes this option on hppa-linux. The main

[C++ PATCH] Add test for c++/77967

Fixed by r246462. Tested x86_64-linux, applying to trunk. 2019-06-07 Marek Polacek PR c++/77967 * g++.dg/cpp0x/alias-decl-68.C: New test. diff --git gcc/testsuite/g++.dg/cpp0x/alias-decl-68.C gcc/testsuite/g++.dg/cpp0x/alias-decl-68.C new file mode 100644 index

[C++ PATCH] Add test for c++/77771

This was fixed by r250659. Tested on x86_64-linux, applying to trunk. 2019-06-07 Marek Polacek PR c++/1 * g++.dg/cpp0x/constexpr-1.C: New test. diff --git gcc/testsuite/g++.dg/cpp0x/constexpr-1.C gcc/testsuite/g++.dg/cpp0x/constexpr-1.C new file mode 100644

[PATCH, v2] Disable PowerPC pc-relative support until the code is checked in

Ok, here is the revised version of the patch. -mcpu=future sets -mprefixed-addr but not -mpcrel. Using either -mpcrel or -mprefixed-addr does not set -mcpu=future. I tweaked the tests for -mpcrel and -mprefixed-addr somewhat, and kept the changes to the testsuite. [gcc] 2019-06-07 Michael

Re: [PATCH 2/2] [ARC] Update RTX costs.

On 6/6/19 1:42 AM, Claudiu Zissulescu wrote: > Update RTX costs to reflect better the ARC architecture. > > Ok to apply? > Claudiu > > gcc/ > -xx-xx Claudiu Zissulescu > > * config/arc/arc.c (arc_rtx_costs): Update costs. > > /gcc/testsuite > -xx-xx Claudiu Zissulescu > >

Re: [PATCH 1/2] [ARC] Improve code gen when compiling for size

On 6/6/19 1:42 AM, Claudiu Zissulescu wrote: > When optimizing for size, try to avoid using long immediate by > employing alternative (short) instructions. > > Ok to apply? > Claudiu > > gcc/ > -xx-xx Claudiu Zissulescu > > * config/arc/arc-protos.h (arc_check_ior_const): Declare.

Re: [PATCH][RFC] Sanitize equals and hash functions in hash-tables.

On Fri, Jun 7, 2019 at 8:14 AM Martin Liška wrote: > > On 6/7/19 2:09 PM, Richard Biener wrote: > > On Fri, Jun 7, 2019 at 2:03 PM Martin Liška wrote: > >> > >> On 6/7/19 10:57 AM, Richard Biener wrote: > >>> On Mon, Jun 3, 2019 at 3:35 PM Martin Liška wrote: > > On 6/1/19 12:06 AM,

Go patch committed: Improve write barrier generation

This patch to the Go frontend by Cherry Zhang changes write barrier generation so that for string, slice, and interface values we do assignments field by field instead of using typedmemmove. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian Index:

[RFA PATCH] Recognize ggc_free'd memory in pretty-printers.

A tree node that has been poisoned by ggc_free is easily recognizable by the TREE_CODE 0xa5a5; let's look for that rather than access some random memory off the end of the array. OK for trunk? * gdbhooks.py (TreePrinter.to_string): Recognize ggc_free'd memory. * tree.c

[C++ PATCH] Avoid constexpr garbage for implicit conversion to void.

All expression statements and some other places express implicit conversion to void with a CONVERT_EXPR. There's no reason to build up a new one as part of constexpr evaluation. The ADDR_EXPR change also avoids a bit of garbage by discarding an ADDR_EXPR we just built but didn't end up using.

Re: [C++ PATCH] PR c++/90449 - add -Winaccessible-base option.

Hi, On 07/06/19 22:31, Marek Polacek wrote: On Fri, Jun 07, 2019 at 10:20:02PM +0200, Paolo Carlini wrote: Hi, On 07/06/19 22:10, Matthew Beliveau wrote: @@ -6025,6 +6025,10 @@ warn_about_ambiguous_bases (tree t) Just a nit, but it seems weird to me that the function implementing

Re: [C++ PATCH] PR c++/90449 - add -Winaccessible-base option.

On Fri, Jun 07, 2019 at 10:20:02PM +0200, Paolo Carlini wrote: > Hi, > > On 07/06/19 22:10, Matthew Beliveau wrote: > > @@ -6025,6 +6025,10 @@ warn_about_ambiguous_bases (tree t) > > Just a nit, but it seems weird to me that the function implementing > warn_inaccessible_base is named

Re: [PATCH] Add missing avx512dqintrin.h _mm_mask_fpclass_s[sd]_mask (PR target/89803)

On 6/3/19 5:06 AM, Jakub Jelinek wrote: > On Mon, Jun 03, 2019 at 06:01:40PM +0800, Hongtao Liu wrote: >> The following patch adds forgotten avx512f fpclass instrinsics for >> masked scalar operations. >> >> Bootstrapped/regtested on x86_64-linux and i686-linux (on skylake-avx512), >> ok for

Re: [C++ PATCH] PR c++/90449 - add -Winaccessible-base option.

Hi, On 07/06/19 22:10, Matthew Beliveau wrote: @@ -6025,6 +6025,10 @@ warn_about_ambiguous_bases (tree t) Just a nit, but it seems weird to me that the function implementing warn_inaccessible_base is named warn_about_ambiguous_bases. Paolo.

Re: [PATCH] Enable GCC support for AVX512_VP2INTERSECT.

On 6/7/19, H.J. Lu wrote: >> @@ -18702,9 +18705,16 @@ >>if (STACK_REGNO_P (regno)) >> return VALID_FP_MODE_P (mode); >>if (MASK_REGNO_P (regno)) >> -return (VALID_MASK_REG_MODE (mode) >> -|| (TARGET_AVX512BW >> - && VALID_MASK_AVX512BW_MODE (mode))); >> +{ >> + /*

Re: [PATCH] Enable GCC support for AVX512_VP2INTERSECT.

On 6/7/19, H.J. Lu wrote: >> > > +/* Register pair. */ >> > > +VECTOR_MODES_WITH_PREFIX (P, INT, 2); /* P2QI */ >> > > +VECTOR_MODES_WITH_PREFIX (P, INT, 4); /* P2HI P4QI */ >> > > >> > > I think >> > > >> > > INT_MODE (P2QI, 16); >> > > INT_MODE (P2HI, 32); >> > > >> > > with the above subreg

[C++ PATCH] PR c++/90449 - add -Winaccessible-base option.

This patch adds a new warning option: Winaccessible-base, so that users are able to selectively control the warning. The warning is enabled by default; however, for the virtual bases' warning, it only triggers with -Wextra flag. Bootstrapped/regtested on x86_64-linux, ok for trunk? 2019-06-07

[PATCH] PR libstdc++/90770 fix missing src/debug/Makefile

PR libstdc++/90770 * configure: Regenerate. * src/Makefile.am (stamp-debug): Also test for missing makefile. * src/Makefile.in: Regenerate. I'm not sure how the src/debug/Makefile gets removed without the directory it's in being removed, but this makes it work

Re: Test for C++20 p0858 - ConstexprIterator requirements.

On 07/06/19 16:42 +0100, Jonathan Wakely wrote: On 01/06/19 15:40 -0400, Ed Smith-Rowland via libstdc++ wrote: On 6/1/19 2:42 PM, Ville Voutilainen wrote: On Sat, 1 Jun 2019 at 21:09, Ed Smith-Rowland <3dw...@verizon.net> wrote: On 5/31/19 6:29 PM, Ville Voutilainen wrote: On Sat, 1 Jun 2019

Re: undefined behavior in value_range::equiv_add()?

On 6/6/19 4:11 PM, Aldy Hernandez wrote: >> Meanwhile I have bootstrapped / tested the following which does the VARYING >> >> thing. >> >> Applied to trunk.  I think we need to backport this since this is a latent >> >> wrong-code issue.  We can see to improve things on the trunk incrementally. >>

Re: [PATCH] handle vla plus offset in strlen (PR 90662)

On 6/6/19 3:53 PM, Jeff Law wrote: On 6/5/19 4:51 PM, Martin Sebor wrote: One of my new tests for the strlen/sprintf integration tripped over an incomplete handling of VLAs by the strlen pass.  Where it can determine the length of a substring at some offset with other kinds of arrays, the pass 

Re: [PATCH] update get_range_strlen description

On 6/6/19 1:32 PM, Martin Sebor wrote: > Hi Jeff, > > It looks like the updated comment for get_range_strlen didn't make > it into the strlen fixup commits last December and the function > still has the old description.  (Not surprising given there are > at least two overloads of the same 

V2: [PATCH] Update preferred_stack_boundary only when expanding function call

On Fri, Jun 7, 2019 at 1:22 AM Richard Biener wrote: > > On Fri, 7 Jun 2019, Richard Sandiford wrote: > > > "H.J. Lu" writes: > > > locate_and_pad_parm is called when expanding function call from > > > initialize_argument_information and when generating function body > > > from

Re: [PATCH] Enable GCC support for AVX512_VP2INTERSECT.

On Fri, Jun 7, 2019 at 8:59 AM Uros Bizjak wrote: > > On Thu, Jun 6, 2019 at 7:54 AM Hongtao Liu wrote: > > > > Hi Uros and all: > > This patch is about to enable support for AVX512_VP2INTERSECT which will > > be in Willow Cove. There are two instructions for AVX512_VP2INTERSECT: > >

Re: [PATCH] Enable GCC support for AVX512_VP2INTERSECT.

On Fri, Jun 7, 2019 at 8:50 AM Uros Bizjak wrote: > > On Fri, Jun 7, 2019 at 5:05 PM H.J. Lu wrote: > > > > On Thu, Jun 6, 2019 at 5:26 AM Uros Bizjak wrote: > > > > > > On Thu, Jun 6, 2019 at 2:12 PM Uros Bizjak wrote: > > > > > > > > On Thu, Jun 6, 2019 at 7:54 AM Hongtao Liu wrote: > > > >

Re: [AArch64] [SVE] PR88837 - Poor vector construction code in VL-specific mode

Prathamesh Kulkarni writes: > 2019-06-07 Prathamesh Kulkarni > > * gcc.target/aarch64/sve/init_1.c: Remove options > -O2 -fno-schedule-insns and instead pass -O. > Update assembly in comments. > * gcc.target/aarch64/sve/init_2.c: Likewise. > *

Re: [PATCH 2/2] Add warn_unused_result attribute for memory-related, functions in libiberty.

On 6/7/19 1:08 AM, Martin Liška wrote: > Part 2. > > > 0002-Add-warn_unused_result-attribute-for-memory-related-.patch > > From 52f1ae0aa86b11fc3ae17e3e224b58aa8b8519a6 Mon Sep 17 00:00:00 2001 > From: Martin Liska > Date: Fri, 7 Jun 2019 08:14:17 +0200 > Subject: [PATCH 2/2] Add

Re: [PATCH 1/2] Add alloc_size for libiberty memory allocation functions.

On 6/7/19 1:07 AM, Martin Liška wrote: > Hi. > > I'm sending 2 follow up patches that touch libiberty memory allocation > functions. > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? > Thanks, > Martin > > >

Re: Review Hashtable extract node API

On 6/5/19 6:22 PM, Jonathan Wakely wrote: On 04/06/19 19:19 +0200, François Dumont wrote: Hi     Here is a patch to enhance the _Hashtable extract node API and fix a FIXME request.     The enhancement to the extract node Api is that extract(const key_type&) do not call

Re: [PATCH] Disable PowerPC pc-relative support until the code is checked in

On Thu, Jun 06, 2019 at 07:53:29PM -0400, Michael Meissner wrote: > On Thu, Jun 06, 2019 at 06:14:29PM -0500, Segher Boessenkool wrote: > > On Thu, Jun 06, 2019 at 06:42:16PM -0400, Michael Meissner wrote: > > > 2019-06-06 Michael Meissner > > > -mpcrel automatically sets -mcpu=future and

Re: [AArch64] [SVE] PR88837 - Poor vector construction code in VL-specific mode

On Fri, 7 Jun 2019 at 18:26, Richard Sandiford wrote: > > Prathamesh Kulkarni writes: > > On Thu, 6 Jun 2019 at 16:54, Richard Sandiford > > wrote: > >> > >> Szabolcs Nagy writes: > >> > On 03/06/2019 08:26, Prathamesh Kulkarni wrote: > >> >> +++ b/gcc/testsuite/gcc.target/aarch64/sve/init_8.c

Re: libbacktrace integration for _GLIBCXX_DEBUG mode

I forgot to comment on the chosen behavior of _GLIBCXX_DEBUG_BACKTRACE. So, if the user define it, it means that he has install libbacktrace on its system. However we silently ignore it if libbacktrace is eventually not supported. I think it is the simplest thing to do. I am not convinced by

[PATCH] aarch64: fix gcc.target/aarch64/pcs_attribute-2.c on non-gnu targets

Move the ifunc symbol tests into a separate file with dg-require-ifunc. And added a base pcs ifunc symbol to the test for completeness. gcc/testsuite/ChangeLog: 2019-06-07 Szabolcs Nagy * gcc.target/aarch64/pcs_attribute-2.c: Remove ifunc usage. *

Re: [PATCH][GCC][AARCH64] Add tests for pointer authentication B-key

On 07/06/2019 13:40, Christophe Lyon wrote: > On Wed, 5 Jun 2019 at 13:07, Sam Tebbs wrote: >> Committed as obvious as r271954. >> >> On 05/06/2019 11:20, Sam Tebbs wrote: >>> Hi all, >>> >>> When committing my b-key patch (r271735) I didn't svn add the new test >>> files, this patch adds them

Re: [PATCH] Enable GCC support for AVX512_VP2INTERSECT.

On Thu, Jun 6, 2019 at 7:54 AM Hongtao Liu wrote: > > Hi Uros and all: > This patch is about to enable support for AVX512_VP2INTERSECT which will > be in Willow Cove. There are two instructions for AVX512_VP2INTERSECT: > VP2INTERSECTD and VP2INTERSECTQ. More details please refer to >

Re: [PATCH] Enable GCC support for AVX512_VP2INTERSECT.

On Fri, Jun 7, 2019 at 5:05 PM H.J. Lu wrote: > > On Thu, Jun 6, 2019 at 5:26 AM Uros Bizjak wrote: > > > > On Thu, Jun 6, 2019 at 2:12 PM Uros Bizjak wrote: > > > > > > On Thu, Jun 6, 2019 at 7:54 AM Hongtao Liu wrote: > > > > > > > > Hi Uros and all: > > > > This patch is about to enable

Re: Test for C++20 p0858 - ConstexprIterator requirements.

On 01/06/19 15:40 -0400, Ed Smith-Rowland via libstdc++ wrote: On 6/1/19 2:42 PM, Ville Voutilainen wrote: On Sat, 1 Jun 2019 at 21:09, Ed Smith-Rowland <3dw...@verizon.net> wrote: On 5/31/19 6:29 PM, Ville Voutilainen wrote: On Sat, 1 Jun 2019 at 01:24, Ed Smith-Rowland via libstdc++ wrote:

Re: [PATCH] Fix bootstrap

Jakub Jelinek writes: > Hi! > > Attached are two different fixes, each of which fixes the build. > The first one arranges gencondmd to be linked against build/errors.o, > so that it links fine, the second one instead doesn't define the function > and method which requires that, as it is only

Re: [PATCH] Fix bootstrap (was: Re: [PATCH][RFC] Sanitize equals and hash functions in hash-tables.)

On 6/7/19 5:13 PM, Jakub Jelinek wrote: Ok for trunk? Which one? Thank you Jakub for the fix. I'm fine with both. Martin

[PATCH] Fix bootstrap (was: Re: [PATCH][RFC] Sanitize equals and hash functions in hash-tables.)

Hi! Attached are two different fixes, each of which fixes the build. The first one arranges gencondmd to be linked against build/errors.o, so that it links fine, the second one instead doesn't define the function and method which requires that, as it is only called from #if CHECKING_P guarded

Re: [PATCH] Add warn_unused_result for malloc-like functions (PR tree-optimization/78902).

On 6/6/19 11:27 PM, Martin Liška wrote: On 6/6/19 5:17 PM, Martin Sebor wrote: On 6/6/19 2:01 AM, Martin Liška wrote: Hi. The patch is about addition of warn_unused_attribute for malloc-like function. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. I like this change

Re: [PATCH] Enable GCC support for AVX512_VP2INTERSECT.

On Thu, Jun 6, 2019 at 5:26 AM Uros Bizjak wrote: > > On Thu, Jun 6, 2019 at 2:12 PM Uros Bizjak wrote: > > > > On Thu, Jun 6, 2019 at 7:54 AM Hongtao Liu wrote: > > > > > > Hi Uros and all: > > > This patch is about to enable support for AVX512_VP2INTERSECT which will > > > be in Willow

Re: [PATCH][RFC] Sanitize equals and hash functions in hash-tables.

On 6/7/19 6:13 AM, Martin Liška wrote: On 6/7/19 2:09 PM, Richard Biener wrote: On Fri, Jun 7, 2019 at 2:03 PM Martin Liška wrote: On 6/7/19 10:57 AM, Richard Biener wrote: On Mon, Jun 3, 2019 at 3:35 PM Martin Liška wrote: On 6/1/19 12:06 AM, Jeff Law wrote: On 5/22/19 3:13 AM, Martin

[PATCH 3/3] Enable full libgfortran library for AMD GCN

This patch basically reverts the previous patch to put AMD GCN in "minimal" mode. OK to commit? -- Andrew Stubbs Mentor Graphics / CodeSourcery Enable full GFortran library for AMD GCN 2019-06-07 Kwok Cheung Yeung Andrew Stubbs libgfortran/ * configure: Regenerate. *

[PATCH 1/3] Create GCN-specific gthreads

This patch creates a new gthread model for AMD GCN devices. For now, there's just enough support for libgfortran to use mutexes in its I/O routines. The rest can be added at a later time, if at all. Notes: * GCN GPUs do not support dynamic creation and deletion of threads, so there can

[PATCH 2/3] Stub implementation of unwinding for AMD GCN.

This patch provides the "_Unwind_Backtrace" and "_Unwind_GetIPInfo" symbols required to link programs using libgfortran. I do not wish to implement proper backtracing at this time (I have other things to work on), and IIUC none of the existing implementations will Just Work. OK to commit?

[PATCH 0/3] Enable full libgfortran for AMD GCN

This short patch series is intended to allow GCN kernels to print to stdout using Fortran "print" and "write" (C printf, write, etc. already work). The first two patches implement dependencies that libgfortran needs. I'll also be posting a newlib patch shortly. The third patch enables the

Go patch committed: Support inlining functions with if statements

This patch to the Go frontend supports inlining functions with if statements. This increases the number of inlinable functions from 455 to 500. An example of a newly inlinable function is strings.Compare. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian

Re: RFA: Synchronize top level files with binutils

Hi Richard, >>> +target_modules = { module= libmpx; >>> + bootstrap=true; >>> + lib_path=.libs; }; >> >> It seems to re-introduce things that have been removed on the >> GCC side. > Is it just that one hunk that's problematic (I can't see any other >

Re: [PATCH, OpenACC] Add support for gang local storage allocation in shared memory

Hi Jakub, Thanks for the review! I believe I've addressed all your comments in the attached version of the patch. On Mon, 3 Jun 2019 18:23:00 +0200 Jakub Jelinek wrote: > Why vec * rather than vec? > > @@ -878,6 +884,7 @@ new_omp_context (gimple *stmt, omp_context > > *outer_ctx) } > > > >

Re: [PATCH] fix more -Wformat-diag issues

On 6/7/19 6:57 AM, Christophe Lyon wrote: On Wed, 5 Jun 2019 at 20:33, Martin Sebor wrote: On 5/31/19 12:20 PM, Jeff Law wrote: On 5/31/19 9:56 AM, Martin Sebor wrote: On 5/30/19 5:49 PM, Jeff Law wrote: So in several places there's a comment which indicates that debugging dumps and the

Re: [committed, amdgcn] Add -march=gfx906 for Vega20

On 07/06/2019 00:44, Joseph Myers wrote: On Thu, 6 Jun 2019, Andrew Stubbs wrote: This patch adds a new -march=gfx906 option, and a new multilib to go with it. This is missing an invoke.texi update. Thanks for spotting that Joseph. I've committed the attached, as obvious. Andrew Document

[PR90742] OpenACC/OpenMP target offloading: Fortran 'allocatable' scalars in 'firstprivate' clauses

Hi! As I had mentioned in the PR... On Tue, 7 Aug 2018 14:55:07 -0700, Cesar Philippidis wrote: > This patch ... would be one component for fixing "OpenACC/OpenMP target offloading: Fortran 'allocatable' scalars in 'firstprivate' clauses". (Also, as mentioned

Re: RFA: Synchronize top level files with binutils

On 29/05/2019 14:46, Richard Biener wrote: > On Wed, May 29, 2019 at 3:40 PM Nick Clifton wrote: >> >> Hi Guys, >> >> I would like to bring over a few additions that have recently been >> made to the binutils versions of the Makefile.def and configure.ac >> files. Any objections ? >> >>

Re: [PATCH 2/4] Implement N disk counters for single value and indirect call counters.

> > Because I removed hist->hvalue.counters[2] where we stored total number of > executions. > It's back again so that _atomic suffix version makes sense again. OK and we do not care about race conditions on the other two counters? > > After we discussed that I decided to live with all

Go patch committed: Do simple deadcode elimination

This patch by Cherry Zhang adds simple deadcode elimination to the Go frontend. Normally the backend will do deadcode elimination and this is sufficient. However, the escape analysis operates on the AST that may have deadcode, and may cause things to escape that otherwise do not. This patch

Re: IPA ICF: enhance dump about items in a non-singular class.

> Hi. > > There's one more similar patch. > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? OK, thanks! Honza > Thanks, > Martin > From 466a951d51064a4b339b1332c1723e77e3170150 Mon Sep 17 00:00:00 2001 > From: Martin Liska > Date: Thu, 6 Jun

Re: [PATCH] fix more -Wformat-diag issues

On Wed, 5 Jun 2019 at 20:33, Martin Sebor wrote: > > On 5/31/19 12:20 PM, Jeff Law wrote: > > On 5/31/19 9:56 AM, Martin Sebor wrote: > >> On 5/30/19 5:49 PM, Jeff Law wrote: > >>> So in several places there's a comment which indicates that debugging > >>> dumps and the like do not follow

Re: [AArch64] [SVE] PR88837 - Poor vector construction code in VL-specific mode

Prathamesh Kulkarni writes: > On Thu, 6 Jun 2019 at 16:54, Richard Sandiford > wrote: >> >> Szabolcs Nagy writes: >> > On 03/06/2019 08:26, Prathamesh Kulkarni wrote: >> >> +++ b/gcc/testsuite/gcc.target/aarch64/sve/init_8.c >> >> @@ -0,0 +1,32 @@ >> >> +/* { dg-do assemble { target

Re: [PATCH][D] Fix PR90778

On Fri, 7 Jun 2019 at 14:37, Richard Biener wrote: > > > The following fixes random debug info differences I was experiencing > building the D runtime. The issue is ordering BLOCK_VARS after > a hash-table traversal order which is susceptible to address-space > randomization differences. > >

IPA ICF: enhance dump about items in a non-singular class.

Hi. There's one more similar patch. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin >From 466a951d51064a4b339b1332c1723e77e3170150 Mon Sep 17 00:00:00 2001 From: Martin Liska Date: Thu, 6 Jun 2019 14:37:45 +0200 Subject: [PATCH] IPA

Re: [PATCH][GCC][AARCH64] Add tests for pointer authentication B-key

On Wed, 5 Jun 2019 at 13:07, Sam Tebbs wrote: > > Committed as obvious as r271954. > > On 05/06/2019 11:20, Sam Tebbs wrote: > > Hi all, > > > > When committing my b-key patch (r271735) I didn't svn add the new test > > files, this patch adds them and moves the exception tests to > >

[PATCH][D] Fix PR90778

The following fixes random debug info differences I was experiencing building the D runtime. The issue is ordering BLOCK_VARS after a hash-table traversal order which is susceptible to address-space randomization differences. Bootstrapped on x86_64-unknown-linux-gnu, testing in progress. OK

Re: [PATCH][RFC] Sanitize equals and hash functions in hash-tables.

On 6/7/19 2:09 PM, Richard Biener wrote: > On Fri, Jun 7, 2019 at 2:03 PM Martin Liška wrote: >> >> On 6/7/19 10:57 AM, Richard Biener wrote: >>> On Mon, Jun 3, 2019 at 3:35 PM Martin Liška wrote: On 6/1/19 12:06 AM, Jeff Law wrote: > On 5/22/19 3:13 AM, Martin Liška wrote: >>

Re: [PATCH][RFC] Sanitize equals and hash functions in hash-tables.

On Fri, Jun 7, 2019 at 2:03 PM Martin Liška wrote: > > On 6/7/19 10:57 AM, Richard Biener wrote: > > On Mon, Jun 3, 2019 at 3:35 PM Martin Liška wrote: > >> > >> On 6/1/19 12:06 AM, Jeff Law wrote: > >>> On 5/22/19 3:13 AM, Martin Liška wrote: > On 5/21/19 1:51 PM, Richard Biener wrote: >

Re: [PATCH][RFC] Sanitize equals and hash functions in hash-tables.

On 6/7/19 10:57 AM, Richard Biener wrote: > On Mon, Jun 3, 2019 at 3:35 PM Martin Liška wrote: >> >> On 6/1/19 12:06 AM, Jeff Law wrote: >>> On 5/22/19 3:13 AM, Martin Liška wrote: On 5/21/19 1:51 PM, Richard Biener wrote: > On Tue, May 21, 2019 at 1:02 PM Martin Liška wrote: >>

Re: [PATCH] PR c/17896 Check for missplaced bitwise op

ping Em sex, 24 de mai de 2019 às 09:53, Rafael Tsuha escreveu: > > This patch adds a function to warn when there's a bitwise operation > between a boolean and any other type. This kind of operation is > probably a programmer mistake that may lead to unexpected behavior > because possibily the

Re: [AArch64] [SVE] PR88837 - Poor vector construction code in VL-specific mode

On Thu, 6 Jun 2019 at 16:54, Richard Sandiford wrote: > > Szabolcs Nagy writes: > > On 03/06/2019 08:26, Prathamesh Kulkarni wrote: > >> +++ b/gcc/testsuite/gcc.target/aarch64/sve/init_8.c > >> @@ -0,0 +1,32 @@ > >> +/* { dg-do assemble { target aarch64_asm_sve_ok } } */ > >> +/* { dg-options

Re: [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git

On 07/06/2019 00:50, Ian Lance Taylor wrote: > On Thu, Jun 6, 2019 at 4:41 PM Joseph Myers wrote: >> >> On Thu, 6 Jun 2019, Richard Earnshaw (lists) wrote: >> For email addresses, I think that using @gcc.gnu.org would be the best approach for people that have such accounts, rather than

Re: [PATCH 2/4] Implement N disk counters for single value and indirect call counters.

On 6/6/19 2:50 PM, Jan Hubicka wrote: >> >> gcc/ChangeLog: >> >> 2019-06-04 Martin Liska >> >> * gcov-io.h (GCOV_DISK_SINGLE_VALUES): New. >> (GCOV_SINGLE_VALUE_COUNTERS): Likewise. >> * ipa-profile.c (ipa_profile_generate_summary): >> Use get_most_common_single_value. >>

Re: [PATCH][arm] Implement usadv16qi and ssadv16qi standard names

Hi all, This patch implements the usadv16qi and ssadv16qi standard names for arm. The V16QImode variant is important as it is the most commonly used pattern: reducing vectors of bytes into an int. The midend expects the optab to compute the absolute differences of operands 1 and 2 and reduce

Re: [PATCH][RFC] Sanitize equals and hash functions in hash-tables.

On Mon, Jun 3, 2019 at 3:35 PM Martin Liška wrote: > > On 6/1/19 12:06 AM, Jeff Law wrote: > > On 5/22/19 3:13 AM, Martin Liška wrote: > >> On 5/21/19 1:51 PM, Richard Biener wrote: > >>> On Tue, May 21, 2019 at 1:02 PM Martin Liška wrote: > > On 5/21/19 11:38 AM, Richard Biener wrote:

Re: [PATCH][Preprocessor][Version 3]patch to fix PR 90581

On Mon, Jun 3, 2019 at 6:46 PM Qing Zhao wrote: > > Hi, > > this is the 3rd version of the patch, which fixed the issues Paolo raised in > the previous email. > > Okay for trunk? OK. Thanks, Richard. > thanks. > > gcc/ChangeLog: > > 2019-06-03 qing zhao > >* doc/cppopts.texi: Add

Re: [PATCH] Update preferred_stack_boundary only when expanding function call

On Fri, 7 Jun 2019, Richard Sandiford wrote: > "H.J. Lu" writes: > > locate_and_pad_parm is called when expanding function call from > > initialize_argument_information and when generating function body > > from assign_parm_find_entry_rtl: > > > > /* Remember if the outgoing parameter requires

Backported fix for PR82920 to 8-branch

The backport for pr82920 to 8.x needed some minor tweaks, so patches posted here for reference. There are also three additional testcases only present on 8 branch that needed adjustment. (re-)tested on x86_64-darwin16, x86_64-linux-gnu (--target_board=unix\{-m32,-m64\}\{,-fpic\}) applied,

Re: [RFC][PR88838][SVE] Use 32-bit WHILELO in LP64 mode

Jeff Law writes: > On 6/6/19 6:33 AM, Richard Sandiford wrote: >> Kugan Vivekanandarajah writes: >>> Hi Richard, >>> >>> On Thu, 6 Jun 2019 at 22:07, Richard Sandiford >>> wrote: Kugan Vivekanandarajah writes: > Hi Richard, > > On Thu, 6 Jun 2019 at 19:35, Richard

Re: [PATCH] RX: Add rx-*-linux target

On Thu, 06 Jun 2019 08:22:55 +0900, Jeff Law wrote: > > [1 ] > On 6/3/19 11:01 AM, Yoshinori Sato wrote: > > On Sun, 02 Jun 2019 22:12:37 +0900, > > Oleg Endo wrote: > >> > >> On Sun, 2019-06-02 at 20:26 +0900, Yoshinori Sato wrote: > >>> On Fri, 31 May 2019 09:16:18 +0900, > >>> Jeff Law wrote:

Re: [PATCH] Update preferred_stack_boundary only when expanding function call

"H.J. Lu" writes: > locate_and_pad_parm is called when expanding function call from > initialize_argument_information and when generating function body > from assign_parm_find_entry_rtl: > > /* Remember if the outgoing parameter requires extra alignment on the > calling function side. */

[PATCH 2/2] Add warn_unused_result attribute for memory-related, functions in libiberty.

Part 2. >From 52f1ae0aa86b11fc3ae17e3e224b58aa8b8519a6 Mon Sep 17 00:00:00 2001 From: Martin Liska Date: Fri, 7 Jun 2019 08:14:17 +0200 Subject: [PATCH 2/2] Add warn_unused_result attribute for memory-related functions in libiberty. include/ChangeLog: 2019-06-07 Martin Liska * ansidecl.h

[PATCH 1/2] Add alloc_size for libiberty memory allocation functions.

Hi. I'm sending 2 follow up patches that touch libiberty memory allocation functions. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin >From bd430388cffe4b72d6be52cbaeda9eb9c8f8a248 Mon Sep 17 00:00:00 2001 From: Martin Liska Date:

Re: Patch: don't cap TYPE_PRECISION of bitsizetype at MAX_FIXED_MODE_SIZE

On Thu, Jun 6, 2019 at 4:04 PM Hans-Peter Nilsson wrote: > > > From: Eric Botcazou > > Date: Wed, 05 Jun 2019 22:03:04 +0200 > > > > This issue exists, not just for targets that can have their > > > MAX_FIXED_MODE_SIZE more-or-less easily tweaked higher, but also > > > for the 'bit-container'

Re: Patch: don't cap TYPE_PRECISION of bitsizetype at MAX_FIXED_MODE_SIZE

On Thu, Jun 6, 2019 at 4:15 PM Hans-Peter Nilsson wrote: > > > Date: Thu, 6 Jun 2019 16:04:47 +0200 > > From: Hans-Peter Nilsson > > > When bitsizetype objects end > > up on the target, they use the actual Pmode and not the larger > > precision mode. > > Oops, a half-way-done email slipped away,

Re: [PATCH] Add warn_unused_result for malloc-like functions (PR tree-optimization/78902).

On 6/7/19 2:02 AM, Jeff Law wrote: > Any thoughts on whether or not we'd want to IPA propagate this attribute > like we do for the malloc attribute? If I see correctly, the pass_warn_unused_result is run very early in the early tree optimizations. Thus we can't propagate that right now. Martin