[Bug c/80685] -Wnonnull-compare warns based on builtin declaration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80685 --- Comment #2 from Andrew Pinski --- Use -fno-builtins if you don't want gcc to assumes things about functions.

[Bug c/80685] -Wnonnull-compare warns based on builtin declaration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80685 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/80685] New: -Wnonnull-compare warns based on builtin declaration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80685 Bug ID: 80685 Summary: -Wnonnull-compare warns based on builtin declaration Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug bootstrap/80677] LIMITS_H_TEST is wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80677 --- Comment #2 from Helmut Grohne --- (In reply to jos...@codesourcery.com from comment #1) > Well, if headers move then configure (and related) tests that look at them > will need updating. See how gcc/configure.ac looks in $target_header_dir

[Bug middle-end/80669] [8 Regression] Bad -Wstringop-overflow warnings for stpncpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80669 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #3 from Martin Sebor

[Bug translation/80280] Missing closing quote (%>) c/semantics.c and c/c-typeck.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80280 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug translation/80280] Missing closing quote (%>) c/semantics.c and c/c-typeck.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80280 --- Comment #6 from Martin Sebor --- Author: msebor Date: Tue May 9 02:47:14 2017 New Revision: 247778 URL: https://gcc.gnu.org/viewcvs?rev=247778=gcc=rev Log: PR translation/80280 - Missing closing quote (%>) c/semantics.c and c/c-typeck.c

Re: [PATCH] handle enumerated types in -Wformat-overflow (PR 80397)

On 04/28/2017 12:35 PM, Jeff Law wrote: On 04/26/2017 11:05 AM, Martin Sebor wrote: On 04/24/2017 03:35 PM, Jeff Law wrote: On 04/11/2017 12:57 PM, Martin Sebor wrote: In a review of my fix for bug 80364 Jakub pointed out that to determine whether an argument to an integer directive is of an

[Bug go/64238] ICE in get_partitioning_class, at symtab.c:1775

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64238 --- Comment #4 from Ian Lance Taylor --- This appears to work in GCC 7. At least, I can see a crash when using GCC 6, but I don't see a crash when using revision 246286. Which revision are you using for the crash you see? I'm afraid that I do

[Bug target/80101] ICE in store_data_bypass_p, at recog.c:3737

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80101 --- Comment #2 from kelvin at gcc dot gnu.org --- Author: kelvin Date: Tue May 9 01:15:46 2017 New Revision: 24 URL: https://gcc.gnu.org/viewcvs?rev=24=gcc=rev Log: gcc/testsuite/ChangeLog: 2017-05-08 Kelvin Nilsen

[Bug c++/80684] New: 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 Bug ID: 80684 Summary: poor error message and fix-it hint for a function with an argument of undeclared type Product: gcc Version: 7.0 Status: UNCONFIRMED

[Bug c++/68905] [DR496] __is_trivially_copyable returns True for volatile class types.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68905 Eric Fiselier changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug rtl-optimization/80358] [7 Regression] ICE (cc1 killed) building glib with -O3 on powerpc64le-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80358 --- Comment #4 from acsawdey at gcc dot gnu.org --- Author: acsawdey Date: Tue May 9 00:03:35 2017 New Revision: 247772 URL: https://gcc.gnu.org/viewcvs?rev=247772=gcc=rev Log: 2017-05-08 Aaron Sawdey

[Bug libstdc++/80658] Memory leak reported in libstdc++ (zerotier)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80658 --- Comment #12 from Jonathan Wakely --- (In reply to Bernd Paysan from comment #11) > My guess. He mentions that he's not a lone wolf coder, and since he didn't > understand why mt_allocator was active, I guessed that a coworker had > enabled

Re: [PATCH] xtensa: add support for SSP

On Mon, May 8, 2017 at 4:24 PM, augustine.sterl...@gmail.com wrote: > On Mon, May 8, 2017 at 3:55 PM, Max Filippov wrote: >> gcc/ >> 2017-03-27 Max Filippov >> >> * config/xtensa/xtensa-protos.h >>

[Bug c++/80683] New: Exceptions don't propagate through default member initializer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80683 Bug ID: 80683 Summary: Exceptions don't propagate through default member initializer Product: gcc Version: 6.3.1 Status: UNCONFIRMED Severity: normal

