Re: C++ xgcc for arm-none-eabi fails in 7.1, 7.2 due to undefined identifiers

On Fri, 2017-08-18 at 11:17 -0500, R0b0t1 wrote: > Just to check, this is actually an > arm-none-eabi toolchain? I looked over the compilation flags and it > looks like it supports all Cortex-M processor features like such a > toolchain should. Most instructions I could find seemed to build a >

Re: Locating a commit from its ChangeLog entry (was Re: How to migrate ggc_alloc_XXX for GCC v8.x (git-20170816)?)

Hi, My first question would be why are you using the ChangeLog files at all? It seems like it would be a lot more straight forward to just look at blame for the thing that changed. thanks Trev On Fri, Aug 18, 2017 at 09:32:34AM +0800, Leslie Zhai wrote: > > > 在 2017年08月17日 23:10, David

Re: C++ xgcc for arm-none-eabi fails in 7.1, 7.2 due to undefined identifiers

R0b0t1 kirjoitti 18.8.2017 klo 19:17: On Fri, Aug 18, 2017 at 1:09 AM, Freddie Chopin wrote: On Thu, 2017-08-17 at 22:27 -0500, R0b0t1 wrote: On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 wrote: When compiling libssp, ssp.c, function __guard_setup: O_RDONLY

Re: Overwhelmed by GCC frustration

On Thu, Aug 17, 2017 at 05:22:34PM +, paul.kon...@dell.com wrote: > I think G-J said "... LRA focusses just comfortable, orthogonal targets" > which is not quite the same thing. > > I'm a bit curious about that, since x86 is hardly "comfortable orthogonal". > But if LRA is targeted only

Re: C++ xgcc for arm-none-eabi fails in 7.1, 7.2 due to undefined identifiers

On Thu, 2017-08-17 at 22:27 -0500, R0b0t1 wrote: > On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 wrote: > > When compiling libssp, ssp.c, function __guard_setup: > > O_RDONLY is undeclared (ssp.c:93:34), > > ssize_t is an unknown type name (ssp.c:96:7), and > > size_t is an unknown

Re: C++ xgcc for arm-none-eabi fails in 7.1, 7.2 due to undefined identifiers

I forgot to say, that the procedure and resulting toolchain is closely modeled after the one provided by ARM on: https://developer.arm.com/open-source/gnu-toolchain/gnu-rm It just has couple of tweaks like slightly different options for newlib, completely disabled C++ exceptions and uses the

Re: Bit-field struct member sign extension pattern results in redundant

On Fri, Aug 18, 2017 at 10:29:04AM +1200, Michael Clark wrote: > Sorry I had to send again as my Apple mailer is munging emails. I’ve disabled > RTF. > > > This one is quite interesting: > > - https://cx.rv8.io/g/WXWMTG > > It’s another target independent bug. x86 is using some LEA followed

Re: Bit-field struct member sign extension pattern results in redundant

> On 18 Aug 2017, at 10:41 PM, Gabriel Paubert wrote: > > On Fri, Aug 18, 2017 at 10:29:04AM +1200, Michael Clark wrote: >> Sorry I had to send again as my Apple mailer is munging emails. I’ve >> disabled RTF. >> >> >> This one is quite interesting: >> >> -

Re: Bit-field struct member sign extension pattern results in redundant

> On 18 Aug 2017, at 10:56 PM, Michael Clark wrote: > >> >> On 18 Aug 2017, at 10:41 PM, Gabriel Paubert wrote: >> >> On Fri, Aug 18, 2017 at 10:29:04AM +1200, Michael Clark wrote: >>> Sorry I had to send again as my Apple mailer is munging emails.

Re: Bit-field struct member sign extension pattern results in redundant

On Fri, 2017-08-18 at 10:29 +1200, Michael Clark wrote: >  > This one is quite interesting: > > - https://cx.rv8.io/g/WXWMTG > > It’s another target independent bug. x86 is using some LEA followed > by SAR trick with a 3 bit shift. Surely SHL 27, SAR 27 would suffice. > In any case RISC-V seems

Re: Optimization breaks inline asm code w/ptrs

