[Patch, x86_64] Fix znver1 imov/imovx load reservations.

Hi Maintainers, The below patch fixes integer load type reservations for -march=znver1. Bootstrapped and regtested on x86_64-pc-linux-gnu. Ok to commit to trunk ? (-Snip) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 9659fbf..19b4066 100644 --- a/gcc/ChangeLog +++

[Bug target/77930] New: Compile time hog w/ -O2 -g -funroll-loops -ftree-loop-if-convert-stores on 32-bit targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77930 Bug ID: 77930 Summary: Compile time hog w/ -O2 -g -funroll-loops -ftree-loop-if-convert-stores on 32-bit targets Product: gcc Version: 7.0 Status: UNCONFIRMED

[Bug tree-optimization/77929] New: [7 Regression] ICE: verify_gimple failed (error: non-trivial conversion at assignment)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77929 Bug ID: 77929 Summary: [7 Regression] ICE: verify_gimple failed (error: non-trivial conversion at assignment) Product: gcc Version: 7.0 Status: UNCONFIRMED

Re: Repository for the conversion machinery

Joseph Myers : > In practice there are a lot of ways people have messed up ChangeLog > commits or commit messages that I would expect to confuse such author > extraction, even before you get to the parts of the history converted from > CVS. This is also true. I looked

Re: [RFC][VRP] Improve intersect_ranges

Hi Richard, On 10/10/16 20:13, Richard Biener wrote: On Sat, Oct 8, 2016 at 9:38 PM, kugan wrote: Hi Richard, Thanks for the review. On 07/10/16 20:11, Richard Biener wrote: On Fri, Oct 7, 2016 at 12:00 AM, kugan wrote:

[Bug c++/77927] unary right fold fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77927 --- Comment #3 from Jeff Mirwaisi --- Apologies for the poor bug report, to clarify, unary right folds which use a binary operator in the fold parameter are failing to compile: ( (x op1 y) op2... ); //clearer examples - error: binary

[Bug tree-optimization/77921] [7 Regression] tree-ssanames.c miscompiled during PGO bootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77921 --- Comment #5 from Markus Trippelsdorf --- (In reply to kugan from comment #4) > Sorry about the breakage. I will try to reproduce it. > > (In reply to Markus Trippelsdorf from comment #1) > > gcc version 7.0.0 20161007 was fine > Are you

Go patch committed: move Backend/Linemap creation out of frontend

This patch by Than McIntosh moves the calls that create the GCC-specific Backend and Linemap objects out of the Go frontend into the gccgo interface code. This allows for more flexibility creating those objects. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.

[PING] [PATCH] fix outstanding -Wformat-length failures (pr77735 et al.)

I'm looking for a review of the patch below: https://gcc.gnu.org/ml/gcc-patches/2016-10/msg00043.html The patch should clean up the remaining test suite failures on ILP32 targets and also fixes up some remaining issues in the gimple-ssa-sprintf pass that stand in the way of re-enabling the

[Bug tree-optimization/77902] Auto-vectorizes epilogue loops of manually vectorized functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77902 --- Comment #2 from Allan Jensen --- While this have been the case in both GCC 5 and GCC 6, it appears to both failing cases previously meantioned already produced the best case result in using a half recent GCC 7. gcc version 7.0.0 20160923

[Bug tree-optimization/77921] [7 Regression] tree-ssanames.c miscompiled during PGO bootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77921 --- Comment #4 from kugan at gcc dot gnu.org --- Sorry about the breakage. I will try to reproduce it. (In reply to Markus Trippelsdorf from comment #1) > gcc version 7.0.0 20161007 was fine Are you saying that this is issue is gone latent?

Go patch committed: copy print code from Go 1.7 runtime

This patch copies the code that implements the print and println predeclared functions from the Go 1.7 runtime. The compiler is changed to use the new names, and to call the printlock and printunlock functions around a sequence of print calls. The writebuf field in the g struct changes to a

[Bug tree-optimization/77902] Auto-vectorizes epilogue loops of manually vectorized functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77902 --- Comment #1 from Allan Jensen --- Further experimentation shows that GCC can sometimes reason about the remaining range but does so inconsistenly. For instance this examplse also fails: int result = 0; for (; count >= 4; count -= 4)