[Bug c++/80682] New: __is_trivially_constructible(void, int) returns true.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80682 Bug ID: 80682 Summary: __is_trivially_constructible(void, int) returns true. Product: gcc Version: 7.0.1 Status: UNCONFIRMED Severity: normal Priority: P3

[RFC] GCC 8 Project proposal: Extensions supporting C Metaprogramming, pseudo-templates

I would like to make some changes in GCC 8, so I thought that formal proposal and RFC would be the best path. I'm still relatively new to the GCC project. I began experimenting with C metaprogramming techniques back in 2012, in order to implement more efficient generic libraries in C. The

Re: [PATCH] xtensa: add support for SSP

On Mon, May 8, 2017 at 3:55 PM, Max Filippov wrote: > gcc/ > 2017-03-27 Max Filippov > > * config/xtensa/xtensa-protos.h > (xtensa_initial_elimination_offset): New declaration. > * config/xtensa/xtensa.c

[Bug libstdc++/80658] Memory leak reported in libstdc++ (zerotier)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80658 --- Comment #11 from Bernd Paysan --- (In reply to Jonathan Wakely from comment #10) > > which he need to disable first > > (after a coworker had enabled it somewhere in the source code): > > Where did you get that information? The blog post

[PATCH] xtensa: add support for SSP

gcc/ 2017-03-27 Max Filippov * config/xtensa/xtensa-protos.h (xtensa_initial_elimination_offset): New declaration. * config/xtensa/xtensa.c (xtensa_initial_elimination_offset): New function. Move its body from the INITIAL_ELIMINATION_OFFSET

[Bug libstdc++/80658] Memory leak reported in libstdc++ (zerotier)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80658 --- Comment #10 from Jonathan Wakely --- (In reply to Bernd Paysan from comment #9) > (In reply to Jonathan Wakely from comment #2) > > "I dropped in jemalloc and ran the test. CPU usage dropped but otherwise > > this had no effect." > > > >

[Bug libstdc++/80658] Memory leak reported in libstdc++ (zerotier)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80658 --- Comment #9 from Bernd Paysan --- (In reply to Jonathan Wakely from comment #2) > "I dropped in jemalloc and ran the test. CPU usage dropped but otherwise > this had no effect." > > i.e. jemalloc was not proposed as a solution. That's the

[Bug c++/80681] New: missing -Wuninitialized for const or reference member of a private base class

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80681 Bug ID: 80681 Summary: missing -Wuninitialized for const or reference member of a private base class Product: gcc Version: 7.0 Status: UNCONFIRMED Severity:

Re: GCC target_clone support (functionality question)

On 05/06/2017 12:44 AM, Richard Sandiford wrote: Michael Meissner writes: This message is separated from the question about moving code, as it is a questions about the functionality of target_clone support. Right now it looks like target_clone only generates the

Re: Question about dump_printf/dump_printf_loc

On 05/05/2017 04:37 PM, Steve Ellcey wrote: I have a simple question about dump_printf and dump_printf_loc. I notice that most (all?) of the uses of these function are of the form: if (dump_enabled_p ()) dump_printf_loc (MSG_*, ..); Since dump_enabled_p() is just

[Bug tree-optimization/80680] New: dead code elimination fails to remove unreferenced function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80680 Bug ID: 80680 Summary: dead code elimination fails to remove unreferenced function Product: gcc Version: 6.3.1 Status: UNCONFIRMED Severity: normal

[PATCH] -fdump option docs

I've committed this to sort the -fdump options. I left the generic -fdump-noaddr, -fdump-unnumbered and -fdump-unnumbered-links at the start. nathan -- Nathan Sidwell 2017-05-08 Nathan Sidwell * doc/invoke.texi: Alphabetize -fdump options. Index: doc/invoke.texi

Re: [PATCH] decl lang hooks

On Mon, 8 May 2017, Nathan Sidwell wrote: > cp/name-lookup has a twisty maze of forwarding functions. One reason is that > a couple of the names are used directly by c-common.c. However, we now have > lang hooks for these things. > > This patch changes the C++ FE to override the pushdecl and

[Bug bootstrap/80677] LIMITS_H_TEST is wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80677 --- Comment #1 from joseph at codesourcery dot com --- On Mon, 8 May 2017, helmut at subdivi dot de wrote: > False negatives: Debian is about to further multiarch. That involves moving > libc headers from /usr/include to

