RE: [PATCH] Fix PR tree-optimization/77654

> From: Richard Biener [rguent...@suse.de] > Sent: Thursday, September 22, 2016 12:43 AM > To: Doug Gilmore > Cc: gcc-patches@gcc.gnu.org; rgue...@gcc.gnu.org > Subject: RE: [PATCH] Fix PR tree-optimization/77654 > > On Wed, 21 Sep 2016, Doug Gilmore wrote: > > ... > > Sorry I that missed point.

Re: gcc build problem (i386.c) -- missing declaration

Hi, > extern unsigned hook_uint_void_0 (void); > extern unsigned int hook_uint_mode_0 (machine_mode); > +extern bool hook_uint_uintp_false (unsigned int, unsigned int *); I'm seeing the same build issue on ppc64le, and your patch fixes it. Thanks. Anton

ICE at -O1 and above in both 32-bit and 64-bit modes on x86_64-linux-gnu

Hi, As Richard pointed out in PR77677, TREE_OVERFLOW is not cleared in IPA-VRP. There are three places in which we set value_range: 1. When value ranges are obtained from SSA_NAME with get_range_info with wide_int_to_tree. In this case we will not have TREE_OVERFLOW set. 2. When we

Re: [PATCH] Extend dg-{error,warning,message,bogus} line specification to allow relative line numbers

On Sep 22, 2016, at 1:05 PM, Jakub Jelinek wrote: > This is something I've been unhappy for a long time with :-) Me too. > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? Ok. Thanks.

Re: [PATCH] accept flexible arrays in struct in unions (c++/71912 - [6/7 regression])

On 09/21/2016 02:43 PM, Jason Merrill wrote: On Tue, Sep 20, 2016 at 1:01 PM, Martin Sebor wrote: On 09/16/2016 12:19 PM, Jason Merrill wrote: On 09/14/2016 01:03 PM, Martin Sebor wrote: + /* Type of the member. */ + tree fldtype = TREE_CODE (fld) == FIELD_DECL

[openacc] fix an ICE with acc declared VLAs

There's a bug with ACC DECLARE clauses involving VLA variables that causes lower_omp_target to thow an ICE on VLA decls. The problem occurred because those clauses are never gimplified. This patch resolves that ICE by teaching gimplify_oacc_declare how to gimplify them. It turns out that

gcc build problem (i386.c) -- missing declaration

As of revision 240383 , i386.c isn't compiling. The errors are: In file included from ../../gcc_trunk/gcc/target-def.h:106:0, from ../../gcc_trunk/gcc/config/i386/i386.c:81: ./target-hooks-def.h:92:38: error: ‘hook_uint_uintp_false’ was not declared in this scope

Re: [PATCHv2][ARM] -mpure-code option for ARM

On 09/22/2016 07:52 AM, Richard Earnshaw (lists) wrote: On 11/07/16 17:56, Andre Vieira (lists) wrote: + diff --git a/gcc/target.def b/gcc/target.def index a4df363698ce776b51d11c187baed2069ba88a52..a3d46fa48d919a16699c33b2b78236e62a33e025 100644 --- a/gcc/target.def +++ b/gcc/target.def @@

[PATCH] fixincludes: fix fixincludes for MinGW

The fixincl executable uses system function to call applyfix or to direcly patch a header file, with parameters enclosed in single quotes. This problem is that MinGW system function just calls cmd.exe, which doesn't strip quotes from parameters and completely ignores quotes for embedding spaces in

Re: [PATCH] builtin expansion of memcmp for powerpc

Hi Aaron, On Thu, Sep 22, 2016 at 03:10:24PM -0500, Aaron Sawdey wrote: > The powerpc target had a movmemsi pattern which supports memcpy() but > did not have anything for memcmp(). This adds support for builtin > expansion of memcmp() into inline code for modest constant lengths. > Performance

Re: [PATCH][RFC][regrename][sel-sched] Fix arm bootstrap

On 09/22/16 15:26, Kyrill Tkachov wrote: > Hi all, > > In the the interest of fixing arm bootstrap here are the two blocking > issues > and the changes proposed for them. > I'm not familiar enough with regrename or sel-sched to make a call on > whether > these are right or not, I just want to keep

Re: [PATCH][RFC][regrename][sel-sched] Fix arm bootstrap

On Thu, 22 Sep 2016, Kyrill Tkachov wrote: > In the the interest of fixing arm bootstrap here are the two blocking issues > and the changes proposed for them. > I'm not familiar enough with regrename or sel-sched to make a call on whether > these are right or not, I just want to keep the ball

Re: [PATCH][RFC][regrename][sel-sched] Fix arm bootstrap

