[PATCH 2/4] rs6000: Rename 74 -> CR6_REGNO

2016-09-01 Segher Boessenkool * config/rs6000/altivec.md: Use CR6_REGNO instead of 74 throughout. * config/rs6000/vector.md: Ditto. * config/rs6000/vsx.md: Ditto. --- gcc/config/rs6000/altivec.md | 30 +++---

[PATCH 4/4] rs6000: Rename 110 -> VSCR_REGNO

2016-09-01 Segher Boessenkool * config/rs6000/altivec.md: Use VSCR_REGNO instead of 110 throughout. --- gcc/config/rs6000/altivec.md | 37 +++-- 1 file changed, 19 insertions(+), 18 deletions(-) diff --git

[PATCH 3/4] rs6000: Rename 109 -> VRSAVE_REGNO

2016-09-01 Segher Boessenkool * config/rs6000/altivec.md: Use VRSAVE_REGNO instead of 109 throughout. --- gcc/config/rs6000/altivec.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/config/rs6000/altivec.md

[PATCH 1/4] Hack: non-symbolic numeric constant warning

This patch prints a warning if a register number in the machine description patterns is non-symbolic, to catch places that should use a constant from a define_constants instead (e.g., LR_REGNO). I hardcoded this to not warn for regno < 32, i.e. the GPRs on PowerPC. That of course is not

Re: [patch, libgfortran] PR77393 [7 Regression] Revision r237735 changed the behavior of F0.0

.0)") -huge(1.0_10) >> if (len(trim(str)).lt.4935) error stop "FAILED AT 9" >> write(str, "(f0.10)") -huge(1.0_16) >> if (len(trim(str)).lt.4945) error stop "FAILED AT 11" >> end program testbigf0 > > FAIL: gfortran.dg/fmt_f0_2.

[PATCH, fortran testsuite]: Correct the calls to c functions in gfortran.dg/c_by_val_1.f

Hello! Functions c_to_c__ and c_to_c8__ in the supplemental testcase c file are prototyped as: extern void c_to_c__ (complex float*, complex float, complex float*, complex float**); extern void c_to_c8__ (complex double*, complex double, complex double*, complex double**); so, we have to call

Re: [PATCH, docs] invoke.texi: random copy-editing

On Wed, 29 Aug 2012, Sandra Loosemore wrote: > * doc/invoke.texi: Fix numerous typos and punctuation/grammatical > errors throughout the file. Re-word some awkward sentences and > paragraphs. I noticed you changed return-value and return-type to their variants without a dash.

Re: stray warning from gcc's cpp

Hi David, I found this older report (including patches for two approaches even!) that it seems did not see any response despite the nice analysis (and the patch). Mind having a look? Gerald PS: If you prefer, I can put this into Bugzilla, too. On Fri, 28 Mar 2014, Andriy Gapon wrote: > on

Re: [PATCH][msp430] Don't output __interrupt_vector sections for weak functions

On 29/08/2016 22:09, DJ Delorie wrote: > > Which results in a more user-obvious case, ignoring the interrupt > attribute or ignoring the weak attribute? I would think that we never > want to compile and link successfully if we can't do what the user > wants, and omitting an interrupt handler

Re: PR35503 - warn for restrict pointer

The attached version passes bootstrap+test on ppc64le-linux-gnu. Given that it only looks if parameters are restrict qualified and not how they're used inside the callee, this can have false positives as in above test-cases. Should the warning be put in Wextra rather than Wall (I have left it in

Re: Implement -Wimplicit-fallthrough (version 8)

On Thu, 1 Sep 2016, Marek Polacek wrote: > Yet another version. Changes from version 7: > > * no more fix-it hints untils we resolve some of the issues this patch > has discovered; instead, I simply used an inform call, > * I've fixed a bogus -Wdeclaration-after-statement warning in the C FE,

Re: [PATCH, testsuite]: Use dg-add-options ieee in some _FloatN tests