On 8/14/17, Alan Modra wrote: > On Sun, Aug 13, 2017 at 10:25:14PM +0930, Alan Modra wrote: >> On Sun, Aug 13, 2017 at 03:35:15AM -0700, David Wohlferd wrote: >> > Using "m"(*pStr) as an (unused) input parameter has no effect. >> >> Use "m" (*(const void *)pStr) and ignore the

[OT] Re: Bit-field struct member sign extension pattern results in redundant

On Fri, Aug 18, 2017 at 10:56:10PM +1200, Michael Clark wrote: > > > On 18 Aug 2017, at 10:41 PM, Gabriel Paubert wrote: > > > > On Fri, Aug 18, 2017 at 10:29:04AM +1200, Michael Clark wrote: > >> Sorry I had to send again as my Apple mailer is munging emails. I’ve > >>

Re: Bit-field struct member sign extension pattern results in redundant

On 08/17/2017 03:29 PM, Michael Clark wrote: > hand coded x86 asm (no worse because the sar depends on the lea) > > sx5(int): > shl edi, 27 > sar edi, 27 > movsx eax, dl Typo in the register, but I know what you mean. More interestingly, edi already has the

Re: C++ xgcc for arm-none-eabi fails in 7.1, 7.2 due to undefined identifiers

On Fri, Aug 18, 2017 at 1:09 AM, Freddie Chopin wrote: > On Thu, 2017-08-17 at 22:27 -0500, R0b0t1 wrote: >> On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 wrote: >> > When compiling libssp, ssp.c, function __guard_setup: >> > O_RDONLY is undeclared

[Bug libstdc++/81891] [5/6/7/8 Regression] heap-use-after-free if inserting element in std::unordered_map(InputIt, InputIt) throws

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81891 Jonathan Wakely changed: What|Removed |Added CC||fdumont at gcc dot gnu.org ---

[Bug c++/52130] missing check for matching underlying type during instantiation of enum member of class template

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52130 --- Comment #3 from Richard Smith --- The diagnostic in #1 is not only wrong for this case, it's also a rejects-valid in the case where the underlying types match. I've filed https://gcc.gnu.org/PR81895 for that.

[PATCH] PR libstdc++/81891 fix double-free in hashtable constructor

We introduced a regression in r214986 when changing the _Hashtable range constructor to delegate to another constructor. That change means that the object has completed construction after the target constructor completes, and so if an exception is thrown in the delegating constructor then the

Re: [PATCH] detect incompatible aliases (PR c/81854)

On 08/18/2017 10:48 AM, Jonathan Wakely wrote: On 18/08/17 08:54 -0600, Martin Sebor wrote: On 08/18/2017 07:10 AM, Jonathan Wakely wrote: On 17/08/17 21:21 -0600, Martin Sebor wrote: Joseph, while looking into implementing enhancement your request pr81824 I noticed that GCC silently accepts

[Bug target/81894] Typo in x86 built-in function list

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

[Bug middle-end/81897] New: spurious -Wmaybe-uninitialized warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81897 Bug ID: 81897 Summary: spurious -Wmaybe-uninitialized warning Product: gcc Version: 7.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/81572] [7/8 Regression] gcc-7 regression: unnecessary vector regmove on compare

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81572 Peter Bergner changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/81891] [5/6/7/8 Regression] heap-use-after-free if inserting element in std::unordered_map(InputIt, InputIt) throws

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81891 --- Comment #3 from Jonathan Wakely --- I think this might be all we need to do to fix it: --- a/libstdc++-v3/include/bits/hashtable.h +++ b/libstdc++-v3/include/bits/hashtable.h @@ -973,17 +973,8 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION

[Bug go/81893] [8 regression] compilation error in libgo starting with r251127

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81893 --- Comment #1 from Ian Lance Taylor --- Did you test powerpc64 little endian?

[Bug c++/81895] New: gcc rejects out-of-line definition of enum member of class template under -pedantic-errors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81895 Bug ID: 81895 Summary: gcc rejects out-of-line definition of enum member of class template under -pedantic-errors Product: gcc Version: 7.2.1 Status: UNCONFIRMED

[Bug c++/50169] "new struct X {{}};" incorrectly treated as an invalid struct-definition

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50169 Ville Voutilainen changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug preprocessor/81794] "would be stringified in traditional C" warning should be controlled by -Wtraditional

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81794 --- Comment #2 from David Malcolm --- Please can you turn it into a patch that contains both the fix *and* the new testcase? (e.g. gcc.dg/pragma-diag-8.c)