On 22/09/16 15:27, Alexander Monakov wrote: On Thu, 22 Sep 2016, Kyrill Tkachov wrote: In the the interest of fixing arm bootstrap here are the two blocking issues and the changes proposed for them. I'm not familiar enough with regrename or sel-sched to make a call on whether these are right

[PATCH] Bits from Early LTO debug merge -- move stuff from late to early finish

This merges moving of unused type pruning from late to early finish as well as handling of debug types and dwarf2 dups elimination. It adds a flag to DIEs so we can mark them as removed in case sth after early finish tries to lookup a DIE for a removed DIE again - we shouldn't re-use the

Re: [PATCH][RFC][regrename][sel-sched] Fix arm bootstrap

On Thu, 22 Sep 2016, Kyrill Tkachov wrote: > Sorry no, the problem is HARD_FRAME_POINTER_REGNUM that is defined as: > #define HARD_FRAME_POINTER_REGNUM\ > (TARGET_ARM\ >? ARM_HARD_FRAME_POINTER_REGNUM\ >: THUMB_HARD_FRAME_POINTER_REGNUM) > > where

Re: PR35503 - warn for restrict pointer

On 20 September 2016 at 18:31, Joseph Myers wrote: > On Tue, 20 Sep 2016, Prathamesh Kulkarni wrote: > >> Could someone please take a look at the change to c-format.c, I am not sure >> if I have added that correctly. > > Any changes to these GCC formats also require tests

Re: [PATCH] Fix ICE with inlining and #pragma omp simd (PR fortran/77665)

On Wed, 21 Sep 2016, Alexander Monakov wrote: > On Wed, 21 Sep 2016, Jakub Jelinek wrote: > > The simduid pass uses the cfun->has_simduid_loops flag to determine if it > > needs to clean up any left-over GOMP_SIMD_* internal functions. > > During inlining, we set the flag if we inline some loop

Re: [Patch] Fix variant::operator= on references

On Thu, Sep 22, 2016 at 12:43 AM, Tim Shen wrote: > Hi, this patch fixes the following compilation failure: For the record, the bug is found by Ville. Thank you Ville! :) -- Regards, Tim Shen

Re: [PATCH] Fix various minor gimple-ssa-sprintf.c issues

On Thu, Sep 22, 2016 at 09:24:11AM +0200, Jakub Jelinek wrote: > On Wed, Sep 21, 2016 at 06:38:54PM -0600, Martin Sebor wrote: > > On 09/21/2016 09:09 AM, Jakub Jelinek wrote: > > >When looking at PR77676, I've noticed various small formatting etc. > > >issues, like not using is_gimple_* APIs

Re: [PATCH] libstdc++/77641 fix std::variant for literal types

This problem is not introduced by the latest patch, but it's something that we should look at anyway. There's been recent discussion about what assignments do with variants that hold references. Consider this: #include int main() { float f1 = 1.0f, f2 = 2.0f; std::variant v1(f1);

Re: [PATCH] Fix PR tree-optimization/77550

On Wed, 21 Sep 2016, Bernd Edlinger wrote: > On 09/21/16 21:57, Christophe Lyon wrote: > > Hi, > > > > The new testcase pr77550.C fails on arm: > > /testsuite/g++.dg/pr77550.C:39:43: error: 'operator new' takes type > > 'size_t' ('unsigned int') as first parameter [-fpermissive] > > compiler

[PATCH] [RTEMS] Always use atomic builtins for libstdc++

libstdc++-v3/ * config/cpu/m68k/atomicity.h: Adjust comment. * acinclude.m4 (GLIBCXX_ENABLE_ATOMIC_BUILTINS): Honor explicit atomicity_dir setup via configure.host. * configure.host (rtems-*): Set atomicity_dir. * configure: Regenerate. ---

Fortran, committed: ICE on missing parameter value for initialisation (segfault) (pr 66107)

Fixed in revision 240341.

Re: [Patch, avr] Provide correct LD offset bound in avr_address_cost

2016-09-22 7:52 GMT+03:00 Senthil Kumar Selvaraj : > Hi, > > This patch fixes cost computation in avr_address_cost - instead of the > hardcoded 61, it uses the already existing MAX_LD_OFFSET(mode) macro. > > This showed up when investigating a code size

[Patch] Fix variant::operator= on references

Hi, this patch fixes the following compilation failure: #include int main() { float f1 = 1.0f, f2 = 2.0f; std::variant v1(f1); v1 = f2; // #1 } The bug is caused by a misuse of __storage. I also examined other __storage usage, they all seem appropriate. Tested on

Re: [PATCH] Fix various minor gimple-ssa-sprintf.c issues