[Bug c++/77927] unary right fold fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77927 --- Comment #2 from Jeff Mirwaisi --- //error: binary expression in operand of fold-expression

Re: [PATCH] Improve performance of list::reverse

I haven't yet but I will try and sort it out tomorrow. If we're replacing the current method with one that takes a size parameter when _GLIBCXX_USE_CXX11_ABI is defined, is this going to cause any issues with ABI compatibility? If not, then I agree that we should go with the #if version. On 10

[Bug target/77586] [7 Regression] ia64 target fails to build due to ICE triggered by -fself-test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77586 --- Comment #3 from Joseph S. Myers --- Author: jsm28 Date: Mon Oct 10 22:43:07 2016 New Revision: 240955 URL: https://gcc.gnu.org/viewcvs?rev=240955=gcc=rev Log: Always support float128 on ia64 (PR target/77586). Bug 77586, and previously

[Bug target/77586] [7 Regression] ia64 target fails to build due to ICE triggered by -fself-test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77586 Joseph S. Myers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: Always support float128 on ia64 (PR target/77586)

On 10/04/2016 10:46 AM, Joseph Myers wrote: Bug 77586, and previously , reports ia64-elf failing to build because of float128_type_node being NULL, but being used by the back end for __float128. The global float128_type_node is only

Re: [PATCH] Update docs on libstdc++ source-code layout

On 10/10/16 19:57 +0100, Jonathan Wakely wrote: Self-explanatory updates to the docs, and regenerating after the various recent changes. * doc/xml/manual/appendix_contributing.xml (contrib.organization): Describe other subdirectories and add markup. Remove outdated

Re: [PATCH 4/5] shrink-wrap: Shrink-wrapping for separate components

On Mon, Oct 10, 2016 at 03:21:31PM -0600, Jeff Law wrote: > On 09/30/2016 04:34 AM, Segher Boessenkool wrote: > >[ whoops, message too big, resending with the attachment compressed ] > > > >On Tue, Sep 27, 2016 at 03:14:51PM -0600, Jeff Law wrote: > >>With transposition issue addressed, the only

[Bug middle-end/77928] New: Add __builtin_iseqsig

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77928 Bug ID: 77928 Summary: Add __builtin_iseqsig Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: middle-end

[Bug c++/77927] unary right fold fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77927 --- Comment #1 from Jeff Mirwaisi --- //unary right fold fails to compile template void f(){int A[]={(((void)N,int()),...)};} //corresponding left fold works as expected template void f(){int A[]={(...,((void)N,int()))};} //both are simple

[Bug c++/77927] New: unary right fold fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77927 Bug ID: 77927 Summary: unary right fold fails to compile Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug tree-optimization/77898] incorrect VR_ANTI_RANGE after evrp and before vrp1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77898 --- Comment #8 from Martin Sebor --- No, I get the range for _2 with a "def_stmt _2 = (sizetype) i_4;" i.0_1: [0, +INF] _2: ~[2147483648, 18446744071562067967] _3: [0, +INF] i_4: VARYING i_6(D): VARYING ... # i_4 = PHI _2

Re: Converting to LRA (calling all maintainers)

> > Do we have a Wiki page for the cc0 conversion? If no, I can start one > > based on my fresh experience with the Visium port. > > There is none so far as far as I know. Thanks for volunteering, OK, the page is at https://gcc.gnu.org/wiki/CC0Transition and linked to from the "Current

[Bug middle-end/77926] New: Add __builtin_iszero

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77926 Bug ID: 77926 Summary: Add __builtin_iszero Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: middle-end

[Bug middle-end/77925] Add __builtin_issubnormal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77925 Joseph S. Myers changed: What|Removed |Added Severity|normal |enhancement

[Bug middle-end/77925] New: Add __builtin_issubnormal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77925 Bug ID: 77925 Summary: Add __builtin_issubnormal Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end

[Bug bootstrap/77917] undefined reference to '__aeabi_unwind_cpp_pr0' during ARM bootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77917 --- Comment #3 from PeteVine --- Unfortunately, even with `--with-build-config=bootstrap-lto` the result was unchanged which makes the issue real after all? Unsurprisingly, eliminating just the `-flto` flag (-flto=4 to be exact) led to a