[Bug fortran/69834] [OOP] Collision in derived type hashes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69834 Jerry DeLisle changed: What|Removed |Added Status|WAITING |RESOLVED CC|

Re: [PATCH] detect incompatible aliases (PR c/81854)

On 18/08/17 08:54 -0600, Martin Sebor wrote: On 08/18/2017 07:10 AM, Jonathan Wakely wrote: On 17/08/17 21:21 -0600, Martin Sebor wrote: Joseph, while looking into implementing enhancement your request pr81824 I noticed that GCC silently accepts incompatible alias declarations (pr81854) so as

[Bug fortran/79072] ICE with class(*) pointer function result and character value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79072 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org ---

[Bug go/81893] [8 regression] compilation error in libgo starting with r251127

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81893 --- Comment #2 from seurer at gcc dot gnu.org --- Yes, it compiles OK on LE. Note that I saw the errors on both power7 and power8 BE systems and using different versions of gcc to build.

[PATCH/AARCH64] Generate FRINTZ for (double)(long) under -ffast-math on aarch64

Like https://gcc.gnu.org/ml/gcc-patches/2010-09/msg00060.html for PowerPC, we should do something similar for aarch64. This pattern does show up in SPEC CPU 2006 in astar but I did not look into performance improvement of it though. OK? Bootstrapped and tested on aarch64-linux-gnu with no

[Bug c/53037] warn_if_not_aligned(X)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53037 --- Comment #27 from H.J. Lu --- (In reply to Rainer Orth from comment #26) > Several of the new tests FAIL on Solaris/SPARC (both 32 and 64-bit): > > +FAIL: g++.dg/pr53037-2.C -std=gnu++11 (test for warnings, line 16) > +FAIL:

[Bug web/81894] New: Typo in x86 built-in function list

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81894 Bug ID: 81894 Summary: Typo in x86 built-in function list Product: gcc Version: 7.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: web

[Bug c++/80684] poor error message and fix-it hint for a function with an argument of undeclared type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80684 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c/80529] Split "C++ style comments are not allowed in ISO C90" pedwarn into its own warning flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80529 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #5

[Bug fortran/81827] Large compile time with derived-type rrays

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81827 Paul Thomas changed: What|Removed |Added Assignee|rguenth at gcc dot gnu.org |pault at gcc dot gnu.org ---

[PATCH] Simplify allocator usage in unordered containers

While fixing PR 81891 I noticed that _Hashtable always creates a __value_alloc_type for constructing and destroying the elements, which is unnecessary. https://wg21.link/lwg2218 confirmed that. We can avoid constructing new allocators just for these calls and can call them directly on the stored

[Bug fortran/80657] [7/8 Regression] Loop in character function declaration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80657 Paul Thomas changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org ---

[Bug go/81893] [8 regression] compilation error in libgo starting with r251127

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81893 Ian Lance Taylor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/53037] warn_if_not_aligned(X)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53037 --- Comment #29 from H.J. Lu --- (In reply to r...@cebitec.uni-bielefeld.de from comment #28) > > --- Comment #27 from H.J. Lu --- > > > What are error messages? > > None, the warnings are simply missing. > > Rainer Sparc defines

[Bug c/80529] Split "C++ style comments are not allowed in ISO C90" pedwarn into its own warning flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80529 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org ---

[Bug go/81893] [8 regression] compilation error in libgo starting with r251127

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81893 --- Comment #3 from Ian Lance Taylor --- Thanks. I think https://golang.org/cl/57110 should fix the problem.

[Bug c++/81896] New: omp target enter data not recognized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81896 Bug ID: 81896 Summary: omp target enter data not recognized Product: gcc Version: 7.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

Re: std::list optimizations

On 28/07/17 18:42 +0200, François Dumont wrote: Hi Completing execution of the testsuite revealed a bug. So here is the correct version of this patch. François On 21/07/2017 19:14, François Dumont wrote: Hi Here is a proposal for 2 optimizations in the std::list implementation.

