RE: [PATCH][GCC][front-end][build-machinery][opt-framework] Allow setting of stack-clash via configure options. [Patch (4/6)]

Hi All, I'm looking for permission to backport this patch to the GCC-8 branch to fix PR86486. OK for backport? Thanks, Tamar > -Original Message- > From: Jeff Law > Sent: Friday, August 3, 2018 19:03 > To: Tamar Christina ; Joseph Myers > > Cc: gcc-patches@gcc.gnu.org; nd ; bonz...@gn

RE: [PATCH][GCC][AArch64] Cleanup the AArch64 testsuite when stack-clash is on [Patch (7/7)]

Hi All, I'm looking for permission to backport this patch to the GCC-8 branch to fix PR86486. OK for backport? Thanks, Tamar > -Original Message- > From: gcc-patches-ow...@gcc.gnu.org > On Behalf Of Tamar Christina > Sent: Friday, September 28, 2018 17:36 > To: Jeff Law ; gcc-patches@g

RE: [PATCH][GCC][AArch64] Set default values for stack-clash and do basic validation in back-end. [Patch (5/6)]

Hi All, I'm looking for permission to backport this patch to the GCC-8 branch to fix PR86486. OK for backport? Thanks, Tamar > -Original Message- > From: James Greenhalgh > Sent: Tuesday, July 31, 2018 22:02 > To: Tamar Christina > Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw >

RE: [PATCH][GCC][mid-end] Add a hook to support telling the mid-end when to probe the stack [patch (2/6)]

Hi All, I'm looking for permission to backport this patch to the GCC-8 branch to fix PR86486. OK for backport? Thanks, Tamar > -Original Message- > From: Jeff Law > Sent: Wednesday, July 11, 2018 19:53 > To: Tamar Christina ; gcc-patches@gcc.gnu.org > Cc: nd ; rguent...@suse.de; i...@a

RE: [PATCH 8/8][GCC][AArch64] stack-clash: Add LR assert to layout_frame.

Hi All, I'm looking for permission to backport this patch to the GCC-8 branch to fix PR86486. OK for backport? Thanks, Tamar > -Original Message- > From: gcc-patches-ow...@gcc.gnu.org > On Behalf Of Tamar Christina > Sent: Wednesday, September 26, 2018 09:30 > To: gcc-patches@gcc.gnu.o

RE: [PATCH][GCC][AArch64] Ensure that outgoing argument size is at least 8 bytes when alloca and stack-clash. [Patch (3/6)]

Hi All, I'm looking for permission to backport this patch to the GCC-8 branch to fix PR86486. OK for backport? Thanks, Tamar > -Original Message- > From: James Greenhalgh > Sent: Tuesday, August 7, 2018 17:18 > To: Tamar Christina > Cc: Jeff Law ; gcc-patches@gcc.gnu.org; nd > ; Richa

RE: [PATCH][GCC][AArch64] Updated stack-clash implementation supporting 64k probes. [patch (1/7)]

Hi All, I'm looking for permission to backport this patch to the GCC-8 branch to fix PR86486. OK for backport? Thanks, Tamar > -Original Message- > From: James Greenhalgh > Sent: Tuesday, September 11, 2018 16:56 > To: Tamar Christina > Cc: Richard Sandiford ; Jeff Law > ; gcc-patches

RE: [PATCH][GCC][AArch64] Add support for SVE stack clash probing [patch (2/7)]

Hi All, I'm looking for permission to backport this patch to the GCC-8 branch to fix PR86486. OK for backport? Thanks, Tamar > -Original Message- > From: Richard Sandiford > Sent: Friday, September 28, 2018 18:18 > To: Tamar Christina > Cc: gcc-patches@gcc.gnu.org; nd ; James Greenhal

Re: introduce --enable-mingw-full32 to default to --large-address-aware

On Oct 5, 2018, Joseph Myers wrote: > A new configure option needs documenting in install.texi. Ah, yes, thanks for the reminder. On Oct 6, 2018, JonY <10wa...@gmail.com> wrote: > They're both OK as far as I can see. I just don't like the configure > name implying all 32bit pointers are used

[PATCH] Make std::list::iterator == and != global inline friend

As we talked one day I would like to make all iterator operators global for consistency. So here is the patch to do so for std::list iterators. Thanks to this change the operators ==(iterator, const_iterator) and != are not necessary anymore, one less ==|!= operator candidate.     * include/b

[PATCH] __debug::list use C++11 direct initialization