[Bug tree-optimization/77424] Identical statements in if-else branches

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77424 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com

Re: [v3 PATCH] Make any's copy assignment operator exception-safe, don't copy the underlying value when any is moved, make in_place constructors explicit.

On 10/10/16 22:21 +0300, Ville Voutilainen wrote: This code was all pretty carefully written to avoid any redundant operations. Does this change buy us anything except simpler code? As discussed, destroying the value but leaving the manager non-null will do bad things. Oops again on my part!

Re: Repository for the conversion machinery

On Mon, 10 Oct 2016, Eric S. Raymond wrote: > I strongly recomend that if you want to try this, you separate it from the > initial repo conversion. That is, get the project to git first. Then > see if you can data-mine author information out of the history. If, > and only if, you get results

Re: [PATCH, C++] Warn on redefinition of builtin functions (PR c++/71973)

On 10/06/16 22:37, Bernd Edlinger wrote: > On 10/06/16 16:14, Kyrill Tkachov wrote: >> >> @@ -1553,7 +1588,7 @@ duplicate_decls (tree newdecl, tree olddecl, bool >> >> /* Whether or not the builtin can throw exceptions has no >>bearing on this declarator. */ >> - TREE_NOTHROW

Re: [patch] aarch64-*-freebsd* support for gcc.

On 10.10.16 23:10, Jeff Law wrote: On 10/10/2016 03:07 PM, Andreas Tobler wrote: Hi all, the attached patch brings support for the aarch64-*-freebsd* target. Bootstraped and tested, results on the list. Not that many results due to board instabilities I lack a cavium ;) Ok for main? And

[Bug tree-optimization/77898] incorrect VR_ANTI_RANGE after evrp and before vrp1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77898 --- Comment #7 from Marc Glisse --- (In reply to Martin Sebor from comment #6) > I meant a subrange of the i variable (i.e., a subrange of int). The range > of every variable is necessarily bounded by its type so returning a range of >

Re: PATCH to introduce c-family/c-warn.c

On 10/10/2016 10:36 AM, Marek Polacek wrote: As outlined recently, this patch creates a new c-warn.c file, where various diagnostic routines should reside, making c-common.c a little bit shorter. There are no function changes though. While at it, I fixed all tabs/space problems in those

Re: [PATCH 4/5] shrink-wrap: Shrink-wrapping for separate components

On 09/30/2016 04:34 AM, Segher Boessenkool wrote: [ whoops, message too big, resending with the attachment compressed ] On Tue, Sep 27, 2016 at 03:14:51PM -0600, Jeff Law wrote: With transposition issue addressed, the only blocker I see are some simple testcases we can add to the suite. They

[Bug c++/64666] gcc wrongly accepts assignment in constant expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64666 Jason Merrill changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

Re: [patch] aarch64-*-freebsd* support for gcc.

On 10/10/2016 03:07 PM, Andreas Tobler wrote: Hi all, the attached patch brings support for the aarch64-*-freebsd* target. Bootstraped and tested, results on the list. Not that many results due to board instabilities I lack a cavium ;) Ok for main? And if yes, how far can I backport? Down

[patch] aarch64-*-freebsd* support for gcc.

Hi all, the attached patch brings support for the aarch64-*-freebsd* target. Bootstraped and tested, results on the list. Not that many results due to board instabilities I lack a cavium ;) Ok for main? And if yes, how far can I backport? Down to 5.4? TIA, Andreas libgcc: 2016-10-10

[tree-optimization/71947] Avoid unwanted propagations

So if we have an equality conditional between A & B, we record into our const/copy tables A = B and B = A. This helps us discover some of the more obscure equivalences. But it also creates problems with an expression like A ^ B Where we might cprop the first operand generating B ^ B

Re: [PATCH] 77864 Fix noexcept conditions for map/set default constructors