[Patch, Fortran, OOP] PR 79311: ICE in generate_finalization_wrapper, at fortran/class.c:1992

Hi all, the attached patch fixes an ICE-on-valid problem with finalization by making sure that the finalization procedures are properly resolved. In the test case, the finalizer of the component type was not being resolved if the superordinate type had a finalizer itself. The patch also fixes a

[Bug fortran/79930] Potentially Missed Optimisation for MATMUL / DOT_PRODUCT

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79930 --- Comment #15 from Jerry DeLisle --- I wonder if we should back port this as well since the bug can have a serious performance hit without it. ?

[Bug c/80428] Incorrect -Wunused-const-variable= instance

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80428 Tom Rini changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug target/69868] vec_perm built-in is not handled by swap optimization on powerpc64le

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69868 --- Comment #5 from Bill Schmidt --- Author: wschmidt Date: Mon May 8 21:03:45 2017 New Revision: 247759 URL: https://gcc.gnu.org/viewcvs?rev=247759=gcc=rev Log: [gcc] 2016-05-08 Bill Schmidt Backport

Re: [patch, fortran] Reduce stack use in blocked matmul

On 05/08/2017 12:29 PM, Thomas Koenig wrote: > Am 08.05.2017 um 18:58 schrieb Jerry DeLisle: > > he attached patch reduces the stack usage by the blocked >>> version of matmul for cases where we don't need the full buffer. >>> This should improve stack usage. >>> >>> OK for trunk? >>> >> >> OK,

[Bug c++/80679] call of overloaded is ambiguous

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80679 Jonathan Wakely changed: What|Removed |Added Keywords||rejects-valid

[committed] correct %D quoting in gcc/config/sol2-c.c

In preparation for committing the meat of the patch for bug 80280 I've committed the following in r247758 as an obvious fix to prevent the new -Wformat warning from breaking Solaris bootstrap. Bootstrap is currently broken due to 80673 (that looks like a separate issue from the warning). Martin

[Bug translation/80280] Missing closing quote (%>) c/semantics.c and c/c-typeck.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80280 --- Comment #5 from Martin Sebor --- Author: msebor Date: Mon May 8 20:50:24 2017 New Revision: 247758 URL: https://gcc.gnu.org/viewcvs?rev=247758=gcc=rev Log: gcc/ChangeLog: PR translation/80280 * config/sol2-c.c

[Bug c++/80679] New: call of overloaded is ambiguous

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80679 Bug ID: 80679 Summary: call of overloaded is ambiguous Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

Re: [PATCH, v3] Fix PR51513, switch statement with default case containing __builtin_unreachable leads to wild branch

On 05/08/2017 01:20 PM, Peter Bergner wrote: > That is what the previous patch did, but as I mention above, > we generate slightly better code for some test cases (other > tests seemed to generate the same code) if we don't attempt > to handle the decision tree case. I'll note that the current >

Re: [PATCH 2/n] [PR tree-optimization/78496] Simplify ASSERT_EXPRs to facilitate jump threading

On 05/08/2017 09:54 AM, Jeff Law wrote: So I'm not sure if changing VRP with your patches is a good thing when you could have used the new API in the first place ... I don't see that the changes to date around 78496 change things significantly in regards to the immediate plans to remove

Re: [PATCH v4 0/12] [i386] Improve 64-bit Microsoft to System V ABI pro/epilogues

On 05/06/2017 03:22 PM, Daniel Santos wrote: gcc-5.4.0 CFLAGS="-march=native -O2 -g": 74 gcc-7.1.0 CFLAGS="-march=native -O2 -g": 74 gcc-7.1.0 CFLAGS="-march=nocona -mtune=generic -O2 -g": 79 gcc-7.1.0 CFLAGS="-march=native -O2 -g -mcall-ms2sysv-xlogues" (patched): 31 I'm building out a

Re: Backporting Patches to GCC 7

On 5 May 2017 at 21:35, Palmer Dabbelt wrote: > I just submitted two patches against trunk. I'd like to also have them on the > 7 branch, so when 7.2 comes out we'll have them. These patches only touch the > RISC-V backend, which I'm a maintainer of. Is there a branch maintainer I'm > supposed