Here is the communication for my yesterday's patch which I thought svn had failed to commit (I had to interrupt it). Similarly to what I've done for associative containers here is a cleanup of the std::__debug::list implementation leveraging more on C++11 direct initialization. I also made s

[PING][PATCH] tighten up -Wclass-memaccess for ctors/dtors (PR 84851)

Ping: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg01528.html I will go ahead and commit this as obvious this week if there are no objections. On 05/25/2018 02:20 PM, Martin Sebor wrote: (I just now noticed the first two attempts were sent to the wrong list. Sorry about that.) On 05/25/2018

Re: [PATCH] handle attribute positional arguments consistently (PR 87541, 87542)

Attached is an updated patch with the INTEGRAL_TYPE_P test added to detect constant non-integer arguments like (void*)0, and with quoting made unconditional. I also removed the pretty printer business to avoid the "value%s" format, and modified the manual to clarify when each of the attributes ar

Print column information in RTL dumps

Now that -gcolum-info is the default, I think that it makes sense to print the column info in the RTL dumps to be able to find out where numbers come from. Tested on x86_64-suse-linux, applied on the mainline. 2018-10-08 Eric Botcazou * print-rtl.c (rtx_writer::print_rtx_operand_cod

Re: [Patch, regrename] Fix PR87330 : ICE in scan_rtx_reg, at regrename.c

> Other notes need not be changed, as they don't hold renamed register > information. > > Ok for trunk? No, REG_DEAD & REG_UNUSED note must be recomputed by passes consuming them. > 2018-10-09 Sameera Deshpande > * gcc/regrename.c (regrename_do_replace): Add condition to alter > regname if not

[Patch, regrename] Fix PR87330 : ICE in scan_rtx_reg, at regrename.c

Hi! Please find attached the patch fixing the issue PR87330 : ICE in scan_rtx_reg, at regrename.c:1097. The regrename pass does not rename the registers which are in notes, because of which the REG_DEAD note had previous register names, which caused conflicting liveness information generated for t

Re: [Patch, fortran] PR87151 - allocating array of character

Hi Paul, Bootstraps and regtests on FC28/x86_64 - OK for trunk and later for 8-branch? OK. Thanks for the patch! Regards Thomas

Re: [Patch, Fortran] PR fortran/83522 – reject array-valued substrings

Hi Tobias, nice to hear from you again! Build and regtested on x86_64-linux. OK for the trunk? OK. Thanks for the patch! Regards Thomas

Re: [PATCHv2] Handle not explicitly zero terminated strings in merge sections

> Besides, the patch seems to have produced more fallout on Solaris: I see > many new Go testsuite failures on Solaris 10 which probably are related, > and Solaris bootstrap with Ada included is broken due to the extended > usage of string merging. I'm currently investigating what's going on > the

Re: [PING] [PATCH] avoid warning on constant strncpy until next statement is reachable (PR 87028)

Ping: https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01818.html As with the other patch (bug 84561), there may be ways to redesign the warning, but I don't have the cycles to undertake it before stage 1 ends. Unless someone has a simpler suggestion for how to avoid this false positive now can we

[PING #2] [PATCH] look harder for MEM_REF operand equality to avoid -Wstringop-truncation (PR 84561)

Ping: https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01934.html On 10/01/2018 03:30 PM, Martin Sebor wrote: Ping: https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01934.html We have discussed a number of different approaches to moving the warning somewhere else but none is feasible in the limited a

[PATCH] Folding and check_function_arguments

On Mon, 2018-10-08 at 10:37 -0400, Jason Merrill wrote: > On Thu, Oct 4, 2018 at 10:12 AM David Malcolm > wrote: > > > > -Wformat in the C++ FE doesn't work as well as it could: > > (a) it doesn't report precise locations within the string literal, > > and > > (b) it doesn't underline arguments f

Re: [PATCH] avoid warning on constant strncpy until next statement is reachable (PR 87028)

On 10/08/2018 04:05 AM, Richard Biener wrote: On Thu, Oct 4, 2018 at 5:51 PM Martin Sebor wrote: On 10/04/2018 08:58 AM, Jeff Law wrote: On 8/27/18 9:42 AM, Richard Biener wrote: On Mon, Aug 27, 2018 at 5:32 PM Jeff Law wrote: On 08/27/2018 02:29 AM, Richard Biener wrote: On Sun, Aug 26,

Re: [C++ PATCH] Fix pretty-print of enumerator ids (PR c++/87364)

OK. On Mon, Oct 8, 2018 at 1:12 PM will wray wrote: > > Hi, > > A PR to fix Bug 87364 - Pretty print of enumerator never prints the id, > always falls back to C-style cast output > > The fix is tested with the code attached to the bug report and additional > usage over the past few weeks. > > Boot

Re: [PATCH, rs6000] Fix PR86731 vec_sl()

On Mon, Oct 08, 2018 at 02:34:53PM -0500, Will Schmidt wrote: > On Sat, 2018-08-25 at 12:46 -0500, Segher Boessenkool wrote: > > Rest looks fine to me (whatever that means :-) ) > > I took that as an OK for trunk, so this (with whitespace adjustments as > recommended) went into trunk via >( ht

[RFC][PATCH IRA] Fix PR87507, IRA unnecessarily uses non-volatile registers during register assignment

PR87507 shows a problem where IRA assigns a non-volatile TImode reg pair to a pseudo when there is a volatile reg pair available to use. This then causes us to emit save/restore code for the non-volatile reg usage. The problem here is that the only volatile reg pair that is available is an odd/ev

Re: [PATCH, rs6000] Fix PR86731 vec_sl()

On Sat, 2018-08-25 at 12:46 -0500, Segher Boessenkool wrote: > Hi! > > On Tue, Aug 14, 2018 at 06:18:28PM -0500, Will Schmidt wrote: > > PR target/86731 > > * config/rs6000/rs6000.c (rs6000_gimple_fold_builtin): Update logic > > around folding of vec_sl() to handle out of range shift

[gomp5] Fix task reduction handling in implicit parallel regions

Hi! In implicit parallel regions, we have NULL teams and often NULL task. For task reductions we need both non-NULL, so this patch creates such a team in that case, like we do already for target nowait. Tested on x86_64-linux, committed to gomp-5_0-branch. 2018-10-08 Jakub Jelinek *

Re: [PATCH] handle attribute positional arguments consistently (PR 87541, 87542)

On 10/08/2018 07:27 AM, Manuel López-Ibáñez wrote: On 07/10/18 23:38, Martin Sebor wrote: + pretty_printer posval; + if (pos != error_mark_node) +{ + /* Only format the position value when it's valid. By convention + do not quote constant integers. */ + pp_space (&posval);

Re: [PATCH] handle attribute positional arguments consistently (PR 87541, 87542)

On 10/08/2018 05:33 AM, Joseph Myers wrote: On Sun, 7 Oct 2018, Martin Sebor wrote: While still testing an enhancement in the area of attributes I ran across bugs and inconsistencies in how different handlers deal with positional arguments. The bugs are either an ICE due to the handlers not co

Re: Use FOR_EACH_IMM_USE_FAST in gimple-ssa-backprop.c

On 10/8/18 11:27 AM, Richard Sandiford wrote: > As pointed out by Richard in PR63155. It speeds up the testcase a few %. > > Tested on aarch64-linux-gnu. OK to install? > > Richard > > > 2018-10-08 Richard Sandiford > > gcc/ > PR middle-end/63155 > * gimple-ssa-backprop.c (bac

Re: [PATCH][4/n] Remove BLOCK_ABSTRACT

On Fri, Oct 5, 2018 at 7:47 AM Richard Biener wrote: > > On Fri, 28 Sep 2018, Richard Biener wrote: > > > > > It turns out that nobody sets this anymore (dwarf2out did with the > > original code of outputting abstract instances, temporarily so IIRC). > > > > Bootstrap and regtest running on x86_64

Use FOR_EACH_IMM_USE_FAST in gimple-ssa-backprop.c

As pointed out by Richard in PR63155. It speeds up the testcase a few %. Tested on aarch64-linux-gnu. OK to install? Richard 2018-10-08 Richard Sandiford gcc/ PR middle-end/63155 * gimple-ssa-backprop.c (backprop::intersect_uses): Use FOR_EACH_IMM_USE_FAST instead

[C++ PATCH] Fix pretty-print of enumerator ids (PR c++/87364)

Hi, A PR to fix Bug 87364 - Pretty print of enumerator never prints the id, always falls back to C-style cast output The fix is tested with the code attached to the bug report and additional usage over the past few weeks. Bootstrap and regtested on x86_64-linux. OK for trunk? 2018-10-08 Will

[PATCH, pdp11] libgcc: remove -mfloat32

I missed a file that needed to be updated for the removal of -mfloat32. Committed. paul ChangeLog: 2018-10-08 Paul Koning * config/pdp11/t-pdp11: Remove -mfloat32 switch. Index: config/pdp11/t-pdp11 === --- con

[gomp5] Don't recompute addresses of original array sections at the end of taskgroup

Hi! Last week we've agreed that it is allowed to modify the base of array section used in task_reductions within the taskgroup construct, so we can't reread/recompute the base and bias again, either we'd need to save those at the start of the region, or we can just read it from where we've previou

[PATCH][i386] Split reductions (was: Re: [PATCH][RFC][i386] Change sminmax reduction patterns)

On Fri, 5 Oct 2018, Uros Bizjak wrote: > On Thu, Oct 4, 2018 at 2:05 PM Richard Biener wrote: > > > > > > This tries to apply the same trick to sminmax reduction patterns > > as for the reduc_plus_scal ones, namely reduce %zmm -> %ymm -> %xmm > > first. On a microbenchmark this improves performa

Re: [PATCHv2] Handle not explicitly zero terminated strings in merge sections

On 10/08/18 13:14, Rainer Orth wrote: > Hi Bernd, > >> On 10/05/18 20:15, Andreas Schwab wrote: >>> On Sep 14 2018, Bernd Edlinger wrote: >>> diff -Npur gcc/testsuite/gnat.dg/string_merge1.adb gcc/testsuite/gnat.dg/string_merge1.adb --- gcc/testsuite/gnat.dg/string_merge1.adb 1970-

Re: [PATCH] i386: Correct _mm512_mask3_fmaddsub_round_pd

On Thu, Oct 4, 2018 at 5:46 AM H.J. Lu wrote: > > Define _mm512_mask3_fmaddsub_round_pd with > __builtin_ia32_vfmaddsubpd512_mask, instead of > __builtin_ia32_vfmaddpd512_mask. > > PR target/87517 > * config/i386/avx512fintrin.h (_mm512_mask_fmaddsub_round_pd): > Defined wi

Re: [PATCH 2/2 v3][IRA,LRA] Fix PR86939, IRA incorrectly creates an interference between a pseudo register and a hard register

On 10/8/18 8:43 AM, Christophe Lyon wrote: > On Mon, 8 Oct 2018 at 16:13, Peter Bergner wrote: >> >> On 10/8/18 4:14 AM, Christophe Lyon wrote: >>> Since r264897, we are seeing lots of regressions when bootstrapping on arm. >>> There are execution errors as well as ICEs. >>> A detailed list can be

Re: [PATCH v3] Change default to -fno-math-errno

On 10/4/18 1:43 PM, Joseph Myers wrote: > On Thu, 4 Oct 2018, Jeff Law wrote: > >>> I doubt you could prove that without LTO of the whole program because an >>> errno value set by a libm function call could always be checked in the >>> caller of whatever function is being compiled. >> Right, but

Re: [PATCH][i386] Update Zen tuning for vector load cost

On Mon, 8 Oct 2018, Jan Hubicka wrote: > > > > This adjusts Zen AVX256 vector load cost to be twice as expensive > > than AVX128 vector load cost (twice via ix86_vec_cost keying on > > TARGET_AVX128_OPTIMAL - should rather use some > > TARGET_VECTOR_IMPL_WIDTH or so). > > > > Likely the current

Re: Merge from trunk to gccgo branch

I merged trunk revision 264932 to the gccgo branch. Ian

Re: [PATCH 2/2] Support string locations for C++ in -Wformat (PR c++/56856)

On Thu, Oct 4, 2018 at 10:12 AM David Malcolm wrote: > > -Wformat in the C++ FE doesn't work as well as it could: > (a) it doesn't report precise locations within the string literal, and > (b) it doesn't underline arguments for those arguments !CAN_HAVE_LOCATION_P, > despite having location wrappe

[PATCH] libgcc: remove t-ppccomm from powerpc-wrs-vxworks

VxWorks doesn't use the __eabi function (in fact, the ecrti.o and ecrtn.o files are not added to extra_parts). This means that the __SBSS_END__ etc. symbols in eabi.S are always undefined. This is mostly harmless, but it is inconvenient when one wants to create a libgcc runtime module by doing a --

Re: [PATCH][i386] Update Zen tuning for vector load cost

> > This adjusts Zen AVX256 vector load cost to be twice as expensive > than AVX128 vector load cost (twice via ix86_vec_cost keying on > TARGET_AVX128_OPTIMAL - should rather use some > TARGET_VECTOR_IMPL_WIDTH or so). > > Likely the current cost value was meant to make AVX256 loads _cheaper_ >

libgo patch committed: Update to 1.11.1 release

This patch updates libgo to the 1.11.1 release. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian Index: gcc/go/gofrontend/MERGE === --- gcc/go/gofrontend/MERGE (revision 264882) +++ gcc/go/gof

[PATCH, pdp11] Fix LRA failure

This patch fixes a failure handling block moves when the LRA register allocator is used. Committed. paul ChangeLog: 2018-10-08 Paul Koning * config/pdp11/pdp11-protos.h (output_block_move): Remove. (expand_block_move): New function. * config/pdp11/pdp11.c (

Re: [PATCH 2/2 v3][IRA,LRA] Fix PR86939, IRA incorrectly creates an interference between a pseudo register and a hard register

On 10/8/18 4:14 AM, Christophe Lyon wrote: > Since r264897, we are seeing lots of regressions when bootstrapping on arm. > There are execution errors as well as ICEs. > A detailed list can be found at: > https://ci.linaro.org/job/tcwg-compare-results/6498/artifact/artifacts/logs/1-diff-d05_32.tcwg-

Re: C++ PATCH to implement P1064R0, Virtual Function Calls in Constant Expressions (v4)

On Sep 20 2018, Jakub Jelinek wrote: > --- gcc/cp/class.c.jj 2018-09-20 09:56:59.229751895 +0200 > +++ gcc/cp/class.c2018-09-20 10:12:17.447370890 +0200 > @@ -9266,7 +9266,6 @@ build_vtbl_initializer (tree binfo, >tree vcall_index; >tree fn, fn_original; >tree init = N

Re: [PATCH] handle attribute positional arguments consistently (PR 87541, 87542)

On 07/10/18 23:38, Martin Sebor wrote: + pretty_printer posval; + if (pos != error_mark_node) +{ + /* Only format the position value when it's valid. By convention +do not quote constant integers. */ + pp_space (&posval); + if (TREE_CODE (pos) != INTEGER_CST) +

Re: [Patch, fortran] PR87151 - allocating array of character

Hi Dominique, Thanks for the testing. Although the tests for PR80931 and PR83196, comment #4, compiled OK, when I attempted to use the modules both segfaulted for the same reason ('span' not being set on the array descriptor) and these required a slightly different version of the same tweak. The

Re: [PATCH 1/2] zEC12 pipeline

Hi, committed only the zEC12 part for now. Performance behavior of z13 with the patch is still unclear and will be tackled separately. Regards Robin

{Patch, fortran] PR86372 - [8/9 Regression] Segfault on ASSOCIATE statement with CHARACTER variable

I have fixed this as 'obvious' on 8-branch(r264925) and trunk(r264915). Paul 2018-10-08 Paul Thomas Backport from trunk PR fortran/86372 * trans-stmt.c (trans_associate_var): Character associate names with variable string length do not have to be deferred length for the st

Re: [PATCH] Come up with gcc/testsuite/g++.target/i386/i386.dg and move there some tests.

On Mon, Oct 8, 2018 at 2:20 PM Martin Liška wrote: > > On 10/8/18 1:29 PM, Uros Bizjak wrote: > > On Mon, Oct 8, 2018 at 1:21 PM Jakub Jelinek wrote: > >> > >> On Mon, Oct 08, 2018 at 01:17:14PM +0200, Martin Liška wrote: > >>> I'm suggesting following patch that comes up with new g++.target > >

[PATCH v2] fixincludes: vxworks: regs.h: Fix includes in regs.h wrapper

A quick experiment reveals that this hack is needed for C code - simply removing this hack entirely breaks the build of libstdc++, since regs.h (more accurately, the cpu-specific header it pulls in) defines structs in terms of types from vxTypesOld. Those definitions are properly guarded by #ifndef

Re: [Patch 3/3][Aarch64] Implement Aarch64 SIMD ABI

Steve Ellcey writes: > This is the third of three patches for Aarch64 SIMD ABI support.  This > patch is not fully tested yet but I want to post it to get comments. > > This is the only patch of the three that touches non-aarch64 specific > code.  The changes here are made to allow GCC to have bet

Re: [PATCHv2] Handle not explicitly zero terminated strings in merge sections

Hi Bernd, > Besides, the patch seems to have produced more fallout on Solaris: I see > many new Go testsuite failures on Solaris 10 which probably are related, > and Solaris bootstrap with Ada included is broken due to the extended > usage of string merging. I'm currently investigating what's goi

[PATCH] Better vectorizer cost model debugging

We dump the target hook calls but sofar omit the resulting cost (which might not be final). It's still useful info for debugging a target cost model. Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. Richard. 2018-10-08 Richard Biener * tree-vect-loop.c (vect_compute_s

Re: [PATCH] Come up with gcc/testsuite/g++.target/i386/i386.dg and move there some tests.

On 10/8/18 1:29 PM, Uros Bizjak wrote: > On Mon, Oct 8, 2018 at 1:21 PM Jakub Jelinek wrote: >> >> On Mon, Oct 08, 2018 at 01:17:14PM +0200, Martin Liška wrote: >>> I'm suggesting following patch that comes up with new g++.target subfolder. >>> I moved there i386 multiversioning tests. >> >> I thi

Re: [Patch 1/3][Aarch64] Implement Aarch64 SIMD ABI

Steve Ellcey writes: > @@ -1005,6 +1005,15 @@ static const struct processor *selected_tune; > /* The current tuning set. */ > struct tune_params aarch64_tune_params = generic_tunings; > > +/* Table of machine attributes. */ > +static const struct attribute_spec aarch64_attribute_table[] = >

Re: [PATCH] PR libstdc++/87538 fix std::not_fn exception specifications

On 08/10/18 12:59 +0100, Jonathan Wakely wrote: PR libstdc++/87538 * include/std/functional (_Not_fn::operator()): Check value of __is_nothrow_invocable as well. * testsuite/20_util/function_objects/not_fn/87538.cc: New test. Tested x86_64-linux, committed to trun

[gomp5] Tweak OMP_AFFINITY_FORMAT handling

Hi! With the addition of host teams, it makes a lot of sense to be able to print also the team number and number of teams. This change made it into OpenMP 5.0, together with various changes to mostly the short names, but two long names too. The following adjusts our implementation to match what

[PATCH] PR libstdc++/87538 fix std::not_fn exception specifications

PR libstdc++/87538 * include/std/functional (_Not_fn::operator()): Check value of __is_nothrow_invocable as well. * testsuite/20_util/function_objects/not_fn/87538.cc: New test. Tested x86_64-linux, committed to trunk. I'll backport this to gcc-7 and gcc-8 too. c

Re: [PATCH v3] Change default to -fno-math-errno

On Mon, 8 Oct 2018, Richard Biener wrote: > So I think it would be fine if we'd have -fno-math-errno as documented > and then the C library would annotate their math functions according > to whether they will ever set errno or not. Once a math function is > const or pure it cannot ever set errno

Re: [PATCH] fixincludes: vxworks: regs.h: Guard include of vxTypesOld.h by !_ASMLANGUAGE

On 2018-09-14 14:39, Olivier Hainque wrote: > > >> On 13 Sep 2018, at 00:25, Rasmus Villemoes wrote: > >>> What happens on your end if you just remove the hack ? > >> Unfortunately, the libstdc++ build breaks: >> >> In file included from >> /usr/powerpc-wrs-vxworks/wind_base/target/h/regs.h:66

Re: [PATCH] handle attribute positional arguments consistently (PR 87541, 87542)

On Sun, 7 Oct 2018, Martin Sebor wrote: > While still testing an enhancement in the area of attributes > I ran across bugs and inconsistencies in how different handlers > deal with positional arguments. The bugs are either an ICE due > to the handlers not consistently converting positional argume

Re: [PATCH] Come up with gcc/testsuite/g++.target/i386/i386.dg and move there some tests.

On Mon, Oct 8, 2018 at 1:21 PM Jakub Jelinek wrote: > > On Mon, Oct 08, 2018 at 01:17:14PM +0200, Martin Liška wrote: > > I'm suggesting following patch that comes up with new g++.target subfolder. > > I moved there i386 multiversioning tests. > > I think you want Uros to review and decide this on

Re: [PATCH] Come up with gcc/testsuite/g++.target/i386/i386.dg and move there some tests.

On Mon, Oct 08, 2018 at 01:17:14PM +0200, Martin Liška wrote: > I'm suggesting following patch that comes up with new g++.target subfolder. > I moved there i386 multiversioning tests. I think you want Uros to review and decide this one. > 2018-10-08 Martin Liska > > * gcc.target/i386/i3

[PATCH] Come up with gcc/testsuite/g++.target/i386/i386.dg and move there some tests.

Hi. I'm suggesting following patch that comes up with new g++.target subfolder. I moved there i386 multiversioning tests. Ready for trunk? Martin >From 152e66a766b69019ef6632276579d9fa9f14f4c4 Mon Sep 17 00:00:00 2001 From: marxin Date: Mon, 8 Oct 2018 13:13:23 +0200 Subject: [PATCH] Come up wit

Re: [PATCHv2] Handle not explicitly zero terminated strings in merge sections

Hi Bernd, > On 10/05/18 20:15, Andreas Schwab wrote: >> On Sep 14 2018, Bernd Edlinger wrote: >> >>> diff -Npur gcc/testsuite/gnat.dg/string_merge1.adb >>> gcc/testsuite/gnat.dg/string_merge1.adb >>> --- gcc/testsuite/gnat.dg/string_merge1.adb 1970-01-01 >>> 01:00:00.0 +0100 >>> +++ gcc/

Re: Add new warning flag "warn_prio_ctor_dtor"

Jeff Law writes: > On 9/3/18 8:48 AM, Vinay Kumar wrote: >> Hi Joseph, >> The documentation is of a new option, not of -Wreturn-type >> Done >> you should list the option as -Wno-prio-ctor-dtor when documenting >> Done >> You're not meant to have the literal text ", no ()" in

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

On 08/10/18 11:29, Richard Biener wrote: > On Mon, Oct 8, 2018 at 12:14 PM Martin Liška wrote: >> >> On 10/8/18 11:55 AM, Richard Earnshaw (lists) wrote: >>> On 08/10/18 10:47, Martin Liška wrote: On 10/8/18 10:46 AM, Renlin Li wrote: > Hi Martin, > > pr82625.C failed on compiler

[PATCH][i386] Update Zen tuning for vector load cost

This adjusts Zen AVX256 vector load cost to be twice as expensive than AVX128 vector load cost (twice via ix86_vec_cost keying on TARGET_AVX128_OPTIMAL - should rather use some TARGET_VECTOR_IMPL_WIDTH or so). Likely the current cost value was meant to make AVX256 loads _cheaper_ than two AVX128

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

On 10/8/18 12:46 PM, Jakub Jelinek wrote: > On Mon, Oct 08, 2018 at 12:34:19PM +0200, Martin Liška wrote: gcc/testsuite/g++.dg/ext/mv*.C >>> >>> You cannot move C++ tests to gcc.target/ >> >> I realized that we don't have ./gcc/testsuite/g++.target/i386 yet :/ > > But we want it and there are

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

On Mon, Oct 08, 2018 at 12:34:19PM +0200, Martin Liška wrote: > >> gcc/testsuite/g++.dg/ext/mv*.C > > > > You cannot move C++ tests to gcc.target/ > > I realized that we don't have ./gcc/testsuite/g++.target/i386 yet :/ But we want it and there are multiple tests waiting for that move.

Re: [PATCH] Provide extension hint for aarch64 target (PR driver/83193).

Hi. I'm attaching updated version of the patch. Martin >From d36974540cda9fb0e159103fdcf92d26ef2f1b94 Mon Sep 17 00:00:00 2001 From: marxin Date: Thu, 4 Oct 2018 16:31:49 +0200 Subject: [PATCH] Provide extension hint for aarch64 target (PR driver/83193). gcc/ChangeLog: 2018-10-05 Martin Liska

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

On 10/8/18 12:29 PM, Richard Biener wrote: > On Mon, Oct 8, 2018 at 12:14 PM Martin Liška wrote: >> >> On 10/8/18 11:55 AM, Richard Earnshaw (lists) wrote: >>> On 08/10/18 10:47, Martin Liška wrote: On 10/8/18 10:46 AM, Renlin Li wrote: > Hi Martin, > > pr82625.C failed on compile

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

On Mon, Oct 8, 2018 at 12:14 PM Martin Liška wrote: > > On 10/8/18 11:55 AM, Richard Earnshaw (lists) wrote: > > On 08/10/18 10:47, Martin Liška wrote: > >> On 10/8/18 10:46 AM, Renlin Li wrote: > >>> Hi Martin, > >>> > >>> pr82625.C failed on compiler builds which don't support "default" and > >

Re: [patch] Fix PR tree-optimization/86659

On Fri, Oct 5, 2018 at 10:29 AM Eric Botcazou wrote: > > > So I wonder why it is necessary to track 'reverse' in gimple_match_op > > at all given we bail out without optimizing as far as I can see? > > Because of the valueization? If it is done, gimple_simplify returns true so > the result will b

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

On 10/8/18 11:55 AM, Richard Earnshaw (lists) wrote: > On 08/10/18 10:47, Martin Liška wrote: >> On 10/8/18 10:46 AM, Renlin Li wrote: >>> Hi Martin, >>> >>> pr82625.C failed on compiler builds which don't support "default" and "avx" >>> target. >>> For example, arm/aarch64 native linux gcc compil

Re: [PATCH v3] Change default to -fno-math-errno

On Thu, Oct 4, 2018 at 9:43 PM Joseph Myers wrote: > > On Thu, 4 Oct 2018, Jeff Law wrote: > > > > I doubt you could prove that without LTO of the whole program because an > > > errno value set by a libm function call could always be checked in the > > > caller of whatever function is being compil

Re: [PATCH] avoid warning on constant strncpy until next statement is reachable (PR 87028)

On Thu, Oct 4, 2018 at 5:51 PM Martin Sebor wrote: > > On 10/04/2018 08:58 AM, Jeff Law wrote: > > On 8/27/18 9:42 AM, Richard Biener wrote: > >> On Mon, Aug 27, 2018 at 5:32 PM Jeff Law wrote: > >>> > >>> On 08/27/2018 02:29 AM, Richard Biener wrote: > On Sun, Aug 26, 2018 at 7:26 AM Jeff L

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

On 08/10/18 10:47, Martin Liška wrote: > On 10/8/18 10:46 AM, Renlin Li wrote: >> Hi Martin, >> >> pr82625.C failed on compiler builds which don't support "default" and "avx" >> target. >> For example, arm/aarch64 native linux gcc compiler. >> >> >> As I found in this gcc wiki: https://gcc.gnu.org

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

On 10/8/18 10:46 AM, Renlin Li wrote: > Hi Martin, > > pr82625.C failed on compiler builds which don't support "default" and "avx" > target. > For example, arm/aarch64 native linux gcc compiler. > > > As I found in this gcc wiki: https://gcc.gnu.org/wiki/FunctionMultiVersioning > ''' > This sup

Re: [PATCH] EfficiencySanitizer implementation.

I assume that the compiler based instrumentation, should be more efficient than binary instrumentation. But, I was just interested in the process of implementation for that tool. Sorry for the noise. On 10/07/2018 11:03 AM, Richard Biener wrote: > On October 6, 2018 10:17:48 PM GMT+02:00, Denis Kh

Re: sched2 priorities and replacements

ping, any insight on this? Regards Robin

Re: [PATCH 2/2 v3][IRA,LRA] Fix PR86939, IRA incorrectly creates an interference between a pseudo register and a hard register

On Sat, 6 Oct 2018 at 04:38, Peter Bergner wrote: > > On 10/5/18 4:12 PM, Vladimir Makarov wrote: > > On 10/05/2018 04:00 PM, Peter Bergner wrote: > >> How about non_conflicting_reg_copy or non_conflicting_copy_insn? > > OK. I like the first name more. > > Ok, I committed the patch using the first

Re: [Patch, fortran] PR87151 - allocating array of character

Hi Paul, Your patch works as expected. It also fixes the ICEs for the tests in pr80931 (and the test accidentally attached to pr83196). Thanks for the patch. Dominique

Re: [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625).

Hi Martin, pr82625.C failed on compiler builds which don't support "default" and "avx" target. For example, arm/aarch64 native linux gcc compiler. As I found in this gcc wiki: https://gcc.gnu.org/wiki/FunctionMultiVersioning ''' This support is available in GCC 4.8 and later. Support is only a

Re: [patch] tighten toplevel guard on ibm-ldouble.c

Hi Segher, > On 05 Oct 2018, at 11:35, Segher Boessenkool > wrote: > > I think it looks fine. Okay for trunk after some testing. Thanks for your feedback. I can't get a pristine mainline to build on our powerpc-linux host - SEGVs from the newly built cc1 during libgcc. Updated ulimits helped

Re: [wwwdocs] Add no_sanitize attribute

On 10/7/18 2:15 PM, Gerald Pfeifer wrote: > On Wed, 18 Apr 2018, Martin Liška wrote: >> I would like to mention the attribute in GCC 8 changes. > > Index: htdocs/gcc-8/changes.html > === >> >> New no_sanitize attribute has been

[PATCH] Minor cleanups / PR63155

Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. Richard. 2018-10-08 Richard Biener PR tree-optimization/63155 * tree-ssa-propagate.c (add_ssa_edge): Do cheap check first. (ssa_propagation_engine::ssa_propagate): Remove redundant bitmap bit clear