Trying again...with a few edits. > On Mon, Oct 10, 2016 at 3:24 PM, François Dumont > wrote: > > @@ -602,24 +612,32 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION > struct _Rb_tree_impl : public _Node_allocator > { >_Key_compare _M_key_compare; > -

Fwd: C++ PATCH for c++/77890, 77912 (C++17 class deduction issues)

77890: we were losing the CLASS_PLACEHOLDER_TEMPLATE when reducing the level of a TEMPLATE_TYPE_PARM. 77912: after 77890 was fixed, we were complaining about an undefined deduction guide; set cp_unevaluated_operand to prevent that. Tested x86_64-pc-linux-gnu, applying to trunk. commit

[Bug tree-optimization/77898] incorrect VR_ANTI_RANGE after evrp and before vrp1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77898 --- Comment #6 from Martin Sebor --- I meant a subrange of the i variable (i.e., a subrange of int). The range of every variable is necessarily bounded by its type so returning a range of [INT_MIN, INT_MAX] for an int isn't terribly helpful.

[Bug c++/77912] [C++17 feature] class template deduction fails in template functions and generic lambdas

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77912 Jason Merrill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/77890] class template type deduction fails for lambda functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77890 Jason Merrill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/77912] [C++17 feature] class template deduction fails in template functions and generic lambdas

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77912 --- Comment #5 from Jason Merrill --- Author: jason Date: Mon Oct 10 20:48:51 2016 New Revision: 240948 URL: https://gcc.gnu.org/viewcvs?rev=240948=gcc=rev Log: C++17 class deduction issues PR c++/77890 PR c++/77912 *

[Bug c++/77890] class template type deduction fails for lambda functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77890 --- Comment #4 from Jason Merrill --- Author: jason Date: Mon Oct 10 20:48:51 2016 New Revision: 240948 URL: https://gcc.gnu.org/viewcvs?rev=240948=gcc=rev Log: C++17 class deduction issues PR c++/77890 PR c++/77912 *

[PATCH], PR 77924, Fix PowerPC breakage on AIX

I accidently broke AIX with my patch on October 6th. That patch split -mfloat128 into -mfloat128-type and -mfloat128 under PowerPC Linux. This patch fixes that issue. I bootstrapped it on PowerPC Linux with no regressions, and David Edelsohn reports that it fixes the problem on AIX. Is it ok

[Bug tree-optimization/71947] [6/7 Regression] x ^ y not folded to 0 if x == y by DOM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71947 --- Comment #12 from Jeffrey A. Law --- Author: law Date: Mon Oct 10 20:40:59 2016 New Revision: 240947 URL: https://gcc.gnu.org/viewcvs?rev=240947=gcc=rev Log: PR tree-optimization/71947 * tree-ssa-dom.c (cprop_into_stmt):

[Bug tree-optimization/77898] incorrect VR_ANTI_RANGE after evrp and before vrp1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77898 --- Comment #5 from Marc Glisse --- (In reply to Martin Sebor from comment #4) > I suppose I was expecting that that after EVRP (and before VRP1) > get_range_info() would either succeed and return a range representing a > subrange of the the

Re: Repository for the conversion machinery

Joseph Myers : > This is still hypothetical, since I haven't seen any scripts posted that > would actual implement this, or any resulting mappings of commits, and one > wouldn't normally expect a repository conversion to attempt to distinguish > committer from author

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On Mon, Oct 10, 2016 at 12:29:32PM -0700, Jerry DeLisle wrote: > On 10/10/2016 08:06 AM, Fritz Reese wrote: > > https://gcc.gnu.org/ml/fortran/2016-09/msg00163.html [original] > > https://gcc.gnu.org/ml/fortran/2016-09/msg00183.html [latest] > > > > On Wed, Sep 28, 2016 at 4:14 PM, Fritz Reese

[Bug c++/77825] [7 Regression] return type deduction regression in C++17 mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77825 Jason Merrill changed: What|Removed |Added Status|NEW |UNCONFIRMED CC|

[Bug tree-optimization/77898] incorrect VR_ANTI_RANGE after evrp and before vrp1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77898 --- Comment #4 from Martin Sebor --- I suppose I was expecting that that after EVRP (and before VRP1) get_range_info() would either succeed and return a range representing a subrange of the the variable's type or fail and return VR_VARYING. If

