[PATCH] RTEMS: Enable some libstdc++ features

libstdc++/ * acinclude.m4 (GLIBCXX_ENABLE_LIBSTDCXX_TIME): Add rtems*. (GLIBCXX_ENABLE_FILESYSTEM_TS): Likewise. * configure: Regenerate. --- libstdc++-v3/acinclude.m4 | 5 - libstdc++-v3/configure| 5 - 2 files changed, 8 insertions(+), 2 deletions(-) diff --g

Re: [patch, fortran] Implement maxloc and minloc for character

On Sun, Nov 19, 2017 at 11:11 PM, Thomas Koenig wrote: > There is one question regarding the ABI. Apparently, the string length > is passed as an int even on a 64-bit system. I verified that this > is indeed the case by doing the actual work on a > powerpc64-unknown-linux-gnu box (gcc110 on the gc

Re: [patch, libgfortran] Bug 78549 - [7/8 Regression] Very slow formatted internal file output

On Mon, Nov 20, 2017 at 12:56 AM, Jerry DeLisle wrote: > Hi all, > > After the usual considerable digging around I determined that for the test > case > doing 100 writes to a string that we were allocating 100 newunit > numbers > and the associated unit structures on the unit treap. Cons

Re: [PATCH] Fix bug in simplify_ternary_operation

On 11/20/2017 03:52 AM, Jeff Law wrote: Sorry, it's taken so long to get back to this patch... On 09/01/2017 02:51 AM, Tom de Vries wrote: On 08/31/2017 11:44 PM, Jeff Law wrote: On 08/28/2017 12:26 PM, Tom de Vries wrote: Hi, I think I found a bug in r17465: ...     * cse.c (simplify

Re: [PATCH] Use bswap framework in store-merging (PR tree-optimization/78821)

On Thu, 16 Nov 2017, Jakub Jelinek wrote: > Hi! > > This patch uses the bswap pass framework inside of the store merging > pass to handle adjacent stores which produce together a 16/32/64 bit > store of bswapped value (loaded or from SSA_NAME) or identity (usually > only from SSA_NAME, the code p

RE: [arc] Remove semicolon after do while (0) in FUNCTION_PROFILER

Thanks Tom, Claudiu From: Tom de Vries [tom_devr...@mentor.com] Sent: Sunday, November 19, 2017 1:27 PM To: GCC Patches Cc: Claudiu Zissulescu Subject: [arc] Remove semicolon after do while (0) in FUNCTION_PROFILER Hi, this patch removes a semicolon after

Fix typo breaking bootstrap

Hi, while doing a last minute cleanup, I managed to introduce a typo into the patch, which effectively disables inlining. Sorry for that. Comitted as obvious, Honza PR bootstrap/83062 * ipa-inline.c (can_inline_edge_p): Fix typo in previous patch. Index: ipa-inline.c =

Re: Fix PR81360

> I believe this caused hundreds of new FAILs on both x86_64 and i686-linux. > Seems after this change we no longer inline always_inline functions into > -O0 callers, which is wrong. That's worse than this, inlining is totally broken... -- Eric Botcazou

Re: [RFA][PATCH] 8/n Pull evrp range analyzer into its own file

On Sat, Nov 18, 2017 at 9:00 AM, Jeff Law wrote: > > > > This is just a straight cut-n-paste pulling the evrp_range_analyzer > methods out of gimple-ssa-evrp.c into gimple-ssa-evrp-analyze.[ch]. > > Bootstrapped and regression tested on x86_64. > > > OK for the trunk? Hum. That makes things har

Re: [RFA][PATCH] 9/n Finish moving BB_VISITED handling into range analyzer

On Sat, Nov 18, 2017 at 9:05 AM, Jeff Law wrote: > > I didn't want to rebase my patchset yet again to fix this minor goof. I > moved initialization of BB_VISITED into the range analyzer, but forgot > to move setting it as we visit each block into the analyzer. > > This fixes that oversight. > > B

Re: [RFA][PATCH] 11/n More VRP related cleanups

On Sat, Nov 18, 2017 at 9:49 AM, Jeff Law wrote: > > Not as extensive as the last set. Just getting a couple data members > privatized as well as one method within vr_values. > > I'd really like to just get values_propagated out of vr_values and bury > it in tree-vrp.c, but we're not to that poin

Re: [RFA][PATCH] 10/n Various class definition cleanups

On Sat, Nov 18, 2017 at 9:39 AM, Jeff Law wrote: > > A batch of random cleanups in the various vrp related bits. > > The goal here is to start banging some of the classes into shape. > Included in this patch: > > > For evrp_folder: > Accepts vr_values in its ctor to attach. > Uses DISABLE_COPY

Re: Fix PR81360

> > I believe this caused hundreds of new FAILs on both x86_64 and i686-linux. > > Seems after this change we no longer inline always_inline functions into > > -O0 callers, which is wrong. > > That's worse than this, inlining is totally broken... It was a typo in the conditional (I cleaned it up

Re: [RFC][PATCH 12/n Embed range analysis in DOM

On Sat, Nov 18, 2017 at 10:31 AM, Jeff Law wrote: > And a WIP. I can justify continuing work on this during stage3 for > pr78496. But I thought it was worth giving folks a looksie. > > The goal here is to make tree-vrp's threading obsolete and remove it and > at the same time pick up all the mis

Re: [RFC][PATCH] Change default to -fcommon

On Sun, Nov 19, 2017 at 2:48 AM, Sandra Loosemore wrote: > On 11/17/2017 12:12 PM, Wilco Dijkstra wrote: >> >> GCC currently defaults to -fcommon. This is an optional C feature dating >> back to early C implementations. On many targets this means global >> variable >> accesses having an unnecess

Re: [patch] Do not report non-executed blocks in Ada coverage

> Is this still needed? I know Martin L did another teak for non-executed > blocks in Ada... BUt I don't know enough to determine if it was > sufficient to address this problem. Yes, Martin's patch fixed the regression in Ada so mine is obsolete. -- Eric Botcazou

Re: [committed][PATCH] Fix bogus propagation in DOM

On Sun, Nov 19, 2017 at 9:16 PM, Jeff Law wrote: > On my local branch gcc.dg/torture/pr56349.c fails by sending GCC into an > infinite loop trying to simplify a self-referring statement. ie > something like > > x_1 = x_1 + 10; > > That, of course, shouldn't be happening in SSA form. After some di

Re: VRP: x+1 and -x cannot be INT_MIN

On Sun, Nov 19, 2017 at 11:41 AM, Marc Glisse wrote: > On Mon, 13 Nov 2017, Richard Biener wrote: > >> On Sat, Nov 11, 2017 at 11:03 PM, Marc Glisse >> wrote: >>> >>> Hello, >>> >>> with undefined overflow, just because we know nothing about one of the >>> arguments of an addition doesn't mean we

Re: Fix PR81360

> It was a typo in the conditional (I cleaned it up just before comitting > because I noticed I can merge it with earlier conditional and accidentally > dropped !). It should be fixed now. OK, thanks, unfortunately the bug made it into the latest source snapshot. -- Eric Botcazou

Re: [Diagnostic Patch] don't print column zero

Hi, On 9 November 2017 at 00:25, Jeff Law wrote: > On 11/08/2017 10:36 AM, Nathan Sidwell wrote: >> On 11/02/2017 04:33 PM, Nathan Sidwell wrote: >>> On 10/26/2017 10:34 AM, David Malcolm wrote: [CCing Rainer and Mike for the gcc-dg.exp part] >>> My Tcl skills aren't great, so hopefully

PR82665 - missing value range optimization for memchr

Hi, The attached patch tries to fix PR82665 by adding value-range for 'n' to [0, PTRDIFF_MAX - 1] in the following case: def = memchr(arg, 0, sz); n = def - arg where def and arg are char *. I suppose it's safe to assume that if arg is char *, then memchr(arg, 0, sz) would return a non NULL pointe

Re: Add optabs for common types of permutation

On Mon, Nov 20, 2017 at 12:56 AM, Jeff Law wrote: > On 11/09/2017 06:24 AM, Richard Sandiford wrote: >> ...so that we can use them for variable-length vectors. For now >> constant-length vectors continue to use VEC_PERM_EXPR and the >> vec_perm_const optab even for cases that the new optabs could

Re: PR82665 - missing value range optimization for memchr

On Mon, Nov 20, 2017 at 04:13:49PM +0530, Prathamesh Kulkarni wrote: > Hi, > The attached patch tries to fix PR82665 by adding value-range for 'n' > to [0, PTRDIFF_MAX - 1] in the following case: > def = memchr(arg, 0, sz); > n = def - arg > > where def and arg are char *. I suppose it's safe to a

Re: Improve canonicalisation of TARGET_MEM_REFs

On Tue, Nov 7, 2017 at 7:04 PM, Richard Sandiford wrote: > Richard Biener writes: >> On Fri, Nov 3, 2017 at 5:32 PM, Richard Sandiford >> wrote: >>> A general TARGET_MEM_REF is: >>> >>> BASE + STEP * INDEX + INDEX2 + OFFSET >>> >>> After classifying the address in this way, the code that bui

[PATCH] Don't split call from its call arg location

When a port is using hardware loops (like ARC) makes use of reorg_loops to find and analyze loops that end in loop_end instructions. The very same function can be set to reorder the cfg such that the loop end occurs after the loop start. This task is performed by reorder_loops function which at its

GCC 8.0.0 Status Report (2017-11-20)

Status == GCC 8 is now in Stage 3 which means open for general bugfixing. As usual we're now in a short period where posted but not yet reviewed feature patches can be accepted. As time goes by even those will be no longer appropriate. As usual in this time not all regressions have been pr

Re: [PATCH 08/22] Add Intel CET support for EH in libgcc.

On Sat, Nov 18, 2017 at 9:11 PM, Tsimbalist, Igor V wrote: > I propose the following changes. I do not have ia64 to test. Ok for trunk? Ok with a proper changelog. Richard. > bash-4.2$ svn diff > Index: libgcc/config/cr16/unwind-cr16.c > =

Re: [patch] Add support for #pragma GCC unroll

> If anybody finds the time to push the corresponding Fortran changes then I'd > be grateful. I won't have time for this until end of stage 1... > > https://gcc.gnu.org/ml/fortran/2015-02/msg00014.html OK, I'm going to merge it in the main patch. -- Eric Botcazou

Re: Make ivopts handle calls to internal functions

On Fri, Nov 17, 2017 at 3:03 PM, Richard Sandiford wrote: > ivopts previously treated pointer arguments to internal functions > like IFN_MASK_LOAD and IFN_MASK_STORE as normal gimple values. > This patch makes it treat them as addresses instead. This makes > a significant difference to the code q

Re: Add support for in-order addition reduction using SVE FADDA

On Fri, Nov 17, 2017 at 5:53 PM, Richard Sandiford wrote: > This patch adds support for in-order floating-point addition reductions, > which are suitable even in strict IEEE mode. > > Previously vect_is_simple_reduction would reject any cases that forbid > reassociation. The idea is instead to te

Re: [patch] Add support for #pragma GCC unroll

> Looking at the middle-end changes. The change to ANNOTATE_EXPR to three > operands is approved also for existing frontends (just in case you > don't get review). > Found the missing possibility of an argument limiting myself... I see. ;-) > Your changes to the RTL unrolling pass as far as I se

Re: PING Fwd: [patch] implement generic debug() for vectors and hash sets

Minor oversight... debug_vec_tree() no longer exist. I forgot to remove the prototype. Also, gdbinit.in has a macro that uses it, but this is no longer necessary as we can print tree vectors generically with "print debug(xxx)". Applied as obvious. Aldy On Sun, Nov 19, 2017 at 5:45 PM, Jeff Law

Re: [PATCH GCC]Support load in CT_STORE_STORE chain if dominated by store in the same loop iteration

On Fri, Nov 17, 2017 at 2:49 PM, Bin Cheng wrote: > Hi, > I previously introduced CT_STORE_STORE chains in predcom. This patch further > supports load > reference in CT_STORE_STORE chain if the load is dominated by a store > reference in the same > loop iteration. So example as in added test c

Re: [patch] Add support for #pragma GCC unroll

On 20 November 2017 at 12:26, Eric Botcazou wrote: >> If anybody finds the time to push the corresponding Fortran changes then I'd >> be grateful. I won't have time for this until end of stage 1... >> >> https://gcc.gnu.org/ml/fortran/2015-02/msg00014.html > > OK, I'm going to merge it in the main

Re: Add unroll-and-jam pass v2

On Fri, Nov 17, 2017 at 2:58 PM, Michael Matz wrote: > Hi, > > so I've dusted off and improved the implementation of unroll-and-jam from > last year. The changes relative to last submission are: > > * corrected feasibility of the transform (i.e. that dependency directions > are correctly retain

Fix gcc-7 and gcc-8 build of GO for Hurd and not kFreeBSD in debian/rules.defs

On Thu, 2017-11-16 at 20:39 +0100, Svante Signell wrote: Seeing the recent update of debian/rules.defs in gcc-7 a mistake was revealed in the patch debian_rules.defs for both gcc-7 and gcc-8. The correct patch is inlined below: --- a/debian/rules.defs 2017-11-20 12:59:25.0 +0100 +++ b/deb

Re: [Diagnostic Patch] don't print column zero

On 11/20/2017 05:41 AM, Christophe Lyon wrote: I have just committed (r254949) the attached patch to fix a regression in the arm tests after this was committed (r254691). I hope it's obvious enough. I certainly think so. thanks! nathan -- Nathan Sidwell

Re: Add optabs for common types of permutation

Richard Biener writes: > On Mon, Nov 20, 2017 at 12:56 AM, Jeff Law wrote: >> On 11/09/2017 06:24 AM, Richard Sandiford wrote: >>> ...so that we can use them for variable-length vectors. For now >>> constant-length vectors continue to use VEC_PERM_EXPR and the >>> vec_perm_const optab even for c

Re: [C++ PATCH] Fix constexpr VEC_COND_EXPR handling (PR c++/82781)

On 11/20/2017 02:42 AM, Jakub Jelinek wrote: Hi! VEC_COND_EXPR is handled in constexpr code like COND_EXPR, but that is wrong. VEC_COND_EXPR is more like an arbitrary arithmetics ternary operation, we need to compute all 3 arguments and based on the elements of the first argument pick up elemen

[PATCH 1/4] [SPARC] Errata workaround for GRLIB-TN-0012

This patch provides a workaround for the errata described in GRLIB-TN-0012. If the workaround is enabled it will: * Prevent any floating-point operation from being placed in the delay slot of an annulled integer branch. * Place a NOP at the branch target of an integer branch if it is a float

[PATCH 0/4] [SPARC] Workarounds for UT699, UT700, and GR712RC errata

Hello, This patch series adds workarounds for the newly discovered errata for UT699, UT700, and GR712RC. The errata and possible workarounds are described in the following documents available at http://www.gaisler.com/index.php/information/app-tech-notes: GRLIB-TN-0010 - LEON3/FT AHB Deadlock

[PATCH 4/4] [SPARC] Errata workaround for GRLIB-TN-0013

This patch provides a workaround for the errata described in GRLIB-TN-0013. If the workaround is enabled it will: * Prevent div and sqrt instructions in the delay slot. * Insert NOPs to prevent the sequence (div/sqrt) -> (two or three floating point operations or loads) -> (div/sqrt). * Not i

[PATCH 2/4] [SPARC] Errata workaround for GRLIB-TN-0011

This patch provides a workaround for the errata described in GRLIB-TN-0011. If the workaround is enabled it will: * Insert .align 16 before atomic instructions (swap, ldstub, casa). It is applicable to GR712RC. gcc/ChangeLog: 2017-11-17 Daniel Cederman * config/sparc/sync.md (swaps

[PATCH 3/4] [SPARC] Errata workaround for GRLIB-TN-0010

This patch provides a workaround for the errata described in GRLIB-TN-0010. If the workaround is enabled it will: * Insert a NOP between load instruction and atomic instruction (swap, ldstub, casa). * Insert a NOP at branch target if load in delay slot and atomic instruction at branch target

Re: Improve canonicalisation of TARGET_MEM_REFs

On Mon, Nov 20, 2017 at 11:02 AM, Richard Biener wrote: > On Tue, Nov 7, 2017 at 7:04 PM, Richard Sandiford > wrote: >> Richard Biener writes: >>> On Fri, Nov 3, 2017 at 5:32 PM, Richard Sandiford >>> wrote: A general TARGET_MEM_REF is: BASE + STEP * INDEX + INDEX2 + OFFSET >

Re: [PR c++/82836] Fixe testcase

On 11/19/2017 07:38 AM, Rainer Orth wrote: Ok for mainline, or would you rather make the use of __int128 and __float128 conditional? Patch is good. I'd rather perturb the source itself as little as possible, and I've verified it still ICEs an unfixed x86_64 compiler. thanks, nathan -- Na

Re: Add support for in-order addition reduction using SVE FADDA

Richard Biener writes: > On Fri, Nov 17, 2017 at 5:53 PM, Richard Sandiford > wrote: >> This patch adds support for in-order floating-point addition reductions, >> which are suitable even in strict IEEE mode. >> >> Previously vect_is_simple_reduction would reject any cases that forbid >> reassoci

Re: [PATCH][AArch64] Restrict POST_INC operand in aarch64_simd_mem_operand_p to register

Thanks for the review! Could you also please commit this patch for me? I don’t have commit rights. Thanks, Dominik > On 17 Nov 2017, at 23:18, James Greenhalgh wrote: > > On Tue, Oct 31, 2017 at 02:47:29PM +0100, Dominik Inführ wrote: >> Hi, >> >> I have a custom optimization pass, that moves

Re: [014/nnn] poly_int: indirect_refs_may_alias_p

Jeff Law writes: > On 10/23/2017 11:05 AM, Richard Sandiford wrote: >> This patch makes indirect_refs_may_alias_p use ranges_may_overlap_p >> rather than ranges_overlap_p. Unlike the former, the latter can handle >> negative offsets, so the fix for PR44852 should no longer be necessary. >> It can

Re: Fix gcc-7 and gcc-8 build of GO for Hurd and not kFreeBSD in debian/rules.defs

On 2017-11-20 13:20, Svante Signell wrote: > On Thu, 2017-11-16 at 20:39 +0100, Svante Signell wrote: > > Seeing the recent update of debian/rules.defs in gcc-7 a mistake was revealed > in > the patch debian_rules.defs for both gcc-7 and gcc-8. The correct patch is > inlined below: > > --- a/deb

Re: Fix gcc-7 and gcc-8 build of GO for Hurd and not kFreeBSD in debian/rules.defs

On Mon, 2017-11-20 at 14:04 +0100, Aurelien Jarno wrote: > On 2017-11-20 13:20, Svante Signell wrote: > > On Thu, 2017-11-16 at 20:39 +0100, Svante Signell wrote: > > > > Seeing the recent update of debian/rules.defs in gcc-7 a mistake was > > revealed in the patch debian_rules.defs for both gcc-7

Re: [PATCH] Fix test-suite fallout of default -Wreturn-type.

On 11/19/2017 01:56 PM, Thomas Schwinge wrote: > Hi! > > On Wed, 18 Oct 2017 14:48:13 +0200, Martin Liška wrote: >> This is second patch that addresses test-suite fallout. All these tests fail >> because -Wreturn-type is >> now on by default. >> >> Patch can bootstrap on ppc64le-redhat-linux and

Re: [PATCH] make canonicalize_condition keep its promise

On Sun, 2017-11-19 at 16:44 -0700, Jeff Law wrote: > On 11/15/2017 08:40 AM, Aaron Sawdey wrote: > > So, the story of this very small patch starts with me adding > > patterns > > for ppc instructions bdz[tf] and bdnz[tf] such as this: > > > >   [(set (pc) > > (if_then_else > >   (and > >

[PATCH] Fix Werror=stringop-overflow in target.c

Hello. This is fix of compilation error I see with --enable-offload-targets=nvptx-none=. It's explained in very detail way here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83007#c1 Ready for trunk? Martin libgomp/ChangeLog: 2017-11-20 Martin Liska * target.c (gomp_target_init): U

Re: [RFTesting] New POINTER_DIFF_EXPR

On Sun, Nov 19, 2017 at 6:54 PM, Marc Glisse wrote: > new version, regtested on powerpc64le-unknown-linux-gnu. The front-end parts > are up for review. The C++ changes are OK. Jason

Re: [PATCH] Fix test-suite fallout of default -Wreturn-type.

On Sun, Nov 19, 2017 at 7:56 AM, Thomas Schwinge wrote: > OK to fix the first four issues as follows? If approving this, please > respond with "Reviewed-by: NAME " so that your effort will be > recorded. See . OK. Reviewed-by: Jason Merrill

Re: VRP: x+1 and -x cannot be INT_MIN

On Mon, 20 Nov 2017, Richard Biener wrote: I had to adapt one testcase where for VR_VARYING | [1, 1] we used to produce ~[0, 0] and now produce [-INT_MAX, INT_MAX]. I am surprised at how late the transformation now happens (only after removing __builtin_unreachable, in forwprop3, while trunk cur

Re: [PATCH][ARM] Fix test armv8_2-fp16-move-1.c

Hi, On 17 November 2017 at 12:12, Kyrill Tkachov wrote: > > On 17/11/17 10:45, Sudi Das wrote: >> >> Hi Kyrill >> >> Thanks I have made the change. > > > Thanks Sudi, I've committed this on your behalf with r254863. > > Kyrill > > >> Sudi >> >> >> >> From: Kyrill Tkachov >> Sent: Thursday, Nove

Re: [v3 PATCH] Implement LWG 2353

On 19/11/17 02:40 +0200, Ville Voutilainen wrote: --- /dev/null +++ b/libstdc++-v3/testsuite/24_iterators/operations/lwg2353.cc @@ -0,0 +1,26 @@ +// { dg-options "-D_GLIBCXX_CONCEPT_CHECKS" } +// { dg-do run { target c++11 } } + +#include +#include +#include +#include +#include + +template +

Re: [PATCH] RTEMS: Enable some libstdc++ features

On 20/11/17 09:03 +0100, Sebastian Huber wrote: libstdc++/ * acinclude.m4 (GLIBCXX_ENABLE_LIBSTDCXX_TIME): Add rtems*. (GLIBCXX_ENABLE_FILESYSTEM_TS): Likewise. * configure: Regenerate. OK, thanks.

Re: [PATCH][ARM] Fix test armv8_2-fp16-move-1.c

On 20/11/17 14:14, Christophe Lyon wrote: Hi, On 17 November 2017 at 12:12, Kyrill Tkachov wrote: On 17/11/17 10:45, Sudi Das wrote: Hi Kyrill Thanks I have made the change. Thanks Sudi, I've committed this on your behalf with r254863. Kyrill Sudi From: Kyrill Tkachov Sent: Thurs

Re: [PATCH][aarch64] Fix pr81356 - copy empty string with wrz, not a ldrb/strb

On 17 November 2017 at 22:41, James Greenhalgh wrote: > On Fri, Sep 15, 2017 at 07:22:39PM +0100, Steve Ellcey wrote: >> PR 81356 points out that doing a __builtin_strcpy of an empty string on >> aarch64 does a copy from memory instead of just writing out a zero byte. >> In looking at this I found

Re: [patch] Add support for #pragma GCC unroll

On Mon, Nov 20, 2017 at 12:57:47PM +0100, Bernhard Reutner-Fischer wrote: > On 20 November 2017 at 12:26, Eric Botcazou wrote: > >> If anybody finds the time to push the corresponding Fortran changes then > >> I'd > >> be grateful. I won't have time for this until end of stage 1... > >> > >> http

Re: [PATCH GCC]A simple implementation of loop interchange

On Thu, Nov 16, 2017 at 4:18 PM, Bin.Cheng wrote: > On Tue, Oct 24, 2017 at 3:30 PM, Michael Matz wrote: >> Hello, >> >> On Fri, 22 Sep 2017, Bin.Cheng wrote: >> >>> This is updated patch for loop interchange with review suggestions >>> resolved. Changes are: >>> 1) It does more light weight c

Re: Fix gcc-7 and gcc-8 build of GO for Hurd and not kFreeBSD in debian/rules.defs

On 2017-11-20 14:31, Svante Signell wrote: > On Mon, 2017-11-20 at 14:04 +0100, Aurelien Jarno wrote: > > On 2017-11-20 13:20, Svante Signell wrote: > > > On Thu, 2017-11-16 at 20:39 +0100, Svante Signell wrote: > > > > > > Seeing the recent update of debian/rules.defs in gcc-7 a mistake was > > >

Re: VRP: x+1 and -x cannot be INT_MIN

On Mon, Nov 20, 2017 at 3:10 PM, Marc Glisse wrote: > On Mon, 20 Nov 2017, Richard Biener wrote: > >>> I had to adapt one testcase where for VR_VARYING | [1, 1] we used to >>> produce >>> ~[0, 0] and now produce [-INT_MAX, INT_MAX]. I am surprised at how late >>> the >>> transformation now happens

Re: [PATCH 1/7]: SVE: Add CLOBBER_HIGH expression

> On 17 Nov 2017, at 19:31, Jeff Law wrote: > > On 11/16/2017 11:50 AM, Alan Hayward wrote: >> >>> On 16 Nov 2017, at 18:24, Richard Biener wrote: >>> >>> On November 16, 2017 7:05:30 PM GMT+01:00, Jeff Law wrote: On 11/16/2017 05:34 AM, Alan Hayward wrote: > This is a set of patche

RE: [RFC, vectorizer] Allow half_type for left shift in vect_operation_fits_smaller_type?

Hi Richard, >Not digged long into this "interesting" function but this case is only valid if type == >final type and if the result is not shifted back. vect_recog_over_widening_pattern >works on a whole sequence of stmts after all, thus > > b = (T_PROMOTED) a; > c = b << 2; > d = b >> 2; > e

Re: [RFC][PATCH] Change default to -fcommon

Richard Biener wrote: > A target specific default might be a good idea if we decide to revert. > > Note I proposed this change a few times already, but the fear was always > we'll break too much legacy code. It will definitely break some code, but new warnings with -Werror might too... > Note y

Re: [RFA][PATCH] 8/n Pull evrp range analyzer into its own file

On 11/20/2017 03:05 AM, Richard Biener wrote: > On Sat, Nov 18, 2017 at 9:00 AM, Jeff Law wrote: >> >> >> >> This is just a straight cut-n-paste pulling the evrp_range_analyzer >> methods out of gimple-ssa-evrp.c into gimple-ssa-evrp-analyze.[ch]. >> >> Bootstrapped and regression tested on x86_64

Re: Adjust empty class parameter passing ABI (PR c++/60336)

On Thu, Nov 16, 2017 at 02:20:59PM -0500, Jason Merrill wrote: > On Thu, Nov 16, 2017 at 12:41 PM, Marek Polacek wrote: > > On Tue, Nov 14, 2017 at 07:34:54AM +0100, Richard Biener wrote: > >> On November 14, 2017 6:21:41 AM GMT+01:00, Jason Merrill > >> wrote: > >> >On Mon, Nov 13, 2017 at 1:02

Re: [PATCH libstdc++/66689] comp_ellint_3 and ellint_3 return garbage values

This patch has introduced new regressions on at least PowerPC and AArch64. FAIL: ext/special_functions/hyperg/check_value.cc execution test FAIL: tr1/5_numerical_facilities/special_functions/17_hyperg/check_value.cc execution test Thanks, David

RFC: SAFE_MACRO_STMT

Hi, when writing macros that are intended to be used as if they were single statements, there are a couple of common problems: 1. Ending in semicolon ... #define foo stmt; ... This works fine if we use it like: ... void bar (void) { foo; } ... but we get an "else without a previous if" err

Re: [RFC][PATCH 12/n Embed range analysis in DOM

On 11/20/2017 03:13 AM, Richard Biener wrote: > On Sat, Nov 18, 2017 at 10:31 AM, Jeff Law wrote: >> And a WIP. I can justify continuing work on this during stage3 for >> pr78496. But I thought it was worth giving folks a looksie. >> >> The goal here is to make tree-vrp's threading obsolete and

Re: [libstdc++] Expose Airy functions.

On 18/11/17 20:33 -0500, Ed Smith-Rowland wrote: Here is the final patch fir libstdc++ Airy functions... OK for trunk, thanks.

Re: [PATCH libstdc++/66689] comp_ellint_3 and ellint_3 return garbage values

On 18/11/17 11:49 -0500, Ed Smith-Rowland wrote: On 11/17/2017 03:54 PM, Jonathan Wakely wrote: Hmm, you're probably right. I'd be tempted to though. I had an idea.  What about a macro _GLIBCXX_ELLINT_3_POS_NU or something that: 1. would allow users to detect which convention is on by defau

Re: std::advance istreambuf_iterator overload

On 20/11/17 07:40 +0100, François Dumont wrote: Here is the latest version I plan to commit after validation. I like the simplified logic for the while-loop. I'd like to keep the change to the money_get/get/[char/wchar_t]/9.cc tests. At the moment those tests passes only because there is no

Re: [RFA][PATCH] 8/n Pull evrp range analyzer into its own file

On November 20, 2017 4:46:08 PM GMT+01:00, Jeff Law wrote: >On 11/20/2017 03:05 AM, Richard Biener wrote: >> On Sat, Nov 18, 2017 at 9:00 AM, Jeff Law wrote: >>> >>> >>> >>> This is just a straight cut-n-paste pulling the evrp_range_analyzer >>> methods out of gimple-ssa-evrp.c into gimple-ssa-ev

Re: Adjust empty class parameter passing ABI (PR c++/60336)

On November 20, 2017 4:51:04 PM GMT+01:00, Marek Polacek wrote: >On Thu, Nov 16, 2017 at 02:20:59PM -0500, Jason Merrill wrote: >> On Thu, Nov 16, 2017 at 12:41 PM, Marek Polacek >wrote: >> > On Tue, Nov 14, 2017 at 07:34:54AM +0100, Richard Biener wrote: >> >> On November 14, 2017 6:21:41 AM GM

Re: [PATCH, rs6000] Testcase updates for power9 codegen

Hi! On Fri, Nov 17, 2017 at 11:30:27AM -0600, Will Schmidt wrote: > [testsuite] > * fold-vec-neg-int.c: Specify -mcpu=power8 Dot at end of sentence (quite a few times), please. > -/* { dg-final { scan-assembler-times "vspltisw|vxor" 1 } } */ > +//# Power9 added xxspltib instruction. > +/*

Re: [PATCH] Add _Float/_FloatX rounding built-ins & improve gimple optimization of _Float/_FloatX built-in functions

Hi! On Fri, Nov 17, 2017 at 07:35:05PM -0500, Michael Meissner wrote: > Here is the fixed patch. It fixes the btrunc2 insn to use the correct > XSRPQI variant for truncf128. I added the float128-hw11.c test as a runtime > test to make sure round, trunc, ceil, and floor return the correct values.

Re: [RFC][PATCH] Change default to -fcommon

Hi, On Mon, 20 Nov 2017, Wilco Dijkstra wrote: > > Note you have to make sure GFortran still works! So I think the patch > > should be changed to make the default behavior be frontend dependent > > or have a fortran/ adjustment that fixes things up for the fortran > > dialects that need it. >

Re: [Patch][aarch64] Use IFUNCs to enable LSE instructions in libatomic on aarch64

Re-ping with a CC to the Aarch64 maintainers. Steve Ellcey sell...@cavium.com On Tue, 2017-10-24 at 11:11 -0700, Steve Ellcey wrote: > Ping. > > Steve Ellcey > sell...@cavium.com > > On Tue, 2017-10-03 at 11:57 -0700, Steve Ellcey wrote: > > > > On Mon, 2017-10-02 at 15:38 +0100, Szabolcs Nagy

Re: [PATCH] Add _Float/_FloatX rounding built-ins & improve gimple optimization of _Float/_FloatX built-in functions

On Mon, Nov 20, 2017 at 11:32:08AM -0600, Segher Boessenkool wrote: > Hi! > > On Fri, Nov 17, 2017 at 07:35:05PM -0500, Michael Meissner wrote: > > Here is the fixed patch. It fixes the btrunc2 insn to use the correct > > XSRPQI variant for truncf128. I added the float128-hw11.c test as a runtim

Re: [Patch][aarch64] Use IFUNCs to enable LSE instructions in libatomic on aarch64

On Mon, Nov 20, 2017 at 05:39:25PM +, Steve Ellcey wrote: > Re-ping with a CC to the Aarch64 maintainers. If I'm completely honest with myself, I don't know enough about this area to review the patch. Szabolcs' OK holds a lot of weight with me, but I'd like to understand more of the top-level

Re: Patch ping

On 11/20/2017 02:55 AM, Jakub Jelinek wrote: Hi! http://gcc.gnu.org/ml/gcc-patches/2017-11/msg01026.html C++2A P0329R4: Designated Initialization OK, thanks -- Nathan Sidwell

Re: [patch, fortran] Implement maxloc and minloc for character

Am 20.11.2017 um 09:30 schrieb Janne Blomqvist: On Sun, Nov 19, 2017 at 11:11 PM, Thomas Koenig wrote: There is one question regarding the ABI. Apparently, the string length is passed as an int even on a 64-bit system. I verified that this is indeed the case by doing the actual work on a powerp

Re: Patch ping

On 11/20/2017 02:55 AM, Jakub Jelinek wrote: http://gcc.gnu.org/ml/gcc-patches/2017-11/msg00851.html C++2A P0428R2 - familiar template syntax for generic lambdas Are there existing testcases checking this is permitted w/o warning under the appropriate circumstances? That seems to be th

Re: [committed][PATCH] Fix bogus propagation in DOM

On 11/20/2017 03:25 AM, Richard Biener wrote: > On Sun, Nov 19, 2017 at 9:16 PM, Jeff Law wrote: >> On my local branch gcc.dg/torture/pr56349.c fails by sending GCC into an >> infinite loop trying to simplify a self-referring statement. ie >> something like >> >> x_1 = x_1 + 10; >> >> That, of cou

Re: [patches] Re: [PATCH] RISC-V: Implement __umulsidi3, umul_ppmm and __muluw3

On Sun, 19 Nov 2017 23:31:56 PST (-0800), ja...@redhat.com wrote: On Sun, Nov 19, 2017 at 08:53:00PM -0800, Jim Wilson wrote: > 2017-11-24 Kito Cheng > > * longlong.h [__riscv] (__umulsidi3): Define. > [__riscv] (umul_ppmm) Likewise. > [__riscv] (__muluw3) Likewise.

[PATCH] avoid assuming strncat/strncpy don't change length of source string (PR 83075)

Unlike strcat and strcpy, it is valid for strncat and strncpy to result in modifying the source string by overwriting its terminating nul. The attached patch removes an assumption to the contrary introduced with the -Wstringop-truncation enhancement. Martin PR tree-optimization/83075 - Invalid s

Re: [Patch][aarch64] Use IFUNCs to enable LSE instructions in libatomic on aarch64

On Mon, 2017-11-20 at 18:27 +, James Greenhalgh wrote: > > If you have the time, would you mind giving me a quick run-down of what > design decisions went in to this patch, and why they are the right thing > to do? Sorry to offload that, but it will be the most efficient route > to a review.

Re: [PATCH] avoid assuming strncat/strncpy don't change length of source string (PR 83075)

On Mon, Nov 20, 2017 at 12:15:09PM -0700, Martin Sebor wrote: > PR tree-optimization/83075 > * tree-ssa-strlen.c (handle_builtin_stxncpy): Avoid assuming > strncat/strncpy don't change length of source string. > > gcc/testsuite/ChangeLog: > > PR tree-optimization/83075 >

Re: [patch] Add support for #pragma GCC unroll

On 11/17/2017 03:23 AM, Eric Botcazou wrote: Index: doc/extend.texi === --- doc/extend.texi (revision 254797) +++ doc/extend.texi (working copy) @@ -22376,6 +22376,18 @@ void ignore_vec_dep (int *a, int k, int @} @end smal

[PATCH, i386]: Add bswaphi2 insn pattern

Hello! Attached patch introduces bswaphi2 named insn pattern that results in movbe instruction. Without the patch, the following testcase:

Re: [PATCH, i386]: Add bswaphi2 insn pattern

Hello! Attached patch introduces bswaphi2 named insn pattern that results in movbe instruction. Without the patch, the following testcase: void baz (char *buf, unsigned int data) { buf[0] = data >> 8; buf[1] = data; } compiles to (-O2 -march=haswell): rolw$8, %si movw

Re: [RFC][PATCH] Change default to -fcommon

On 11/20/2017 10:34 AM, Michael Matz wrote: What's your rationale for changing this? In your initial mail you said: "On many targets this means global variable accesses having an unnecessary codesize and performance penalty in C code (the same source generates better code when built as C++)."

[PATCH] PR 53796 Improve INQUIRE(RECL=...) handling

The current F2018 draft (N2137) specifies behavior of the RECL= specifier in the INQUIRE statement, where it previously was left as undefined. Namely: - If the unit is not connected, RECL= should be given the value -1. - If the unit is connected with stream access, RECL= should be given the valu

Re: [PATCH] rs6000: Don't touch below the stack pointer (PR77687)

On Tue, Sep 19, 2017 at 09:21:50PM +, Segher Boessenkool wrote: > With the 32-bit SVR4 ABI we don't have a red zone, so we have to restore > the callee-saved registers before we restore the stack pointer. > > The previous fix for this PR failed in two ways, for huge frames: first, > we use a n

Re: [PATCH, rs6000] Testcase updates for power9 codegen

On Mon, 2017-11-20 at 11:23 -0600, Segher Boessenkool wrote: > Hi! > > On Fri, Nov 17, 2017 at 11:30:27AM -0600, Will Schmidt wrote: > > [testsuite] > > * fold-vec-neg-int.c: Specify -mcpu=power8 > > Dot at end of sentence (quite a few times), please. > > > -/* { dg-final { scan-assembler-ti

  1   2   >