[Bug c++/81514] g++.dg/lookup/missing-std-include-2.C FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81514 --- Comment #4 from David Malcolm --- Author: dmalcolm Date: Fri Aug 18 18:12:47 2017 New Revision: 251186 URL: https://gcc.gnu.org/viewcvs?rev=251186=gcc=rev Log: C++: fix ordering of missing std #include suggestion (PR c++/81514)

[Bug c++/81514] g++.dg/lookup/missing-std-include-2.C FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81514 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[PATCH] Fix PR81488

Hi, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81488 reports a problem with SLSR where too many memory resources are required to complete SLSR processing of conditional candidates. The code in question contains large trees of PHI dependencies that must be examined in order to find all

Re: [PATCH], Enable -mfloat128 by default on PowerPC VSX systems

On Wed, Aug 16, 2017 at 06:59:50PM -0400, Michael Meissner wrote: > This patch enables -mfloat128 to be the default on PowerPC Linux VSX systems. > > This patch depends on the libquadmatch/81848 patch being approved and > installed: > https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00977.html That

[Bug libstdc++/81891] [5/6/7/8 Regression] heap-use-after-free if inserting element in std::unordered_map(InputIt, InputIt) throws

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81891 --- Comment #4 from Jonathan Wakely --- Author: redi Date: Fri Aug 18 17:46:57 2017 New Revision: 251185 URL: https://gcc.gnu.org/viewcvs?rev=251185=gcc=rev Log: PR libstdc++/81891 fix double-free in hashtable constructor PR

[Bug fortran/69834] [OOP] Collision in derived type hashes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69834 --- Comment #16 from Paul Thomas --- Dear Jerry, Thanks for your confirmation of my feeling about this. I have enough on my plate as it is! Cheers Paul

[Bug c/53037] warn_if_not_aligned(X)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53037 --- Comment #28 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #27 from H.J. Lu --- > What are error messages? None, the warnings are simply missing. Rainer

libgo patch commited: Don't use little-endian code to dump big-endian PPC regs

According to GCC PR 81893 the code that dumps the registers for PPC only works for little-endian. This patch fixes it to only be used in that case. Bootstrapped on x86_64-pc-linux-gnu, for what that's worth. Committed to mainline. Ian Index: gcc/go/gofrontend/MERGE

[Bug go/81893] [8 regression] compilation error in libgo starting with r251127

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81893 --- Comment #4 from ian at gcc dot gnu.org --- Author: ian Date: Fri Aug 18 20:17:26 2017 New Revision: 251188 URL: https://gcc.gnu.org/viewcvs?rev=251188=gcc=rev Log: PR go/81893 runtime: only use PPC GNU/Linux register code on

[Bug c++/44283] bad error recovery for explicit template instantiation in wrong namespace

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44283 Eric Gallager changed: What|Removed |Added Keywords||error-recovery

Re: Ping on target independent stack clash protection patches

> #01 of #08: > https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01971.html > > #02 of #08: > https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01972.html > > #03 of #08: > https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01974.html > > Need to reach some kind of closure on these, then I can start

[Bug c/53037] warn_if_not_aligned(X)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53037 Rainer Orth changed: What|Removed |Added CC||ro at gcc dot gnu.org --- Comment #26

[Bug libstdc++/81891] [5/6/7/8 Regression] heap-use-after-free if inserting element in std::unordered_map(InputIt, InputIt) throws

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81891 Jonathan Wakely changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug c++/80567] bogus fixit hint for undeclared memset: else

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80567 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug preprocessor/81794] "would be stringified in traditional C" warning should be controlled by -Wtraditional

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81794 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/81891] [5/6/7 Regression] heap-use-after-free if inserting element in std::unordered_map(InputIt, InputIt) throws

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81891 Jonathan Wakely changed: What|Removed |Added Known to work||8.0 Target Milestone|---

[Bug tree-optimization/81488] [8 Regression] gcc goes off the limits allocating memory in gimple-ssa-strength-reduction.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81488 --- Comment #6 from Bill Schmidt --- Patch submitted: https://gcc.gnu.org/ml/gcc-patches/2017-08/msg01145.html

Re: [PATCH, rs6000] Add testcase coverage for vec_sums built-in