On Thu, 1 Sep 2016, Uros Bizjak wrote: > Hello! > > Attached patch adds dg-add-options ieee in _FloatN tests where > advanced IEEE features are used (e.g. NaN, infinity, subnormals). > > 2016-09-01 Uros Bizjak > > * gcc.dg/torture/float128-builtin.c,

Re: Implement C _FloatN, _FloatNx types [version 6]

On Thu, 1 Sep 2016, Szabolcs Nagy wrote: > it seems that the FLT_EVAL_METHOD change in TS 18661 was a > bad decision: existing code have to be modified to conform > to the new semantics. this situation could have been avoided > by introducing new macros or only changing behaviour when > the user

Re: [patch, libstdc++] std::shuffle: Generate two swap positions at a time if possible

On 01/09/16 17:31 +0200, Eelis van der Weegen wrote: On 2016-09-01 17:14, Jonathan Wakely wrote: On 31/08/16 13:45 +0100, Jonathan Wakely wrote: On 03/05/16 16:42 +0200, Eelis van der Weegen wrote: Ah, thanks, I forgot to re-attach when I sent to include the libstdc++ list. On 2016-05-03

Re: [patch, libstdc++] std::shuffle: Generate two swap positions at a time if possible

On 01/09/16 17:27 +0200, Marc Glisse wrote: On Thu, 1 Sep 2016, Jonathan Wakely wrote: + const __uc_type __comp_range = __swap_range * (__swap_range + 1); If __swap_range is 3, then __comp_range is 10 and ??? Bah :-) Thanks. I guess I read the code correctly the other day at

Re: [patch, libstdc++] std::shuffle: Generate two swap positions at a time if possible

On 2016-09-01 17:14, Jonathan Wakely wrote: On 31/08/16 13:45 +0100, Jonathan Wakely wrote: On 03/05/16 16:42 +0200, Eelis van der Weegen wrote: Ah, thanks, I forgot to re-attach when I sent to include the libstdc++ list. On 2016-05-03 14:38, Jonathan Wakely wrote: ENOPATCH On 1 May 2016 at

Re: [patch, libstdc++] std::shuffle: Generate two swap positions at a time if possible

On Thu, 1 Sep 2016, Jonathan Wakely wrote: + const __uc_type __comp_range = __swap_range * (__swap_range + 1); If __swap_range is 3, then __comp_range is 10 and ??? -- Marc Glisse

Re: [PATCH 2/3] rs6000: Use LR_REGNO instead of constant 65

On Thu, Sep 01, 2016 at 09:50:09AM +0100, Iain Sandoe wrote: > > I left it in *restore_world because Iain will remove it there soon. > > Here is the patch to fix up Darwin, > I guess it’s both Darwin-local and reasonably obvious now, but OK? Yes, okay for trunk, thanks! Segher > 2016-09-01

Re: [patch, libstdc++] std::shuffle: Generate two swap positions at a time if possible

On 31/08/16 13:45 +0100, Jonathan Wakely wrote: On 03/05/16 16:42 +0200, Eelis van der Weegen wrote: Ah, thanks, I forgot to re-attach when I sent to include the libstdc++ list. On 2016-05-03 14:38, Jonathan Wakely wrote: ENOPATCH On 1 May 2016 at 15:21, Eelis wrote:

Re: Implement -Wimplicit-fallthrough (version 8): add gcc_fallthrough()

On Thu, Sep 01, 2016 at 04:51:37PM +0200, Marek Polacek wrote: > I thought I'd keep it since it conveys something more than a pure "falls > through" comments, but I changed it anyway. Here's the pure comment > changes patch which I hope can be committed right away. > > 2016-09-01 Marek Polacek

Re: Implement -Wimplicit-fallthrough (version 8): add gcc_fallthrough()