Re: [PATCH 1/7] enhance -Wformat to detect quoting problems (PR 80280 et al.)

On 05/05/2017 11:49 AM, Joseph Myers wrote: On Thu, 4 May 2017, Martin Sebor wrote: I like the flags2 idea. I split up the initialization array to also detect quoted %K, and unquoted %R and %r. With that I ran into test failures that took me a bit to debug. It turns out that there's code (a

[Bug libstdc++/80676] basic_stringbuf does not use initial capacity of SSO string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80676 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

Re: [patch, fortran] Reduce stack use in blocked matmul

Am 08.05.2017 um 18:58 schrieb Jerry DeLisle: he attached patch reduces the stack usage by the blocked version of matmul for cases where we don't need the full buffer. This should improve stack usage. OK for trunk? OK, thanks. Is this something we should consider for backporting to gcc-7?

Re: Use "oacc kernels" attribute for OpenACC kernels

Hi! On Thu, 4 Aug 2016 16:07:00 +0200, I wrote: > Ping. > > On Wed, 27 Jul 2016 12:06:59 +0200, I wrote: > > On Mon, 25 Jan 2016 16:09:14 +0100, Jakub Jelinek wrote: > > > On Mon, Jan 25, 2016 at 10:06:50AM -0500, Nathan Sidwell wrote: > > > > On 01/04/16 10:39, Nathan Sidwell

[PATCH] decl lang hooks

cp/name-lookup has a twisty maze of forwarding functions. One reason is that a couple of the names are used directly by c-common.c. However, we now have lang hooks for these things. This patch changes the C++ FE to override the pushdecl and getdecl lang hooks. In addition to simply

[Bug c++/80178] Class with deleted copy and move constructors uses wrong argument passing ABI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80178 --- Comment #4 from Jason Merrill --- Author: jason Date: Mon May 8 19:08:07 2017 New Revision: 247757 URL: https://gcc.gnu.org/viewcvs?rev=247757=gcc=rev Log: PR c++/80178 - parameter passing for uncopyable classes * tree.c

[Bug tree-optimization/80647] vectorized loop crashes from wrongly assuming 16 byte alignment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80647 --- Comment #2 from Yale Zhang --- Very interesting case. First, I didn't know unaligned loads were undefined behavior on x86. ICC 17 doesn't vectorize the loop probably because the destination and source of the memmove() alias. But apparently

C++ PATCH for c++/80178 (ABI of non-copyable class)

Bug 80178 points out that we are doing bitwise copy when passing a class with only deleted copy/move constructors; we should use invisible reference instead. The second patch updates the trunk to use -fabi-version=12 by default for GCC 8. Tested x86_64-pc-linux-gnu, applying to trunk. commit

[Bug other/80678] New: g++.dg/cpp1y/constexpr-79681-2.C fails with ICE starting with r247678

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80678 Bug ID: 80678 Summary: g++.dg/cpp1y/constexpr-79681-2.C fails with ICE starting with r247678 Product: gcc Version: 6.3.1 Status: UNCONFIRMED Severity: normal

[Bug fortran/79930] Potentially Missed Optimisation for MATMUL / DOT_PRODUCT

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79930 --- Comment #14 from Thomas Koenig --- Author: tkoenig Date: Mon May 8 18:22:44 2017 New Revision: 247755 URL: https://gcc.gnu.org/viewcvs?rev=247755=gcc=rev Log: 2017-05-08 Thomas Koenig PR fortran/79930

Re: [PATCH, v3] Fix PR51513, switch statement with default case containing __builtin_unreachable leads to wild branch

On 05/08/2017 12:44 PM, Richard Biener wrote: On Wed, 26 Apr 2017, Peter Bergner wrote: One difference from the last patch is that I am no longer setting default_label to NULL when we emit a decision tree. I noticed that the decision tree code seemed to generate slightly better code for some

[Bug debug/80646] [5/6/7 Regression] wrong type info for extern inline function when compiling Emacs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80646 --- Comment #3 from Paul Eggert --- (In reply to Richard Biener from comment #1) > So I start to belive this is a gdb bug. Thanks, I filed a GDB bug report here: https://sourceware.org/bugzilla/show_bug.cgi?id=21473

