[wwwdocs] gcc-9/changes.html - Thread Building Blocks got a new home

2019-08-31 Thread Gerald Pfeifer
Committed. Gerald Index: changes.html === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-9/changes.html,v retrieving revision 1.75 diff -u -r1.75 changes.html --- changes.html14 Aug 2019 11:18:43 - 1.75 +++ changes.html

[C++ PATCH] Add source location to TRAIT_EXPR.

2019-08-31 Thread Jason Merrill
Since TRAIT_EXPR is exceptional, maybe_wrap_with_location won't wrap it, so we need to put its location in the TRAIT_EXPR node itself. Tested x86_64-pc-linux-gnu, applying to trunk. * cp-tree.h (TRAIT_EXPR_LOCATION): New. (struct tree_trait_expr): Add locus field. *

[PATCH] PR fortran/91552 -- Walk array constructor to do type conversion

2019-08-31 Thread Steve Kargl
The attached patch has been built and tested on i586-*-freebsd and x86_64-*-freebsd. OK to commit? The patch fixes an ICE during type conversion where an array constructor contains another array. The new function recursively walks the constructor, and tries to do the type conversion. The

Re: [PATCH] rs6000: Make CSE'ing __tls_get_addr calls possible

2019-08-31 Thread Segher Boessenkool
On Sat, Aug 31, 2019 at 02:17:30PM -0500, Segher Boessenkool wrote: > Hi all, > > On Sat, Mar 23, 2019 at 11:46:12PM +, Segher Boessenkool wrote: > > CSE does not consider calls, not even const calls. This patch puts a > > REG_EQUAL note on the pseudo we assign the __tls_get_addr result to,

Re: [PATCH] rs6000: Make CSE'ing __tls_get_addr calls possible

2019-08-31 Thread Segher Boessenkool
Hi all, On Sat, Mar 23, 2019 at 11:46:12PM +, Segher Boessenkool wrote: > CSE does not consider calls, not even const calls. This patch puts a > REG_EQUAL note on the pseudo we assign the __tls_get_addr result to, > so that those pseudos can be CSE'd and the extra calls deleted as dead >

[PATCH] rs6000: Fix darn-3.c for GCC 8 and GCC 7

2019-08-31 Thread Segher Boessenkool
Apparently I didn't properly test the testcase backport to GCC 8 and GCC 7. This makes it not fail there. Tested (properly this time) on everything everywhere; committing. Segher 2019-08-31 Segher Boessenkool gcc/testsuite/ PR target/91481 * gcc.target/powerpc/darn-3.c:

Re: [PATCH] Fix up go regressions caused by my recent switchconv changes (PR go/91617)

2019-08-31 Thread Richard Biener
On August 31, 2019 7:41:17 PM GMT+02:00, Jakub Jelinek wrote: >On Sat, Aug 31, 2019 at 07:23:35PM +0200, Richard Biener wrote: >> Hmm, couldn't we make range_check_type_for take an argument whether >signed >> or unsigned type is required? That is, what do we do if the caller >wants >> a signed

Re: [Patch, fortran] Implementation of F2018 SELECT RANK

2019-08-31 Thread Steve Kargl
On Sat, Aug 31, 2019 at 04:59:03PM +0100, Paul Richard Thomas wrote: > > Bootstraps and regtests on FC29/x86_64 - OK for trunk? Well, I've made it through to the trans-* files. Reading that part of the patch will take a awhile. I'm think you should commit. -- steve

Re: [PATCH] Fix up go regressions caused by my recent switchconv changes (PR go/91617)

2019-08-31 Thread Jakub Jelinek
On Sat, Aug 31, 2019 at 07:23:35PM +0200, Richard Biener wrote: > Hmm, couldn't we make range_check_type_for take an argument whether signed > or unsigned type is required? That is, what do we do if the caller wants > a signed type? Leaving it unspecified what the function returns is odd. I

Re: [Patch, fortran] Implementation of F2018 SELECT RANK

2019-08-31 Thread Steve Kargl
On Sat, Aug 31, 2019 at 06:34:43PM +0100, Paul Richard Thomas wrote: > Hi Steve, > > > > > > If an error occurs, should this set m = MATCH_ERROR and goto cleanup? > > > > OR, set m = MATCH_ERROR, free expr1 and expr2 and return m? > > > > IOW, if an error occurs, why should gfortran continue to