[libgo] Silence compiler error message

Hi, on Solaris the configuration of the library yields an ugly: checking whether linker supports split/non-split linked together... cc1: error: '-fsplit-stack' is not supported by this compiler configuration xgcc: error: conftest1.o: No such file or directory no Tested on x86-64/Linux and

[Bug target/68752] PowerPC: vector reciprocal square root estimate missed optimisations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68752 --- Comment #4 from Carl Love --- I do not seem to have permission to change the status of the bug. Anton, can you recheck the issue and close if you agree it is no longer an issue. Thanks. Carl

New Swedish PO file for 'gcc' (version 6.2.0)

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 Swedish team of translators. The file is available at: http://translationproject.org/latest/gcc/sv.po (This file, 'gcc-6.2.0.sv.po', has

[Bug target/68752] PowerPC: vector reciprocal square root estimate missed optimisations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68752 --- Comment #3 from Carl Love --- I investigated the issue using GCC 6.1. The t1() function from file recip-vec-sqrtf.c file is as follows: void t1(void) { int i; for (i = 0; i < 4; i++) r[i] = a[i] / sqrtf (b[i]); } The assembly code being

[Bug target/68752] PowerPC: vector reciprocal square root estimate missed optimisations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68752 Carl Love changed: What|Removed |Added CC||cel at us dot ibm.com --- Comment #2 from

Move OVERRIDE/FINAL from gcc/coretypes.h to include/ansidecl.h (was: Re: [PATCH 1/2] Add OVERRIDE and FINAL macros to coretypes.h)

Please find below a patch moving the FINAL/OVERRIDE macros to include/ansidecl.h, as I was suggesting in the earlier discussion: On 05/06/2016 07:33 PM, Trevor Saunders wrote: > On Fri, May 06, 2016 at 07:10:33PM +0100, Pedro Alves wrote: >> On 05/06/2016 06:56 PM, Pedro Alves wrote: >> I was

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On 10/10/2016 08:06 AM, Fritz Reese wrote: > https://gcc.gnu.org/ml/fortran/2016-09/msg00163.html [original] > https://gcc.gnu.org/ml/fortran/2016-09/msg00183.html [latest] > > On Wed, Sep 28, 2016 at 4:14 PM, Fritz Reese wrote: >> Attached is a patch extending the GNU

[Bug tree-optimization/71947] [6/7 Regression] x ^ y not folded to 0 if x == y by DOM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71947 --- Comment #11 from Jeffrey A. Law --- So I don't like the pain of trying to fold at each propagation step. Specifically, the structure of the gimple statement can change, which invalidates the operand cache. And the canonicalization of

Re: [PATCH] 77864 Fix noexcept conditions for map/set default constructors

On 09/10/2016 17:14, Jonathan Wakely wrote: On 08/10/16 22:55 +0200, François Dumont wrote: On 06/10/2016 23:34, Jonathan Wakely wrote: On 06/10/16 22:17 +0200, François Dumont wrote: Another approach is to rely on existing compiler ability to compute conditional noexcept when defaulting

Re: [v3 PATCH] Make any's copy assignment operator exception-safe, don't copy the underlying value when any is moved, make in_place constructors explicit.

On 10 October 2016 at 21:19, Jonathan Wakely wrote: > I prefer to put "explicit" on a line of its own, as we do for return > types, but I won't complain if you leave it like this. Changed. >> + any(__rhs).swap(*this); > > > I was trying to avoid the "redundant" xfer

[Bug tree-optimization/77898] incorrect VR_ANTI_RANGE after evrp and before vrp1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77898 --- Comment #3 from Marc Glisse --- (In reply to Martin Sebor from comment #2) > I may also be confused about other things but below is what I see in GDB > when I call get_range_info() from plus_stmt_object_size() on the offset in >

[Bug target/77924] -mfloat128-type change broke AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77924 --- Comment #2 from Michael Meissner --- Created attachment 39785 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39785=edit Revised proposed patch to fix the problem without syntax error

[Bug tree-optimization/77824] unreachable code in SLSR GIMPLE pass

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77824 Bill Schmidt changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[PATCH] Update docs on libstdc++ source-code layout