On Thu, Aug 17, 2017 at 09:18:54AM -0500, Will Schmidt wrote: > Add some testcase coverage for the vec_sums() built-in. > > Tested across power platforms (p6 and newer). OK for trunk? Okay, thanks! Segher > * gcc.target/powerpc/fold-vec-sums-int.c: New.

Re: [PATCH], Delete some PowerPC debug switches

Hi! On Thu, Aug 17, 2017 at 07:48:54PM -0400, Michael Meissner wrote: > This patch deletes some of the debug switches that I've added over the years, > and now don't use any more. > > I did bootstrap builds and make check runs on a little endian power8 system. > There were no regressions. Can I

[Bug tree-optimization/46805] ICE: SIGSEGV in optab_for_tree_code (optabs.c:407) with -O -fno-tree-scev-cprop -ftree-vectorize

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46805 --- Comment #5 from David Malcolm --- Author: dmalcolm Date: Fri Aug 18 23:56:28 2017 New Revision: 251192 URL: https://gcc.gnu.org/viewcvs?rev=251192=gcc=rev Log: jit: fix segfault with autovectorization (PR tree-optimization/46805) libgccjit

[Bug target/80210] ICE in in extract_insn, at recog.c:2311 on ppc64 for with __builtin_pow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80210 --- Comment #8 from Peter Bergner --- Fixed on trunk. I'm testing backports to the open release branches and will commit them after the trunk patch has aged a bit (next week?).

[Bug tree-optimization/19794] [meta-bug] Jump threading related bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794 Bug 19794 depends on bug 70879, which changed state. Bug 70879 Summary: Missed jump threading opportunity with multiple != conditions https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70879 What|Removed |Added

[Bug middle-end/70879] Missed jump threading opportunity with multiple != conditions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70879 --- Comment #5 from Andrew Macleod --- On 08/18/2017 06:13 PM, law at redhat dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70879 > > Jeffrey A. Law changed: > > What|Removed |Added >

[Bug target/80210] ICE in in extract_insn, at recog.c:2311 on ppc64 for with __builtin_pow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80210 --- Comment #7 from Peter Bergner --- Author: bergner Date: Fri Aug 18 23:41:41 2017 New Revision: 251190 URL: https://gcc.gnu.org/viewcvs?rev=251190=gcc=rev Log: gcc/ PR target/80210 * config/rs6000/rs6000.c

Re: [PATCH, rs6000] 2/3 Add x86 SSE intrinsics to GCC PPC64LE taget

On Thu, Aug 17, 2017 at 08:40:34PM -0500, Steven Munroe wrote: > > > +/* Convert the lower SPFP value to a 32-bit integer according to the > > > current > > > + rounding mode. */ > > > +extern __inline int __attribute__((__gnu_inline__, __always_inline__, > > > __artificial__)) > > >

Re: [PATCH, rs6000] 3/3 Add x86 SSE intrinsics to GCC PPC64LE taget

On Fri, Aug 18, 2017 at 04:49:44PM -0500, Steven Munroe wrote: > On Thu, 2017-08-17 at 00:47 -0500, Segher Boessenkool wrote: > > On Wed, Aug 16, 2017 at 03:50:55PM -0500, Steven Munroe wrote: > > > This it part 3/3 for contributing PPC64LE support for X86 SSE > > > instrisics. This patch includes

Re: [PATCH, rs6000] testcase coverage for vec_perm built-ins

Hi Will, On Thu, Aug 17, 2017 at 09:19:23AM -0500, Will Schmidt wrote: > Add some Testcase coverage for the vector permute intrinsics. > > Tested across power platforms. OK for trunk? > * gcc.target/powerpc/fold-vec-perm-char.c: New. > * gcc.target/powerpc/fold-vec-perm-double.c:

Re: [PATCH, rs6000] Fix PR target/80210: ICE in extract_insn