[Bug c/80677] New: LIMITS_H_TEST is wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80677 Bug ID: 80677 Summary: LIMITS_H_TEST is wrong Product: gcc Version: 7.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee:

[Bug libstdc++/80676] New: basic_stringbuf does not use initial capacity of SSO string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80676 Bug ID: 80676 Summary: basic_stringbuf does not use initial capacity of SSO string Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: enhancement

[C++ PATCH] function decl pushing

This patch implements a couple of changes. 1) set DECL_ANTICIPATED before pushing an anticipated builtin. My overload management changes will keep the overload list ordered, so needs to know this up front. 2) pushdecl has some funky code to detect when we're trying to push a function decl

[C++ PATCH] pushdecl

This small patch replaces pushdecl_with_scope with a more-specific pushdecl_outermost_localscope. It's used in 2 places to inject an artifical decl into the outermost block scope of a function (__FUNCTION__ var and lambda capture proxies). This moves some binding-level handling into

[Bug libfortran/80602] Reduce stack usage for blocked matmul

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80602 --- Comment #3 from Thomas Koenig --- Author: tkoenig Date: Mon May 8 17:56:13 2017 New Revision: 247753 URL: https://gcc.gnu.org/viewcvs?rev=247753=gcc=rev Log: 2017-05-08 Thomas Koenig PR fortran/80602

Re: [PATCH, v3] Fix PR51513, switch statement with default case containing __builtin_unreachable leads to wild branch

On May 8, 2017 6:41:01 PM GMT+02:00, Peter Bergner wrote: >On 05/03/2017 08:32 AM, Richard Biener wrote: > > As for Bernhards concern I share this -- please intead make the > > interface take either a gimple_seq or a gimple_stmt_iterator > > instead of a basic-block. That

Re: [PATCH 1/2] C++ template type diff printing

On 05/08/2017 12:51 PM, David Malcolm wrote: On Mon, 2017-05-08 at 07:36 -0400, Nathan Sidwell wrote: On 05/04/2017 07:44 PM, David Malcolm wrote: Is '-felide-type' a good name? Wouldn't something like '-fdiagnostic-elide-template-args' be better? Here I'm merely copying clang's option

[PATCH] correct length stpncpy handling in -Wformat-overflow (PR 80669)

The -Wformat-overflow warning newly enhanced in GCC 8.0 to detect reading past the end of the source sequence misinterprets the size argument to stpncpy as a request to read that many bytes from the source sequence, rather than the number of bytes to write. Like strncpy, the function never reads

[Bug middle-end/35412] Correctness with -ftrapv depended on libcall notes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35412 R0b0t1 changed: What|Removed |Added CC||r030t1 at gmail dot com --- Comment #9 from

Re: [PATCH] Don't assume __secure_getenv is available

On 05/07/2017 11:37 PM, Janne Blomqvist via fortran wrote: > PING > > On Thu, Apr 27, 2017 at 9:55 PM, Janne Blomqvist > wrote: >> On Thu, Apr 27, 2017 at 9:50 PM, Janne Blomqvist >> wrote: >> [snip] >> >> And on top of that patch this

[Bug fortran/80668] wrong error message with -finit-derived

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80668 Fritz Reese changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at

[PATCH] Tweak static assertions in std::optional

This simplifies the conditions of some static assertions, using one assertion per condition instead of asserting the conjunction. This means we don't need any string literal, because the conditions are quite readable now. * include/std/optional: Use a separate static_assert per

[Bug libstdc++/80675] New: Incorrect implementation of LWG 2534

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80675 Bug ID: 80675 Summary: Incorrect implementation of LWG 2534 Product: gcc Version: 8.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3

[Bug libfortran/51119] MATMUL slow for large matrices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119 Bug 51119 depends on bug 68600, which changed state. Bug 68600 Summary: Inlined MATMUL is too slow. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68600 What|Removed |Added

[Bug fortran/37131] inline matmul for small matrix sizes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37131 Bug 37131 depends on bug 68600, which changed state. Bug 68600 Summary: Inlined MATMUL is too slow. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68600 What|Removed |Added

[Bug fortran/68600] Inlined MATMUL is too slow.

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

[PATCH v2,rs6000] Add built-in function support for compare bytes instruction