On Wed, Sep 21, 2016 at 06:38:54PM -0600, Martin Sebor wrote: > On 09/21/2016 09:09 AM, Jakub Jelinek wrote: > >When looking at PR77676, I've noticed various small formatting etc. > >issues, like not using is_gimple_* APIs where we have them, not using > >gimple_call_builtin_p/gimple_call_fndecl

RE: [PATCH] Fix PR tree-optimization/77654

On Wed, 21 Sep 2016, Doug Gilmore wrote: > > From: Richard Biener [rguent...@suse.de] > > Sent: Wednesday, September 21, 2016 12:48 AM > > To: Doug Gilmore > > Cc: gcc-patches@gcc.gnu.org; rgue...@gcc.gnu.org > > Subject: RE: [PATCH] Fix PR tree-optimization/77654 > > > > On Tue, 20 Sep 2016,

Re: [Patch, fortran] Clean up of error recovery in DTIO procedures

Committed as revision 240342. Paul On 21 September 2016 at 12:18, Paul Richard Thomas wrote: > Dear All, > > Please find attached a patch to clean up the various issues with > errors in DTIO procedures. The tests were all provided by Gerhard > Steinmetz for which

Re: [PATCH] libstdc++/77641 fix std::variant for literal types

On 22/09/16 09:45 +0300, Ville Voutilainen wrote: This problem is not introduced by the latest patch, but it's something that we should look at anyway. There's been recent discussion about what assignments do with variants that hold references. Consider this: #include int main() { float f1

Re: [PATCH] libstdc++/77641 fix std::variant for literal types

On 22/09/16 09:37 +0100, Jonathan Wakely wrote: On 22/09/16 09:45 +0300, Ville Voutilainen wrote: This problem is not introduced by the latest patch, but it's something that we should look at anyway. There's been recent discussion about what assignments do with variants that hold references.

Re: [RFC] Extend ipa-bitwise-cp with pointer alignment propagation

On Wed, Sep 21, 2016 at 6:44 PM, Prathamesh Kulkarni wrote: > Hi, > The attached patch tries to extend ipa bits propagation to handle > pointer alignment propagation. > The patch just disables ipa-cp-alignment pass, I suppose we want to > eventually remove it ? > >

Re: [Patch] Fix variant::operator= on references