Re: [Patch, fortran] Implementation of F2018 SELECT RANK

2019-08-31 Thread Steve Kargl
In resolve_select_rank you have a comment about casading error. + /* Loop over RANK cases. Note that returning on the errors causes a + cascade of further errors because the case blocks do not compile + correctly. */ Shouldn't gfortran stop looping if an error occurs? See below...

Re: [Patch, fortran] Implementation of F2018 SELECT RANK

2019-08-31 Thread Paul Richard Thomas
Hi Steve, > > > If an error occurs, should this set m = MATCH_ERROR and goto cleanup? > > > OR, set m = MATCH_ERROR, free expr1 and expr2 and return m? > > > IOW, if an error occurs, why should gfortran continue to match select > > > rank? This prevents or reduces the deluge of errors that

Re: [PATCH] Fix up go regressions caused by my recent switchconv changes (PR go/91617)

2019-08-31 Thread Richard Biener
On August 31, 2019 3:12:07 PM GMT+02:00, Jakub Jelinek wrote: >Hi! > >Apparently my recent tree-{cfg,switch-conversion}.c changes broke a >bunch of >go tests. >The problem is that range_check_type actually doesn't guarantee an >unsigned >type; it forces integer type for enum/bool (that was what

[doc] doc/generic.texi - minor markup improvement

2019-08-31 Thread Gerald Pfeifer
I've had this in my tree for months; time to push this out. Committed. Gerald 2019-08-31 Gerald Pfeifer * doc/generic.texi (Unary and Binary Expressions): Mark up an instance of TYPE_MIN. Index: doc/generic.texi

Re: [Patch, fortran] Implementation of F2018 SELECT RANK

2019-08-31 Thread Steve Kargl
On Sat, Aug 31, 2019 at 10:12:55AM -0700, Steve Kargl wrote: > On Sat, Aug 31, 2019 at 09:56:52AM -0700, Steve Kargl wrote: > > On Sat, Aug 31, 2019 at 04:59:03PM +0100, Paul Richard Thomas wrote: > > > + > > > + /* Match a SELECT RANK statement. */ > > > + > > > + match > > > +

Re: [Patch, fortran] Implementation of F2018 SELECT RANK