On Thu, Aug 17, 2017 at 07:02:14PM -0500, Peter Bergner wrote: > PR target/80210 exposes a problem in rs6000_set_current_function() where > is fails to correctly clear the rs6000_previous_fndecl cache correctly. > With the test case, we notice that rs6000_previous_fndecl is set (when it >

[Bug target/81850] [mingw/cygwin] -mabi=sysv ignored

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81850 --- Comment #1 from Daniel Santos --- I have a patch that I've tested and will be submitting it shortly (I can't change the assigned to field yet).

Re: [PATCH, rs6000] Fix PR target/80210: ICE in extract_insn

On 8/18/17 6:27 PM, Segher Boessenkool wrote: > On Thu, Aug 17, 2017 at 07:02:14PM -0500, Peter Bergner wrote: >> This is also broken in GCC 7, GCC 6 and GCC 5. Ok for those after this >> has been on trunk for a little while and assuming testing passes? > > Okay for trunk and all branches.

[Bug c/53037] warn_if_not_aligned(X)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53037 --- Comment #30 from H. Peter Anvin --- On August 18, 2017 3:52:12 PM CDT, "hjl.tools at gmail dot com" wrote: >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53037 > >--- Comment #29 from H.J. Lu --- >(In reply to

[Bug fortran/80164] ICE in gfc_format_decoder at gcc/fortran/error.c:933

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80164 --- Comment #15 from Jerry DeLisle --- Author: jvdelisle Date: Fri Aug 18 21:36:50 2017 New Revision: 251189 URL: https://gcc.gnu.org/viewcvs?rev=251189=gcc=rev Log: 2017-08-18 Jerry DeLisle Backport from

[Bug fortran/80164] ICE in gfc_format_decoder at gcc/fortran/error.c:933

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80164 Jerry DeLisle changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/47413] Constant Propagation and Virtual Function Tables

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47413 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED CC|

[committed] jit: fix segfault with autovectorization (PR tree-optimization/46805)

On Thu, 2017-08-17 at 11:51 -0400, David Malcolm wrote: > On Thu, 2017-08-17 at 09:15 +1200, Michael Cree wrote: > > On Wed, Aug 16, 2017 at 10:01:57AM -0400, David Malcolm wrote: > > > On Wed, 2017-08-16 at 21:58 +1200, Michael Cree wrote: > > > > > > > > But I have hit a problem which I suspect

Re: [PATCH, rs6000] testcase coverage for vec_perm built-ins

On Thu, Aug 17, 2017 at 09:19:17AM -0500, Will Schmidt wrote: > Add testcase coverage for the vec_ld intrinsic builtins. > > Tested across power platforms (p6 and newer). OK for trunk? > * gcc.target/powerpc/fold-vec-ld-char.c: New. > * gcc.target/powerpc/fold-vec-ld-double.c: New. >

Re: [PATCH] Fix fallout from VRP strict-overflow changes

gnu, applied to trunk. This breaks gfortran.dg/alloc_comp_auto_array_2.f90 on aarch64 with -mabi=ilp32 (only for -O3): FAIL: gfortran.dg/alloc_comp_auto_array_2.f90 -O3 -g (test for excess errors) Excess errors: /opt/gcc/gcc-20170818/gcc/testsuite/gfortran.dg/alloc_comp_auto_array

[Bug middle-end/70879] Missed jump threading opportunity with multiple != conditions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70879 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[committed] jit: make simpler reproducers

The C reproducers generated by gcc_jit_context_dump_reproducer_to_file contain numerous pointer values (from %p) to ensure uniqueness of the identifiers, but this makes them less readable than they could be. This patch updates reproducer::make_identifier so that the pointer is only added if it's

[Bug fortran/81898] New: Issue with polymorphic container class

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81898 Bug ID: 81898 Summary: Issue with polymorphic container class Product: gcc Version: 7.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

Re: [PATCH, rs6000] 3/3 Add x86 SSE intrinsics to GCC PPC64LE taget

On Thu, 2017-08-17 at 00:47 -0500, Segher Boessenkool wrote: > On Wed, Aug 16, 2017 at 03:50:55PM -0500, Steven Munroe wrote: > > This it part 3/3 for contributing PPC64LE support for X86 SSE > > instrisics. This patch includes testsuite/gcc.target tests for the > > intrinsics included by

[Bug middle-end/81897] [5.4/6.4/7.2/8 Regression] spurious -Wmaybe-uninitialized warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81897 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Known to work|

[Bug middle-end/64928] [5/6/7/8 Regression] Inordinate cpu time and memory usage in "phase opt and generate" with -ftest-coverage -fprofile-arcs