This patch adds support for the compare bytes instruction, which has been available in the rs6000 architecture since Power6. Thank you to Segher Boessenkool for feedback on the original submission of this patch. The following refinements have been incorporated: 1. Changed the implementation

Re: Test cases to check OpenACC offloaded function's attributes and classification

Hi! Ping. On Thu, 4 Aug 2016 16:06:10 +0200, I wrote: > Ping. > > On Wed, 27 Jul 2016 10:59:02 +0200, I wrote: > > OK for trunk? (In the mean time, I also added some more testing.) commit b7d61270dfc581a6ea130f7a4fa7506a0a5762d8 Author: Thomas Schwinge Date: Mon

Re: [C++ PATCH] namespace bindings

On 05/08/2017 11:17 AM, Andreas Schwab wrote: g++.dg/cpp0x/defaulted34.C has the same problem. I'd managed to flub my xcompiler build. The code path for fn-descriptor-using targets is different, and I'd missed that the shadowed outer 'fn' was expected to have been initialized in that

Re: [patch, fortran] Reduce stack use in blocked matmul

On 05/05/2017 01:31 PM, Thomas Koenig wrote: > Hello world, > > the attached patch reduces the stack usage by the blocked > version of matmul for cases where we don't need the full buffer. > This should improve stack usage. > > Regression-tested. I also added a stress test (around 3 secs of >

[Bug fortran/80674] New: trunk/gcc/fortran/trans-stmt.c:2578]: (style) Redundant condition

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80674 Bug ID: 80674 Summary: trunk/gcc/fortran/trans-stmt.c:2578]: (style) Redundant condition Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

Re: [PATCH 1/2] C++ template type diff printing

On Mon, 2017-05-08 at 07:36 -0400, Nathan Sidwell wrote: > On 05/04/2017 07:44 PM, David Malcolm wrote: > > This patch kit implements two new options to make it easier > > to read diagnostics involving mismatched template types: > >-fdiagnostics-show-template-tree and > >-fno-elide-type. >

[Bug target/80672] gcc/config/sh/sh.c:716: prefer compare to find.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80672 --- Comment #1 from David Binderman --- Unrelated issue in the same file: trunk/gcc/config/sh/sh.c:10817]: (style) Expression is always false because 'else if' condition matches previous condition at line 10803. else if (scratch0 !=

[Bug bootstrap/80673] New: sparcv9-solaris2.11 bootstrap error: cannot convert ‘format_std_version {enum}’ to ‘const char*’ in initialization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80673 Bug ID: 80673 Summary: sparcv9-solaris2.11 bootstrap error: cannot convert ‘format_std_version {enum}’ to ‘const char*’ in initialization Product: gcc Version:

[Bug libstdc++/80624] char_traits::eof() doesn't meet requirements

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80624 --- Comment #1 from Jonathan Wakely --- Some more examples of misbehaviour caused by eof() being a valid character: #include #include int main() { std::basic_ostringstream s; s.put(u'\u'); assert( s.str().length() == 1 ); } a.out:

[Bug target/80672] New: gcc/config/sh/sh.c:716: prefer compare to find.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80672 Bug ID: 80672 Summary: gcc/config/sh/sh.c:716: prefer compare to find. Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [PATCH, v3] Fix PR51513, switch statement with default case containing __builtin_unreachable leads to wild branch

On 05/03/2017 08:32 AM, Richard Biener wrote: > As for Bernhards concern I share this -- please intead make the > interface take either a gimple_seq or a gimple_stmt_iterator > instead of a basic-block. That makes it more obvious you > can't use things like gsi_after_labels. Also I think it's

[Bug target/80671] New: config/aarch64/cortex-a57-fma-steering.c:416: bad statement order ?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80671 Bug ID: 80671 Summary: config/aarch64/cortex-a57-fma-steering.c:416: bad statement order ? Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

Re: [PATCH] [PR79542][Ada] Fix ICE in dwarf2out.c with nested func. inlining

On Wed, May 3, 2017 at 3:22 PM, Jason Merrill wrote: > On Tue, Mar 14, 2017 at 8:24 AM, Pierre-Marie de Rodat > wrote: >> Hello, >> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79542 reports an ICE in >> dwarf2out.c for an Ada testcase built with

[Bug c++/80670] Member specialization of alias declaration from different namespace

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80670 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[PATCH 4/4] Vect peeling cost model