On Thu, Sep 01, 2016 at 04:27:01PM +0200, Jakub Jelinek wrote: > On Thu, Sep 01, 2016 at 03:42:12PM +0200, Marek Polacek wrote: > > --- gcc/gcc/c-family/c-common.c > > +++ gcc/gcc/c-family/c-common.c > > @@ -11590,6 +11590,7 @@ resolve_overloaded_builtin (location_t loc, tree > > function, > >

Re: [PATCH v2, rs6000] Fix PR72827 (ada bootstrap failure)

On Sep 1, 2016, at 9:32 AM, Segher Boessenkool wrote: > > On Wed, Aug 31, 2016 at 09:15:32PM -0500, Bill Schmidt wrote: >> This patch (suggested by Michael Meissner) instead prevents the problem >> by disallowing reg+reg addressing for TImode, allowing D-form

Re: [PATCH v2, rs6000] Fix PR72827 (ada bootstrap failure)

On Wed, Aug 31, 2016 at 09:15:32PM -0500, Bill Schmidt wrote: > This patch (suggested by Michael Meissner) instead prevents the problem > by disallowing reg+reg addressing for TImode, allowing D-form addressing > to be used for the separate stores of the GPRs. This is not an ideal > permanent

Re: Implement -Wimplicit-fallthrough (version 8): add gcc_fallthrough()

On Thu, Sep 01, 2016 at 03:42:12PM +0200, Marek Polacek wrote: > --- gcc/gcc/c-family/c-common.c > +++ gcc/gcc/c-family/c-common.c > @@ -11590,6 +11590,7 @@ resolve_overloaded_builtin (location_t loc, tree > function, > gcc_unreachable (); > } > /* Fallthrough to the normal

Ping Re: Make max_align_t respect _Float128

Ping. This patch is pending review (with either __i386__ or __SIZEOF_FLOAT128__, although __i386__ is safest in that it minimizes the cases where there is any ABI change at all even in the size of the type). -- Joseph S. Myers

Implement -Wimplicit-fallthrough (version 8): add gcc_fallthrough()

Tobias pointed out that I need to add a new gcc_fallthrough into trans-io.c, so done. Bootstrapped/regtested on x86_64-linux and ppc64-linux. 2016-08-31 Marek Polacek PR c/7652 * Makefile.in (insn-attrtab.o-warn, insn-dfatab.o-warn,

Implement -Wimplicit-fallthrough (version 8)

Yet another version. Changes from version 7: * no more fix-it hints untils we resolve some of the issues this patch has discovered; instead, I simply used an inform call, * I've fixed a bogus -Wdeclaration-after-statement warning in the C FE, new test added, * I've addressed Jason's comments

Re: [PATCH][AArch64 - v2] Simplify eh_return implementation

On 10/08/16 17:26, Wilco Dijkstra wrote: > I noticed it would still be a good idea to add an extra barrier in the epilog > as the > scheduler doesn't appear to handle aliases of frame accesses properly. > > This patch simplifies the handling of the EH return value. We force the use > of the

Re: [patch] Fix segfault in param_change_prob

On Thu, Sep 1, 2016 at 3:17 PM, Eric Botcazou wrote: >> So I think it's better to apply get_base_address here rather than only >> stripping VIEW_CONVERT_EXRPs. >> (beware of it returning NULL_TREE for WITH_SIZE_EXPRs, thus maybe >> strip those first as well) > > Something

[PATCH] Fix PR77436

The following fixes the wide-int conversion of tree_fold_binomial. Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. Richard. 2016-09-01 Richard Biener PR middle-end/77436 * tree-chrec.c (tree_fold_binomial): Use widest_int, properly

Re: [patch] Fix segfault in param_change_prob

> So I think it's better to apply get_base_address here rather than only > stripping VIEW_CONVERT_EXRPs. > (beware of it returning NULL_TREE for WITH_SIZE_EXPRs, thus maybe > strip those first as well) Something like this? The testsuite is still clean with it. * ipa-inline-analysis.c

[arm-embedded] [PATCH, ARM 7/7] Enable atomics for ARMv8-M Mainline

Hi, We've decided to apply the following patch to ARM/embedded-6-branch. Best regards, Thomas Forwarded Message Subject: Re: [PATCH, ARM 7/7] Enable atomics for ARMv8-M Mainline Date: Thu, 14 Jul 2016 17:34:44 +0100 From: Thomas Preudhomme

Re: [PATCH][AArch64 - v2] Simplify eh_return implementation

Ping I noticed it would still be a good idea to add an extra barrier in the epilog as the scheduler doesn't appear to handle aliases of frame accesses properly. This patch simplifies the handling of the EH return value.  We force the use of the frame pointer so the return location is always

Re: [PATCH, PR70955] Tag {ms,sysv}_va_list_type_node with {ms,sysv}_abi attribute

On 2016.08.26 at 17:33 +0200, Tom de Vries wrote: > On 26/08/16 10:40, Richard Biener wrote: > >I suppose > >you could get away with using sth entirely private to the backend, > >like "sysv abi valist", also not ever user-creatable. Does this > >side-step the FE issue? > > It does. > > Added

Re: [PATCH, docs] invoke.texi: random copy-editing

Hi Sandra, On Wed, 29 Aug 2012, Sandra Loosemore wrote: > I've had this largish pile of random copy-edits to invoke.texi left over > from my previous passes through that file earlier this year. that was an amazing amount of changes; I admire your patience and thoroughness! > I'll wait a few

[PTX] cbranch expanders

I noticed the conditional branch expanders unnecessarily forced alll ops to be registers. Of course later optimization fixes that up, but why create the problem in the first place? committed to trunk. nathan

[committed] Backports to 6.x branch

Hi! I've committed following backports of some trunk fixes, after bootstrapping/regtesting them on x86_64-linux and i686-linux. Jakub 2016-09-01 Jakub Jelinek Backported from mainline 2016-08-16 Jakub Jelinek PR

Re: [patch] Fix segfault in param_change_prob

On Wed, Aug 31, 2016 at 8:46 PM, Eric Botcazou wrote: > Hi, > > the attached Ada testcase triggers a segfault in param_change_prob because the > parameter is VIEW_CONVERT_EXPR (or it fools the logic and walk_aliased_vdefs is called on a NULL

[Patch, testsuite] Fix more bogus failures for avr

Hi, The below patch fixes some bogus testsuite failures for the avr target. The first three expect 32 bit ints, and the last one uses too much RAM for a typical avr device. Regtested with avr and x86_64-pc-linux, and committed to trunk. Regards Senthil gcc/testsuite/ChangeLog

Re: Implement C _FloatN, _FloatNx types [version 6]

On 31/08/16 18:26, Joseph Myers wrote: > On Wed, 31 Aug 2016, James Greenhalgh wrote: > >> My concern with this is that the use of comparisons of FLT_EVAL_METHOD >> against 0 that Szabolcs is referring to is common and can have performance >> implications. In glibc for example, >> >> static

Re: [patch, libgfortran] PR77393 [7 Regression] Revision r237735 changed the behavior of F0.0

write(str, "(f0.10)") -huge(1.0_16) > if (len(trim(str)).lt.4945) error stop "FAILED AT 11" > end program testbigf0 FAIL: gfortran.dg/fmt_f0_2.f90 -O0 (test for excess errors) Excess errors: /daten/aranym/gcc/gcc-20160901/gcc/testsuite/gfortran.dg/fmt_f0_2.f90:12:

Re: PR35503 - warn for restrict pointer

On 1 September 2016 at 12:25, Richard Biener wrote: > On Tue, 30 Aug 2016, Tom de Vries wrote: > >> On 30/08/16 17:34, Prathamesh Kulkarni wrote: >> > On 30 August 2016 at 20:24, Tom de Vries wrote: >> > > On 26/08/16 13:39, Prathamesh Kulkarni wrote:

Re: [doc, SPU] Remove references to sites no longer carrying SPU information from doc/extend.texi

On Sat, 27 Aug 2016, Gerald Pfeifer wrote: > 2016-08-27 Gerald Pfeifer > > * doc/extend.texi (SPU Built-in Functions): Remove stale > references to material formerly at IBM and Sony. Now also pushed back to the GCC 6 branch. Gerald

Re: [ARM] Fix broken sibcall with longcall, APCS frame and VFP

On 01/09/16 10:03, Richard Earnshaw (lists) wrote: > On 01/09/16 08:47, Eric Botcazou wrote: >>> Since you're going to need a back-port there should be a PR filed for this. >> >> PR target/77439 >> >>> Have you checked that this works with multi-lib dejagnu runs and on >>> hard-float systems? I

Re: [ARM] Fix broken sibcall with longcall, APCS frame and VFP

On 01/09/16 08:47, Eric Botcazou wrote: >> Since you're going to need a back-port there should be a PR filed for this. > > PR target/77439 > >> Have you checked that this works with multi-lib dejagnu runs and on >> hard-float systems? I doubt this will work in armhf-linux, for example. > > No,

Re: [PATCH] Improvements to typed_splay_tree (v2)

On 09/01/2016 03:01 AM, David Malcolm wrote: On Wed, 2016-08-31 at 16:12 +0200, Bernd Schmidt wrote: Looks ok otherwise. Thanks. Here's a revised version; I moved the "struct closure" into the class itself. Successfully bootstrapped on x86_64-pc-linux-gnu. OK for trunk? Sure. Bernd

Re: [PATCH][AArch64] Add ANDS pattern for CMP+ZERO_EXTEND

On 01/09/16 09:50, Kyrill Tkachov wrote: > Hi all, > > For the testcase in this patch combine tries to match: > (parallel [ > (set (reg:CC 66 cc) > (compare:CC (zero_extend:SI (reg:QI 0 x0 [ x ])) > (const_int 0 [0]))) > (set (reg/v:SI 77 [ x ]) >

[PATCH][AArch64] Add ANDS pattern for CMP+ZERO_EXTEND

Hi all, For the testcase in this patch combine tries to match: (parallel [ (set (reg:CC 66 cc) (compare:CC (zero_extend:SI (reg:QI 0 x0 [ x ])) (const_int 0 [0]))) (set (reg/v:SI 77 [ x ]) (zero_extend:SI (reg:QI 0 x0 [ x ]))) ]) which

Re: [PATCH 2/3] rs6000: Use LR_REGNO instead of constant 65

Hi, > On 1 Sep 2016, at 01:49, Segher Boessenkool > wrote: > I left it in *restore_world because Iain will remove it there soon. Here is the patch to fix up Darwin, I guess it’s both Darwin-local and reasonably obvious now, but OK? Iain [PATCH] rs6000,Darwin:

Re: [PATCH] Fix up -fsanitize=address ctor order (PR sanitizer/77396)

On Thu, Sep 01, 2016 at 09:58:44AM +0200, Richard Biener wrote: > > and thus if no globals have been registered, dynamic_init_globals is NULL, > > and without the assertion it would crash on dynamic_init_globals->size(). > > The fix would be just to do: > >if

Re: [PATCH][Aarch64][gcc] Fix vld2/3/4 on big endian systems

On 30 August 2016 at 18:45, Tamar Christina wrote: > > > On 30/08/16 17:11, Christophe Lyon wrote: >> >> On 18 August 2016 at 11:15, Tamar Christina >> wrote: >>> >>> Hi all, >>> >>> This fixes a bug in the vector load functions in which they

[PATCH, testsuite]: Use dg-add-options ieee in some _FloatN tests

Hello! Attached patch adds dg-add-options ieee in _FloatN tests where advanced IEEE features are used (e.g. NaN, infinity, subnormals). 2016-09-01 Uros Bizjak * gcc.dg/torture/float128-builtin.c, gcc.dg/torture/float128-floath.c, gcc.dg/torture/float128-ieee-nan.c,

Re: [PATCH] Fix up -fsanitize=address ctor order (PR sanitizer/77396)

On Thu, 1 Sep 2016, Jakub Jelinek wrote: > On Thu, Sep 01, 2016 at 09:39:37AM +0200, Richard Biener wrote: > > > On Thu, Sep 01, 2016 at 08:59:57AM +0200, Richard Biener wrote: > > > > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? > > > > > > > > Hmm, maybe simply do > >

Re: [PATCH] Fix up -fsanitize=address ctor order (PR sanitizer/77396)

On Thu, Sep 01, 2016 at 09:39:37AM +0200, Richard Biener wrote: > > On Thu, Sep 01, 2016 at 08:59:57AM +0200, Richard Biener wrote: > > > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? > > > > > > Hmm, maybe simply do > > > > > > if (gimple_call_builtin_p (g,

Re: [ARM] Fix broken sibcall with longcall, APCS frame and VFP

> Since you're going to need a back-port there should be a PR filed for this. PR target/77439 > Have you checked that this works with multi-lib dejagnu runs and on > hard-float systems? I doubt this will work in armhf-linux, for example. No, I guess some dg-skip-if would be in order, but I'm

Re: [PATCH] Fix up -fsanitize=address ctor order (PR sanitizer/77396)

On Thu, 1 Sep 2016, Jakub Jelinek wrote: > On Thu, Sep 01, 2016 at 08:59:57AM +0200, Richard Biener wrote: > > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? > > > > Hmm, maybe simply do > > > > if (gimple_call_builtin_p (g, BUILT_IN_ASAN_AFTER_DYNAMIC_INIT)) > > {

Re: [PATCH] Fix up -fsanitize=address ctor order (PR sanitizer/77396)

On Thu, Sep 01, 2016 at 08:59:57AM +0200, Richard Biener wrote: > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? > > Hmm, maybe simply do > > if (gimple_call_builtin_p (g, BUILT_IN_ASAN_AFTER_DYNAMIC_INIT)) > { > gimple *def = SSA_NAME_DEF_STMT (gimple_vuse

Re: [committed] C: Fix missing spaces in 'struct' fix-it hints

On Sep 01 2016, David Malcolm wrote: > diff --git a/gcc/c/c-parser.c b/gcc/c/c-parser.c > index a6281fc..531d94e 100644 > --- a/gcc/c/c-parser.c > +++ b/gcc/c/c-parser.c > @@ -1685,7 +1685,7 @@ c_parser_declaration_or_fndef (c_parser *parser, bool > fndef_ok, >if

Re: [PATCH v2, rs6000] Fix PR72827 (ada bootstrap failure)

> This patch (suggested by Michael Meissner) instead prevents the problem > by disallowing reg+reg addressing for TImode, allowing D-form addressing > to be used for the separate stores of the GPRs. This is not an ideal > permanent solution, because it disallows reg+reg addressing not only for >

Re: [patch] Fix PR fortran/72743

On Wed, 31 Aug 2016, Chung-Lin Tang wrote: > Hi Richard, Martin, > this issue is actually sort of like PR 70856, basically the same ICE > after IPA-ICF, due to DECL_PT_UIDs not consistent after reaching for the > ultimate_alias_target(). > > The reason this wasn't covered by the PR70856 fix is

Re: [PATCH] Fix up -fsanitize=address ctor order (PR sanitizer/77396)

On Wed, 31 Aug 2016, Jakub Jelinek wrote: > Hi! > > libasan currently has an assertion that __asan_before_dynamic_init > is called only after registering at least one global var. I have no idea > how to always guarantee that without making the code too ugly or registering > dummy global vars,

Re: PR35503 - warn for restrict pointer

On Tue, 30 Aug 2016, Tom de Vries wrote: > On 30/08/16 17:34, Prathamesh Kulkarni wrote: > > On 30 August 2016 at 20:24, Tom de Vries wrote: > > > On 26/08/16 13:39, Prathamesh Kulkarni wrote: > > > > > > > > Hi, > > > > The following patch adds option -Wrestrict that