On 22/09/16 01:49 -0700, Tim Shen wrote: Done. When writing the initial version, I was trying to save as much qualifications as possible (as long as the semantic doesn't change) for readability, but that might not be a good idea. It does change the semantics, as forward<_Tp>(__tp) can find

Re: [Patch] Fix variant::operator= on references

On 22/09/16 00:43 -0700, Tim Shen wrote: Hi, this patch fixes the following compilation failure: #include int main() { float f1 = 1.0f, f2 = 2.0f; std::variant v1(f1); v1 = f2; // #1 } The bug is caused by a misuse of __storage. I also examined other __storage usage, they all

Re: [PATCH] [RTEMS] Always use atomic builtins for libstdc++

On 22/09/16 09:41 +0200, Sebastian Huber wrote: libstdc++-v3/ * config/cpu/m68k/atomicity.h: Adjust comment. * acinclude.m4 (GLIBCXX_ENABLE_ATOMIC_BUILTINS): Honor explicit atomicity_dir setup via configure.host. * configure.host (rtems-*): Set atomicity_dir.

Re: [v3 PATCH] PR libstdc++/77288 and the newest proposed resolution for LWG 2756

Hi, On 21 September 2016 at 21:42, Ville Voutilainen wrote: > On 21 September 2016 at 12:31, Jonathan Wakely wrote: >> On 06/09/16 09:00 +0300, Ville Voutilainen wrote: >>> >>>PR libstdc++/77288 >>>* include/std/optional

Re: [gofrontend-dev] Go patch committed: Avoid warning by using a local var for std::ofstream

On Wed, 2016-09-21 at 16:56 +0200, Florian Weimer wrote: > Torvald, would it be possible to align mutexes internally on hppa, to > avoid the 16-byte alignment of the entire struct (that is, store a > pointer to the actual mutex object, which points to a sub-region of > the struct which is suitably

Re: [v3 PATCH] PR libstdc++/77288 and the newest proposed resolution for LWG 2756

On 22 September 2016 at 11:05, Ville Voutilainen wrote: > On 22 September 2016 at 11:55, Christophe Lyon > wrote: >> The new test 77288.cc fails on old arm targets (armv5t): >>

Re: [PATCH GCC][v2]Simplify alias check code generation in vectorizer

On Wed, Sep 21, 2016 at 3:01 PM, Richard Biener wrote: > On Tue, Sep 20, 2016 at 5:25 PM, Bin Cheng wrote: >> Hi, >> I originally posted a patch improving code generation for alias check in >> vectorizer at

Re: [PATCH] [RTEMS] Always use atomic builtins for libstdc++

On 22/09/16 10:49 +0200, Sebastian Huber wrote: On 22/09/16 10:47, Jonathan Wakely wrote: On 22/09/16 09:41 +0200, Sebastian Huber wrote: libstdc++-v3/ * config/cpu/m68k/atomicity.h: Adjust comment. * acinclude.m4 (GLIBCXX_ENABLE_ATOMIC_BUILTINS): Honor explicit atomicity_dir setup

Re: [Patch] Fix variant::operator= on references

On Thu, Sep 22, 2016 at 3:36 AM, Tim Shen wrote: > Then my question is, what about type traits uses like > is_copy_constructible? I have seen non-qualified uses in std::any and > std::optional and other places. Should all of them be qualified? Ah never mind, I realized that

Re: [PATCH] [RTEMS] Always use atomic builtins for libstdc++

On 22/09/16 11:28 +0100, Jonathan Wakely wrote: On 22/09/16 10:49 +0200, Sebastian Huber wrote: On 22/09/16 10:47, Jonathan Wakely wrote: On 22/09/16 09:41 +0200, Sebastian Huber wrote: libstdc++-v3/ * config/cpu/m68k/atomicity.h: Adjust comment. * acinclude.m4

Re: [PATCH] [RTEMS] Always use atomic builtins for libstdc++

On Sep 22 2016, Sebastian Huber wrote: > diff --git a/libstdc++-v3/acinclude.m4 b/libstdc++-v3/acinclude.m4 > index 6d897be..3256ce4 100644 > --- a/libstdc++-v3/acinclude.m4 > +++ b/libstdc++-v3/acinclude.m4 > @@ -3490,9 +3490,10 @@ EOF >AC_LANG_RESTORE >

Re: [PATCH] [RTEMS] Always use atomic builtins for libstdc++

On 22/09/16 10:47, Jonathan Wakely wrote: On 22/09/16 09:41 +0200, Sebastian Huber wrote: libstdc++-v3/ * config/cpu/m68k/atomicity.h: Adjust comment. * acinclude.m4 (GLIBCXX_ENABLE_ATOMIC_BUILTINS): Honor explicit atomicity_dir setup via configure.host. * configure.host

Re: [Patch] Fix variant::operator= on references

On Thu, Sep 22, 2016 at 1:39 AM, Jonathan Wakely wrote: > Please qualify std::forward here. Done. When writing the initial version, I was trying to save as much qualifications as possible (as long as the semantic doesn't change) for readability, but that might not be a good

[PATCH v2] [RTEMS] Always use atomic builtins for libstdc++

v2: Fix shell script part since shell grouping is expressed by { }. libstdc++-v3/ * config/cpu/m68k/atomicity.h: Adjust comment. * acinclude.m4 (GLIBCXX_ENABLE_ATOMIC_BUILTINS): Honor explicit atomicity_dir setup via configure.host. * configure.host (rtems-*): Set

Re: [C++ PATCH] Aligned new option handling fixes (PR c++/77651)

Hi, On 21 September 2016 at 17:03, Jason Merrill wrote: > OK. > > On Wed, Sep 21, 2016 at 10:46 AM, Jakub Jelinek wrote: >> Hi! >> >> The following patch fixes some ICEs which were because of missing >> RejectNegative for the *aligned-new= options - they

Re: [v3 PATCH] PR libstdc++/77288 and the newest proposed resolution for LWG 2756

On 22 September 2016 at 11:55, Christophe Lyon wrote: > The new test 77288.cc fails on old arm targets (armv5t): > /aci-gcc-fsf/sources/gcc-fsf/gccsrc/libstdc++-v3/testsuite/20_util/optional/77288.cc: > In function 'void test01()': >

Re: [RFC] Extend ipa-bitwise-cp with pointer alignment propagation

On Thu, Sep 22, 2016 at 11:21 AM, Richard Biener wrote: > On Wed, Sep 21, 2016 at 6:44 PM, Prathamesh Kulkarni > wrote: >> Hi, >> The attached patch tries to extend ipa bits propagation to handle >> pointer alignment propagation. >> The

Re: [v3 PATCH] PR libstdc++/77288 and the newest proposed resolution for LWG 2756

On 22 September 2016 at 12:37, Christophe Lyon wrote: >> Does the attached patch fix the problem? > > Yes, thanks! Here be the changelog. Jonathan, ok for trunk? Patch attached again for convenience. 2016-09-22 Ville Voutilainen

Re: [Patch] Fix variant::operator= on references

On 22 September 2016 at 13:03, Jonathan Wakely wrote: > On 22/09/16 01:49 -0700, Tim Shen wrote: >> >> Done. When writing the initial version, I was trying to save as much >> qualifications as possible (as long as the semantic doesn't change) >> for readability, but that might

Re: [PATCH] libstdc++/77641 fix std::variant for literal types

On 21/09/16 20:23 -0700, Tim Shen wrote: On Wed, Sep 21, 2016 at 1:52 AM, Jonathan Wakely wrote: THanks, OK for trunk. Committed. This fixes the pretty printer. Committed to trunk. commit 6b869af56fa80da5b746390ce5616ebebcc0bd5d Author: redi

Re: [Patch] Fix variant::operator= on references

On Thu, Sep 22, 2016 at 3:03 AM, Jonathan Wakely wrote: > On 22/09/16 01:49 -0700, Tim Shen wrote: >> >> Done. When writing the initial version, I was trying to save as much >> qualifications as possible (as long as the semantic doesn't change) >> for readability, but that

Re: [PATCH] [RTEMS] Always use atomic builtins for libstdc++

On 22/09/16 09:47 +0100, Jonathan Wakely wrote: On 22/09/16 09:41 +0200, Sebastian Huber wrote: libstdc++-v3/ * config/cpu/m68k/atomicity.h: Adjust comment. * acinclude.m4 (GLIBCXX_ENABLE_ATOMIC_BUILTINS): Honor explicit atomicity_dir setup via configure.host. *

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

Hi Martin, >> Another nit, if I may: FWIW I'm not in love with the wording of the >> messages. Sorry to bikeshed, but how about: >> warning: buffer overflow will occur when writing terminating NUL >> and: >> note: formatted output of 2 bytes into a destination of size 1 >> or somesuch. > > I

Re: [PATCH v2] [RTEMS] Always use atomic builtins for libstdc++

On Sep 22 2016, Sebastian Huber wrote: > diff --git a/libstdc++-v3/acinclude.m4 b/libstdc++-v3/acinclude.m4 > index 6d897be..d7db435 100644 > --- a/libstdc++-v3/acinclude.m4 > +++ b/libstdc++-v3/acinclude.m4 > @@ -3490,9 +3490,10 @@ EOF >AC_LANG_RESTORE >

Re: [PATCH GCC][v2]Simplify alias check code generation in vectorizer

On Thu, Sep 22, 2016 at 11:43 AM, Bin.Cheng wrote: > On Wed, Sep 21, 2016 at 3:01 PM, Richard Biener > wrote: >> On Tue, Sep 20, 2016 at 5:25 PM, Bin Cheng wrote: >>> Hi, >>> I originally posted a patch improving code

Re: [v3 PATCH] PR libstdc++/77288 and the newest proposed resolution for LWG 2756

On 22/09/16 12:41 +0300, Ville Voutilainen wrote: On 22 September 2016 at 12:37, Christophe Lyon wrote: Does the attached patch fix the problem? Yes, thanks! Here be the changelog. Jonathan, ok for trunk? Patch attached again for convenience. OK, thanks.

[PATCH] Fix LTO with Java some more

Ok, I know... (I'll eventually backport this and the earlier change) Thus, committed as obvious. Richard. 2016-09-22 Richard Biener java/ * class.c (push_super_field): Set DECL_CONTEXT. Index: gcc/java/class.c

Re: [Patch] Fix variant::operator= on references

On 22/09/16 03:40 -0700, Tim Shen wrote: On Thu, Sep 22, 2016 at 3:36 AM, Tim Shen wrote: Then my question is, what about type traits uses like is_copy_constructible? I have seen non-qualified uses in std::any and std::optional and other places. Should all of them be

Re: [RFC] Update gmp/mpfr/mpc minimum versions

On Thu, 22 Sep 2016, Martin Sebor wrote: > In light of this risk and given that the recommended MPFR version > is still 2.4 I wonder if the download_prerequisites script shouldn't > instead download the minimum supported version. That way those of No, it should download the latest version known

Re: [RFC] Update gmp/mpfr/mpc minimum versions

On 09/22/16 19:26, Martin Sebor wrote: > On 04/27/2016 09:47 AM, Bernd Edlinger wrote: >> >> >> Yes, when they are pre-installed there should be no problem. >> Also newer versions than these seem to work. >> >> In-tree only the versions that download_prerequisite picks are >> tested and guaranteed

Re: [Patch] Remove all uses of TARGET_FLT_EVAL_METHOD_NON_DEFAULT and poison it

On Thu, 22 Sep 2016, James Greenhalgh wrote: > The relaxation isn't portable, and keeping it in place is tricky, so this > patch removes it, and poisons TARGET_FLT_EVAL_METHOD_NON_DEFAULT in > system.h to prevent future use. > > Bootstrapped and tested on x86_64 with

Re: [RFC] Update gmp/mpfr/mpc minimum versions

On 09/22/16 20:00, Joseph Myers wrote: > On Thu, 22 Sep 2016, Bernd Edlinger wrote: > >> There is no feasible way how to make all gmp/mpfr/mpc versions from >> minimal to latest build for all targets and all possible >> cross-configurations. >> >> I hope that we do not "recommend" these versions.

Re: [RFC] Update gmp/mpfr/mpc minimum versions

On 09/22/16 20:07, Moritz Klammler wrote: > Martin Sebor writes: > >> [...] >> >>> In-tree only the versions that download_prerequisite picks are >>> tested and guaranteed to work. >> >> I was made aware today that my recent patch for pr49905 broke >> bootstrap with MPFR 2.4: >>

Re: [RFC] Update gmp/mpfr/mpc minimum versions

On Thu, 22 Sep 2016, Bernd Edlinger wrote: > There is no feasible way how to make all gmp/mpfr/mpc versions from > minimal to latest build for all targets and all possible > cross-configurations. > > I hope that we do not "recommend" these versions. > > They are only the minimum versions for

Re: [RFC] Update gmp/mpfr/mpc minimum versions

Martin Sebor writes: > [...] > >> In-tree only the versions that download_prerequisite picks are >> tested and guaranteed to work. > > I was made aware today that my recent patch for pr49905 broke > bootstrap with MPFR 2.4: > >

Re: [RFC] Update gmp/mpfr/mpc minimum versions

On Thu, 22 Sep 2016, Moritz Klammler wrote: > As some of you might already be aware of, I'm currently trying to get a > new version of the `contrib/download_prerequisites` script approved that > will verify the checksums of the tarballs it downloads and also provides > additional options. If it

Re: [PATCHv3][ARM] -mpure-code option for ARM

This patch broke bootstrap. In file included from /nasfarm/edelsohn/src/src/gcc/target-def.h:106:0, from /nasfarm/edelsohn/src/src/gcc/config/rs6000/rs6000.c:77:./target-hooks-def.h:92:38: error: 'hook_uint_uintp_false' was not declared in this scope #define

Re: PR35503 - warn for restrict pointer

On Thu, 22 Sep 2016, Prathamesh Kulkarni wrote: > Would that be acceptable ? I am not sure how to make %Z check if the > argument has type vec * > since vec is not really a builtin C type. > Could you suggest me a better solution so that the format checker will check > if arg has type vec *

Re: [RFC] Update gmp/mpfr/mpc minimum versions

On September 22, 2016 8:00:40 PM GMT+02:00, Joseph Myers wrote: >On Thu, 22 Sep 2016, Bernd Edlinger wrote: > >> There is no feasible way how to make all gmp/mpfr/mpc versions from >> minimal to latest build for all targets and all possible >> cross-configurations. >>

Re: [v3 PATCH] PR libstdc++/77288 and the newest proposed resolution for LWG 2756

On 22 September 2016 at 15:25, Jonathan Wakely wrote: > On 22/09/16 12:15 +0100, Jonathan Wakely wrote: >> >> On 22/09/16 11:16 +0100, Jonathan Wakely wrote: >>> >>> (Somebody should fix PR58938 so exception_ptr is portable). >> >> >> Christophe, would you be able to test this

[PATCH, i386]: Improve x86 target selectors and cleanup a couple of gcc.dg tests

2016-09-22 Uros Bizjak * gcc.dg/ifcvt-1.c: Compile also for 64-bit i?86-*-* target. * gcc.dg/ifcvt-2.c: Ditto. * gcc.dg/zero_bits_compound-1.c: Ditto. * gcc.dg/zero_bits_compound-1.c: Ditto. * gcc.dg/pr40550.c: Simplify target selectors. Use

Re: [PATCH] Fix PR ipa/77653

On Thu, Sep 22, 2016 at 1:18 PM, Martin Liška wrote: > Hi. > > After some investigation, it shows that IPA ICF merges a pair of variables > where > for just one them address matters. Which is obvious error, fixed in attached > patch. > > Patch can bootstrap on

[PATCH] Fix PR77677

This avoids some more TREE_OVERFLOWs in the IL (which now confuses IPA VRP). Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk. Richard. 2016-09-22 Richard Biener PR middle-end/77677 * gimple-match-head.c (gimple_resimplify1): Drop

[PATCH] Fix PR77678

This fixes an ice-on-invalid for fortran. Bootstrapped/tested on x86_64-unknown-linux-gnu, applied to trunk. Richard. 2016-09-22 Richard Biener PR middle-end/77678 * expr.c (expand_expr_real_1): Guard array access against negative offset. Index:

[PATCH] Fix PR77697

This fixes PR77697, an ice-on-invalid for Fortran (varasm later errors). Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk. Richard. 2016-09-22 Richard Biener PR middle-end/77697 * gimple-fold.c (fold_array_ctor_reference): Turn

[PATCH] Disable sim build for ARC in top-level configure.ac

Hi, This disables "sim" build for ARC, otherwise it is required to pass --disable-sim to top-level configure. Anton 0001-Disable-sim-builds-for-ARC-in-top-level-configure.ac.patch Description: 0001-Disable-sim-builds-for-ARC-in-top-level-configure.ac.patch

Re: [v3 PATCH] PR libstdc++/77288 and the newest proposed resolution for LWG 2756

On 22/09/16 11:16 +0100, Jonathan Wakely wrote: (Somebody should fix PR58938 so exception_ptr is portable). Christophe, would you be able to test this patch? It uses a single global mutex for exception_ptr objects, which doesn't scale well but that probably isn't a problem for processors

[PATCH] Fix PR ipa/77653

Hi. After some investigation, it shows that IPA ICF merges a pair of variables where for just one them address matters. Which is obvious error, fixed in attached patch. Patch can bootstrap on ppc64le-redhat-linux and survives regression tests. Ready to be installed? Martin >From

Backport fix for PR 65210 to gcc-5-branch

Hi, Is it ok to backport PR 65210 to gcc-5-branch? The patch is already in 6.x and trunk. Regards Senthil gcc/ChangeLog 2016-09-22 Senthil Kumar Selvaraj Backport from trunk r227496 PR target/65210 * config/avr/avr.c

[PATCH] Improve SCCVN with devirtualization to pure/const calls

Not because it might be terribly important but the recent change triggered a latent(?) issue on AIX which broke bootstrap. Let's try if another change mitigates that. The change basically allows devirt-to-const/pure to be taken into account during the value-numbering rather than only in

Correct module change introduced by DTIO patch.

Dear All, This patch has just been committed to trunk as r240349, following an OK from Andre on #gfortran. This was urgently needed since the original DTIO patch, committed on 2016-31-08, added two extra pairs of parentheses, which are always empty, to the intrinsic operator list in module

Re: Make regcprop to eliminate noop moves better

> > while working on the GCN port I ended up with many redundant register copies > > of the form > > mov reg, exec > > do something > > mov reg, exec > > do something > > ... > > these copies are generated by LRA because exec is small register class and > > needs a lot of reloading (it could

Re: [RFC] Extend ipa-bitwise-cp with pointer alignment propagation

> Hi, > The attached patch tries to extend ipa bits propagation to handle > pointer alignment propagation. > The patch just disables ipa-cp-alignment pass, I suppose we want to > eventually remove it ? Yes, can you please verify that alignments it computes are monotonously worse than those your

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

Hi Martin, > your patch broke bootstrap with MPFR 2.4.2, which is still the > recommended (or perhaps minimal) version according to install.texi: [...] > The following patch (together with your other one to fix ILP32 targets) > allows a sparc-sun-solaris2.12 bootstrap to continue. I'm going to >

[C++ Patch] PR 71979

Hi, in this ICE on invalid [5/6/7] regression the gcc_assert in build_base_path is triggered during error recovery when lookup_base returns NULL_TREE (makes sense because B is looked up as base of A!). It seems to me that we can simply allow for this case in the assertion and be done with

Re: [C++ PATCH] Aligned new option handling fixes (PR c++/77651)

On Thu, Sep 22, 2016 at 4:58 AM, Christophe Lyon wrote: > This new test (aligned-new6.C) fails on arm/aarch64 bare-metal targets > (using newlib): > arm-none-eabi/./libstdc++-v3/src/.libs/libstdc++.a(new_opa.o): In > function `operator new(unsigned int,

Re: [PATCH, ARM/testsuite 6/7] Force soft float in ARMv6-M and ARMv8-M Baseline options

On 22/09/16 15:51, Thomas Preudhomme wrote: > Sorry, noticed an error in the patch. It was not caught during testing > because GCC was built with --with-mode=thumb. Correct patch attached. > > Best regards, > > Thomas > > On 22/09/16 14:49, Thomas Preudhomme wrote: >> Hi, >> >> ARMv6-M and

Re: [PATCH, ARM/testsuite 6/7] Force soft float in ARMv6-M and ARMv8-M Baseline options

Sorry, noticed an error in the patch. It was not caught during testing because GCC was built with --with-mode=thumb. Correct patch attached. Best regards, Thomas On 22/09/16 14:49, Thomas Preudhomme wrote: Hi, ARMv6-M and ARMv8-M Baseline only support soft float ABI. Therefore, the

[Fortran, accaf, patch, v1] Fixing compatibility with opencoarrays (mostly)

Hi all, attached patch fixes compatibility with opencoarrays by using the old coarray interface of caf_get() as long as possible. Bootstrapped and regtested ok on x86_64-linux/F23. Ok for trunk? Regards, Andre -- Andre Vehreschild * Email: vehre ad gmx dot de gcc/fortran/ChangeLog:

Re: [PATCH][RFC][regrename][sel-sched] Fix arm bootstrap

On Thu, 22 Sep 2016, Kyrill Tkachov wrote: > > I don't follow. The macro used as a boolean in places changed by your patch > > is H_F_P_IS_FRAME_POINTER, not H_F_P_REGNUM. > > > > Am I missing something? > > I'm following Bernd's proposed change from: >

Re: Make regcprop to eliminate noop moves better

On 09/22/2016 01:48 PM, Jan Hubicka wrote: * postreload.c (reload_cse_simplify): Also accept USE in noop move patterns. diff --git a/gcc/postreload.c b/gcc/postreload.c index 61c1ce8..4f3a526 100644 --- a/gcc/postreload.c +++ b/gcc/postreload.c @@ -153,7 +153,8 @@

Re: [PATCH, ARM/testsuite 6/7] Force soft float in ARMv6-M and ARMv8-M Baseline options

On 22/09/16 16:47, Richard Earnshaw (lists) wrote: On 22/09/16 15:51, Thomas Preudhomme wrote: Sorry, noticed an error in the patch. It was not caught during testing because GCC was built with --with-mode=thumb. Correct patch attached. Best regards, Thomas On 22/09/16 14:49, Thomas

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

your patch broke bootstrap with MPFR 2.4.2, which is still the recommended (or perhaps minimal) version according to install.texi: /vol/gcc/src/hg/trunk/local/gcc/gimple-ssa-sprintf.c: In function 'int {anonymous}::format_floating_max(tree, char)':

Re: [PATCH][RFC][regrename][sel-sched] Fix arm bootstrap

On 09/22/16 16:34, Kyrill Tkachov wrote: > > On 22/09/16 15:27, Alexander Monakov wrote: >> H_F_P_IS_FRAME_POINTER (the ChangeLog is wrong). As I understand, the >> issue is >> that config/arm/arm.h defines that to plain 0, which causes the >> warning (ugh?). >> >> Does the following restore

Re: [PATCH][RFC][regrename][sel-sched] Fix arm bootstrap

On 22/09/16 15:39, Alexander Monakov wrote: On Thu, 22 Sep 2016, Kyrill Tkachov wrote: Sorry no, the problem is HARD_FRAME_POINTER_REGNUM that is defined as: #define HARD_FRAME_POINTER_REGNUM\ (TARGET_ARM\ ? ARM_HARD_FRAME_POINTER_REGNUM\ :

Re: [PATCHv3][ARM] -mpure-code option for ARM

On 22/09/16 16:04, Andre Vieira (lists) wrote: > > I reworked the patch according to the comments above. > > Is this OK? > > gcc/ChangeLog: > 2016-09-22 Andre Vieira > Terry Guo > > * target.def (elf_flags_numeric):

Re: [PATCHv3][ARM] -mpure-code option for ARM

On 22/09/16 14:52, Richard Earnshaw (lists) wrote: > On 11/07/16 17:56, Andre Vieira (lists) wrote: >> On 07/07/16 13:30, mickael guene wrote: >>> Hi Andre, >>> >>> Another feedback on your purecode patch. >>> You have to disable casesi pattern since then it will >>> generate wrong code with

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

On 09/22/2016 06:14 AM, Rainer Orth wrote: Hi Martin, your patch broke bootstrap with MPFR 2.4.2, which is still the recommended (or perhaps minimal) version according to install.texi: [...] The following patch (together with your other one to fix ILP32 targets) allows a

Re: [PATCH] fix ILP32 bootstrap failures due to -Wformat-length

Jeff or Richard, As the two middle end maintainers familiar with my work, can one of you approve the updated patch? It's necessary to restore ILP32 bootstrap on a number of targets (pr77676). https://gcc.gnu.org/ml/gcc-patches/2016-09/msg01477.html Thanks Martin On 09/21/2016 06:28 PM,

  1   2   >