Self-explanatory updates to the docs, and regenerating after the various recent changes. * doc/xml/manual/appendix_contributing.xml (contrib.organization): Describe other subdirectories and add markup. Remove outdated reference to check-script target. *

[PATCH] Fix PR77824

Hi, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77824 reports unreachable code where MODIFY_EXPR is being tested instead of SSA_NAME to identify RHS's for copies. This patch corrects that. I instrumented the compiler to identify copies being added to the candidate table, and found that this

Re: [PATCH 10/16] Introduce class function_reader (v3)

David Malcolm writes: > On Wed, 2016-10-05 at 18:00 +0200, Bernd Schmidt wrote: >> On 10/05/2016 06:15 PM, David Malcolm wrote: >> >* errors.c: Use consistent pattern for bconfig.h vs config.h >> >includes. >> >(progname): Wrap with #ifdef GENERATOR_FILE. >> >

[Bug tree-optimization/77824] unreachable code in SLSR GIMPLE pass

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77824 --- Comment #7 from Bill Schmidt --- Author: wschmidt Date: Mon Oct 10 18:39:41 2016 New Revision: 240945 URL: https://gcc.gnu.org/viewcvs?rev=240945=gcc=rev Log: 2016-10-10 Bill Schmidt PR

[PATCH] Correct C++11 implementation status docs

The std::list allocator status and the note about timed mutexes are out of date, those are both completely implemented now (there's a fallback timed mutex for targets without _POSIX_TIMEOUTS). * doc/xml/manual/status_cxx2011.xml: Correct C++11 status. Committed to trunk. I'll backport

[Bug c++/64666] gcc wrongly accepts assignment in constant expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64666 --- Comment #7 from Harald van Dijk --- (In reply to Jason Merrill from comment #6) > > but > > anyway, even with -std=c++14 -pedantic-errors, no message at all is given > > for the program in my earlier comment. > > I don't see the syntax

[PATCH] Use noexcept instead of _GLIBCXX_USE_NOEXCEPT

This file is compiled with -std=gnu++11 so there's no need to use the macro, we can use noexcept directly. * libsupc++/eh_ptr.cc (exception_ptr): Replace _GLIBCXX_USE_NOEXCEPT with noexcept. Tested powerpc64le-linbux, committed to trunk. commit

Re: [v3 PATCH] Make any's copy assignment operator exception-safe, don't copy the underlying value when any is moved, make in_place constructors explicit.

On 10/10/16 19:19 +0100, Jonathan Wakely wrote: On 08/10/16 16:07 +0300, Ville Voutilainen wrote: Tested on Linux-x64. 2016-10-08 Ville Voutilainen Make any's copy assignment operator exception-safe, don't copy the underlying value when any is moved, make

[Bug c++/64666] gcc wrongly accepts assignment in constant expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64666 Jason Merrill changed: What|Removed |Added CC||jason at gcc dot gnu.org --- Comment #6

[Bug target/77924] -mfloat128-type change broke AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77924 --- Comment #1 from Michael Meissner --- Created attachment 39784 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39784=edit Proposed patch to fix the problem This patch should only create the __ibm128 type when long double == IEEE and

[Bug tree-optimization/77898] incorrect VR_ANTI_RANGE after evrp and before vrp1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77898 Martin Sebor changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

Re: [PATCH] Implement new hook for max_align_t_align

Attached is an updated version using the new builtin __MAX_ALIGN_T_ALIGN__. This simplifies the declaration of max_align_t and ensures it is always the same as max_align_t_align(). Tested on hppa-unknown-linux-gnu. Okay for trunk? Dave -- John David Anglin dave.ang...@bell.net

Re: [v3 PATCH] Make any's copy assignment operator exception-safe, don't copy the underlying value when any is moved, make in_place constructors explicit.

On 08/10/16 16:07 +0300, Ville Voutilainen wrote: Tested on Linux-x64. 2016-10-08 Ville Voutilainen Make any's copy assignment operator exception-safe, don't copy the underlying value when any is moved, make in_place constructors explicit. *

[Bug c++/77890] class template type deduction fails for lambda functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77890 Jason Merrill changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[Bug c++/77912] [C++17 feature] class template deduction fails in template functions and generic lambdas

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77912 Jason Merrill changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug tree-optimization/77899] incorrect VR_RANGE for a signed char function argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77899 --- Comment #10 from Martin Sebor --- Yes, I've also come to realize that the surprising signed char range is a red herring since the abort in the following test case is also not optimized away. void f (_Bool i) { char d [3]; const char *p