gcc/ChangeLog: 2017-05-08 Robin Dapp * tree-vect-data-refs.c (vect_peeling_hash_get_lowest_cost): Remove unused variable. (vect_enhance_data_refs_alignment): Compare best peelings costs to doing no peeling and choose no peeling

[PATCH 3/4] Vect peeling cost model

gcc/ChangeLog: 2017-05-08 Robin Dapp * tree-vect-data-refs.c (vect_peeling_hash_choose_best_peeling): Return peel info. (vect_enhance_data_refs_alignment): Compute full costs when peeling for unknown alignment, compare to costs

Re: [RFC] S/390: Alignment peeling prolog generation

> So the new part is the last point? There's a lot of refactoring in 3/3 that > makes it hard to see what is actually changed ... you need to resist > in doing this, it makes review very hard. The new part is actually spread across the three last "-"s. Attached is a new version of [3/3] split

[Bug fortran/80668] wrong error message with -finit-derived

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80668 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/80670] New: Member specialization of alias declaration from different namespace

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80670 Bug ID: 80670 Summary: Member specialization of alias declaration from different namespace Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

Re: [PATCH 1/4][PR tree-optimization/78496] Don't simplify conditionals too early in VRP

On 05/08/2017 01:32 AM, Richard Biener wrote: Note that I tried last stage3 (it ended up being too late) to get rid of ASSERT_EXPRs doing substitute-and-fold itself (basically copy-propagate them out at this point rather than as a separate thing later). This is because the ASSERT_EXPR uses

Re: [PATCH 2/n] [PR tree-optimization/78496] Simplify ASSERT_EXPRs to facilitate jump threading

On 05/08/2017 01:25 AM, Richard Biener via gcc-patches wrote: ps. An astute observer might note that improving the effectiveness of VRP jump threading seems counterproductive since I've stated I want to remove VRP jump threading. These improvements don't significantly change how I was

Re: [C++ PATCH] namespace bindings

On 05/08/2017 08:56 AM, Jason Merrill wrote: On Fri, May 5, 2017 at 4:07 PM, Nathan Sidwell wrote: This cleanup patch kills IDENTIFIER_NAMESPACE_VALUE and replaces {get,set}_namespace_binding with get_namespace_value and set_global_value respectively. I'd prefer to stick with

[Bug fortran/80666] character length parameter fails if declaration order incorrect

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80666 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

Re: [PATCH, RFC] warn about raw pointers that can be unique_ptr

Note that the new option will need documenting in invoke.texi for any patch version actually proposed for inclusion. -- Joseph S. Myers jos...@codesourcery.com

[CHKP] Attempt to fix PR79765 (multiversioning and instrumentation)

Hi, I'm trying to fix the problem with function multiversioning and MPX instrumentation (PR79765) and I face several issues. I would appreciate your advice: The first problem that arises is that multiversioning tries to make versions out of thunks, which do not have bodies. This is fixed with

MinGW compilation warnings in libiberty's xstrndup.c

When compiling libiberty (as part of GDB) with MinGW on MS-Windows, I see the following warning: gcc -c -DHAVE_CONFIG_H -O2 -gdwarf-4 -g3 -D__USE_MINGW_ACCESS -I. -I./../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic -D_GNU_SOURCE ./xstrndup.c -o xstrndup.o

MinGW compilation warnings in libiberty's waitpid.c

When compiling libiberty (as part of GDB) with MinGW on MS-Windows, I see the following warning: gcc -c -DHAVE_CONFIG_H -O2 -gdwarf-4 -g3 -D__USE_MINGW_ACCESS -I. -I./../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic -D_GNU_SOURCE ./waitpid.c -o waitpid.o

MinGW compilation warnings in libiberty's include/environ.h

When compiling libiberty (as part of GDB) with MinGW on MS-Windows, I see the following warning: gcc -c -DHAVE_CONFIG_H -O2 -gdwarf-4 -g3 -D__USE_MINGW_ACCESS -I. -I./../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic -D_GNU_SOURCE ./setenv.c -o setenv.o

[Bug middle-end/80669] [8 Regression] Bad -Wstringop-overflow warnings for stpncpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80669 Martin Sebor changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

  1   2   3   >