2019-08-31 Thread Steve Kargl
On Sat, Aug 31, 2019 at 09:56:52AM -0700, Steve Kargl wrote: > On Sat, Aug 31, 2019 at 04:59:03PM +0100, Paul Richard Thomas wrote: > > + > > + /* Match a SELECT RANK statement. */ > > + > > + match > > + gfc_match_select_rank (void) > > + { > > + gfc_expr *expr1, *expr2 = NULL; > > + match

Re: [Patch, fortran] Implementation of F2018 SELECT RANK

2019-08-31 Thread Steve Kargl
On Sat, Aug 31, 2019 at 04:59:03PM +0100, Paul Richard Thomas wrote: > + > + /* Match a SELECT RANK statement. */ > + > + match > + gfc_match_select_rank (void) > + { > + gfc_expr *expr1, *expr2 = NULL; > + match m; > + char name[GFC_MAX_SYMBOL_LEN]; > + gfc_symbol *sym, *sym2; > +

New Spanish PO file for 'gcc' (version 9.1.0)

2019-08-31 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the Spanish team of translators. The file is available at: https://translationproject.org/latest/gcc/es.po (This file, 'gcc-9.1.0.es.po', has

[Patch, fortran] Implementation of F2018 SELECT RANK

2019-08-31 Thread Paul Richard Thomas
When I started on this about three months ago, I thought that with SELECT TYPE as a template this was going to be low hanging fruit. Not so :-) Among the issues on the way were: class selectors; unlimited polymorphic selectors even more so; and error recovery. It's a good starting point but I am

Re: [PATCH] Fix up go regressions caused by my recent switchconv changes (PR go/91617)

2019-08-31 Thread Ian Lance Taylor via gcc-patches
On Sat, Aug 31, 2019 at 6:12 AM Jakub Jelinek wrote: > > Hi! > > Apparently my recent tree-{cfg,switch-conversion}.c changes broke a bunch of > go tests. > The problem is that range_check_type actually doesn't guarantee an unsigned > type; it forces integer type for enum/bool (that was what was

Re: [SVE] PR86753

2019-08-31 Thread Prathamesh Kulkarni
On Fri, 30 Aug 2019 at 16:15, Richard Biener wrote: > > On Wed, Aug 28, 2019 at 11:02 AM Richard Sandiford > wrote: > > > > Prathamesh Kulkarni writes: > > > On Tue, 27 Aug 2019 at 21:14, Richard Sandiford > > > wrote: > > >> > > >> Richard should have the final say, but some comments... > >

Re: [PATCH, i386]: Do not limit the cost of moves to/from XMM register to minimum 8.

2019-08-31 Thread Richard Biener
On August 31, 2019 2:51:51 AM GMT+02:00, Alan Modra wrote: >On Fri, Aug 30, 2019 at 09:42:06AM +0200, Uros Bizjak wrote: >> On Fri, Aug 30, 2019 at 9:22 AM Richard Biener >> wrote: >> > >> > On Thu, Aug 29, 2019 at 9:54 AM Uros Bizjak >wrote: >> > > >> > > On Wed, Aug 28, 2019 at 5:12 PM Uros

[PATCH] Fix up go regressions caused by my recent switchconv changes (PR go/91617)

2019-08-31 Thread Jakub Jelinek
Hi! Apparently my recent tree-{cfg,switch-conversion}.c changes broke a bunch of go tests. The problem is that range_check_type actually doesn't guarantee an unsigned type; it forces integer type for enum/bool (that was what was really needed to fix the PR), and for integer types that don't wrap

Re: [PATCH] Fix free_lang_data on asm stmts (PR lto/91572)

2019-08-31 Thread Richard Biener
On August 31, 2019 8:30:03 AM GMT+02:00, Jakub Jelinek wrote: >Hi! > >The following testcase ICEs, because on the inline asm LTO streaming >streams >the constraint strings ("g" in this case), including their type, but >the >fld type discovery doesn't see that type and so we end up streaming

Re: [PATCH, V3, #4 of 10], Add general prefixed/pcrel support

2019-08-31 Thread Segher Boessenkool
On Sat, Aug 31, 2019 at 10:36:00AM +0930, Alan Modra wrote: > On Fri, Aug 30, 2019 at 11:35:11AM -0500, Segher Boessenkool wrote: > > > - unsigned HOST_WIDE_INT val = INTVAL (XEXP (addr, 1)); > > > - return val + 0x8000 >= 0x1 - (TARGET_POWERPC64 ? 8 : 12); > > > + HOST_WIDE_INT val =

Re: [PATCH 2/2] gcc/riscv: Add a mechanism to remove some calls to _riscv_save_0

2019-08-31 Thread Andreas Schwab
On Aug 30 2019, Jim Wilson wrote: > underlying problem is that the save/restore functions were always > called as non-pic, even for a shared library. But fixing that > produced shared libraries that failed again, which turned out because > the save/restore functions use the alternate link

Re: [PATCH 2/2] gcc/riscv: Add a mechanism to remove some calls to _riscv_save_0

2019-08-31 Thread Andreas Schwab
On Aug 30 2019, Jim Wilson wrote: > produced shared libraries that failed again, which turned out because > the save/restore functions use the alternate link register t0/x5 which > is clobbered by plts, so we can't call them in shared libraries at > all. Shouldn't the save/restore functions

[PATCH] [AARCH64] Add support for new control bits CTR_EL0.DIC and CTR_EL0.IDC

2019-08-31 Thread Shaokun Zhang
The DCache clean & ICache invalidation requirements for instructions to be data coherence are discoverable through new fields in CTR_EL0. Let's support the two bits if they are enabled, the CPU core will not execute the unnecessary DCache clean or Icache Invalidation instructions. 2019-08-31

[PATCH] Fix free_lang_data on asm stmts (PR lto/91572)

2019-08-31 Thread Jakub Jelinek
Hi! The following testcase ICEs, because on the inline asm LTO streaming streams the constraint strings ("g" in this case), including their type, but the fld type discovery doesn't see that type and so we end up streaming const char type turned into its own main variant. The strings for asm are