Re: Repository for the conversion machinery

On Mon, 10 Oct 2016, Jonathan Wakely wrote: > > My view is: contributors are free to specify what name and email address > > they want used, but if they want something other than a single name and > > email address for the whole commit history with a given username, it's the > > contributor's

[Bug target/77924] -mfloat128-type change broke AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77924 Michael Meissner changed: What|Removed |Added Priority|P3 |P2 CC|

[Bug target/77924] -mfloat128-type change broke AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77924 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/77924] New: -mfloat128-type change broke AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77924 Bug ID: 77924 Summary: -mfloat128-type change broke AIX Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: target

[Bug tree-optimization/77899] incorrect VR_RANGE for a signed char function argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77899 --- Comment #9 from Marc Glisse --- I don't see what "signed" has to do with it. void f (unsigned char i) { char d [1260]; const char *p = [130]; p += i; if (p < d + 2 || d + 757 < p) __builtin_abort (); } We don't optimize this

[Bug tree-optimization/77899] incorrect VR_RANGE for a signed char function argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77899 --- Comment #8 from Andrew Pinski --- (In reply to Martin Sebor from comment #7) > Here's what I see in GDB after get_range_info returns to update_value_range: > > (gdb) p rtype > $39 = VR_ANTI_RANGE > (gdb) p min > $40 = { = {val = {128,

Go patch committed: remove GCC-specific linemap usage

This patch by Than McIntosh removes a GCC-specific use of the linemap code to retrieve the line number. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian 2016-10-10 Than McIntosh * go-linemap.cc (Gcc_linemap::location_line): New method.

[Bug c++/77923] GCC emits "declares nothing" diagnostic on meaningful declarations.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77923 Jonathan Wakely changed: What|Removed |Added Keywords||diagnostic

[Bug c++/55039] std::addressof vs. constexpr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55039 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/55004] [meta-bug] constexpr issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004 Bug 55004 depends on bug 55039, which changed state. Bug 55039 Summary: std::addressof vs. constexpr https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55039 What|Removed |Added

[Bug tree-optimization/77899] incorrect VR_RANGE for a signed char function argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77899 --- Comment #7 from Martin Sebor --- Here's what I see in GDB after get_range_info returns to update_value_range: (gdb) p rtype $39 = VR_ANTI_RANGE (gdb) p min $40 = { = {val = {128, 18061790, 140737235530016}, len = 1, precision = 64}, static

[Bug tree-optimization/77899] incorrect VR_RANGE for a signed char function argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77899 --- Comment #6 from Andrew Pinski --- (In reply to Martin Sebor from comment #5) > My other point (one somewhat related to bug 77898) is that it's confusing to > represent the VR_RANGE [-128, 127] of the signed char variable as a > VR_ANTI_RANGE

[Bug tree-optimization/77899] incorrect VR_RANGE for a signed char function argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77899 Martin Sebor changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[PATCH] Minor simplification to std::_Bind_result helpers

We don't need to define new class templates for the SFINAE helpers in _Bind_result, we can just use alias templates. This also moves where the helpers are used to the return types, instead of as a defaulted argument. * include/std/functional (_Bind_result::__enable_if_void): Use alias

Re: [PATCH] Improve performance of list::reverse

On 09/10/16 16:23 +0100, Elliot Goodrich wrote: Hi, If we unroll the loop so that we iterate both forwards and backwards, we can take advantage of memory-level parallelism when chasing pointers. This means that reverse takes 35% less time when nodes are randomly scattered in memory and about

[Bug target/77904] [ARM Cortex-M0] Frame pointer thrashes registers if assembly statements with "sp" clobber are used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77904 Thomas Preud'homme changed: What|Removed |Added Last reconfirmed||2016-10-10 CC|

  1   2   3   >