_64-pc-linux-gnu Configured with: ../../gcc-mainline/configure --prefix=/pkgs/gcc-mainline --enable-checking=release --enable-languages=c --disable-multilib --enable-gather-detailed-mem-stats Thread model: posix gcc version 8.0.0 20170818 (experimental) [trunk revision 251188] (

[PATCH 1/2] c-family/c/c++: pass optional vec to c-format.c

This patch passes along the vec of argument locations at a callsite from the C frontend to check_function_arguments and from there to c-format.c, so that we can underline the pertinent argument to mismatched format codes even for tree codes like decls and constants which lack a location_t for

[PATCH 2/2] C: use full locations within c_parser_expr_list's vec

The previous patch uncovered a bug in how c_parser_expr_list builds the vec: it was only using the location of the first token within each assignment-expression in the expr-list. This shows up in e.g. this -Wformat warning, where only part of the 2nd param is underlined: printf("hello %i",

Re: [PATCH] correct documentation of attribute ifunc (PR 81882)

On Aug 17 2017, Martin Sebor wrote: > -static void (*resolve_memcpy (void)) (void) > +static void* (*resolve_memcpy (void))(void *, const void *, size_t) Please use consistent spacing. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53

[Bug libstdc++/81835] cxxabi.h has invalid link in comment.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81835 --- Comment #4 from Jonathan Wakely --- That should point back to the cxxabi.h file, where you started.

Re: [Libgomp, Fortran] Fix canadian cross build

On 4 August 2017 at 15:52, Yvan Roux wrote: > On 11 July 2017 at 12:25, Yvan Roux wrote: >> On 3 July 2017 at 11:21, Yvan Roux wrote: >>> On 23 June 2017 at 15:44, Yvan Roux wrote: Hello,

[Bug tree-optimization/81884] Invalid code generation with zero size arrays or flexible array members

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81884 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug tree-optimization/81884] [6/7/8 Regression] Invalid code generation with zero size arrays or flexible array members

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81884 Richard Biener changed: What|Removed |Added Keywords||wrong-code Priority|P3

Re: [PATCH v2] Simplify pow with constant

On Thu, Aug 17, 2017 at 5:43 PM, Alexander Monakov wrote: > On Thu, 17 Aug 2017, Wilco Dijkstra wrote: > >> This patch simplifies pow (C, x) into exp (x * C1) if C > 0, C1 = log (C). > > Note this changes the outcome for C == +Inf, x == 0 (pow is specified to > return 1.0 in

[Bug c++/66639] declare __func__ , __FUNCTION__ & __PRETTY_FUNCTION__ as constexpr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66639 --- Comment #11 from Benjamin Buch --- Also test case #3 doesn't work if you declare the function return type auto: constexpr auto foo () { static_assert (0 == __builtin_strcmp (__func__, "foo"), "#1"); static_assert (0 == __builtin_strcmp

[Bug ipa/81877] [7/8 Regression] Incorrect results with lto and -fipa-cp and -fipa-cp-clone

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81877 --- Comment #10 from Richard Biener --- So I think what safelen > 1 (and thus ivdep) guarantees is that (even if the loop doesn't iterate) we can peel any iteration before or after the loop which effectively means all references in one iteration

Re: [PATCH] PR c++/80287 add new testcase

On 4 August 2017 at 15:52, Yvan Roux wrote: > On 13 July 2017 at 14:02, Yvan Roux wrote: >> Hi, >> >> as discussed in the PR, this patch adds a new reduced testcase which >> doesn't rely on c++17 features, this is a prereq to the backport of >> the fix

[Bug libstdc++/81835] cxxabi.h has invalid link in comment.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81835 --- Comment #3 from Chris Johns --- (In reply to Jonathan Wakely from comment #2) > (In reply to Chris Johns from comment #0) > > Tiny issue. > > > > Looking over cxxabi.h I noticed a link in a comment about __cxa_demangle is > > not valid

Add a full_integral_type_p helper function

There are several places that test whether: TYPE_PRECISION (t) == GET_MODE_PRECISION (TYPE_MODE (t)) for some integer type T. With SVE variable-length modes, this would need to become: TYPE_PRECISION (t) == GET_MODE_PRECISION (SCALAR_TYPE_MODE (t)) (or SCALAR_INT_TYPE_MODE, it doesn't

  1   2   3   >