Re: [RFC][PR64946] "abs" vectorization fails for char/short types

Hi Richard, Thanks for the review. I am revising the patch based on Andrew's comments too. On 17 May 2018 at 20:36, Richard Biener wrote: > On Thu, May 17, 2018 at 4:56 AM Andrew Pinski wrote: > >> On Wed, May 16, 2018 at 7:14 PM, Kugan

[Bug middle-end/85602] -Wsizeof-pointer-memaccess for strncat with size of source

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

[PATCH] refine -Wstringop-truncation and -Wsizeof-pointer-memaccess for strncat of nonstrings (PR 85602)

The -Wstringop-truncation and -Wsizeof-pointer-memaccess warnings I added and enhanced, respectively, in GCC 8 are arguably overly strict for source arguments declared with the nonstring attribute. For example, -Wsizeof-pointer-memaccess triggers for the strncat call below: __attribute__

Re: [C++ Patch] PR 84588 ("[8 Regression] internal compiler error: Segmentation fault (contains_struct_check())")​ (Take 2)

Hi again, On 18/05/2018 02:31, Paolo Carlini wrote: Hi, On 18/05/2018 01:21, Jason Merrill wrote: On Thu, May 17, 2018 at 5:54 PM, Paolo Carlini wrote: On 17/05/2018 16:58, Jason Merrill wrote: On Thu, May 17, 2018 at 10:27 AM, Paolo Carlini

Re: [C++ Patch] PR 84588 ("[8 Regression] internal compiler error: Segmentation fault (contains_struct_check())")​ (Take 2)

Hi, On 18/05/2018 01:21, Jason Merrill wrote: On Thu, May 17, 2018 at 5:54 PM, Paolo Carlini wrote: On 17/05/2018 16:58, Jason Merrill wrote: On Thu, May 17, 2018 at 10:27 AM, Paolo Carlini wrote: PS: maybe better using

Re: [PATCH] use string length to relax -Wstringop-overflow for nonstrings (PR 85623)

Ping: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00509.html On 05/10/2018 01:26 PM, Martin Sebor wrote: GCC 8.1 warns for unbounded (and some bounded) string comparisons involving arrays declared attribute nonstring (i.e., char arrays that need not be nul-terminated). For instance:

libcpp PATCH to avoid deprecated copy assignment

Another case of assignment from a value-initialized temporary, which in this case ought to be placement new. Tested x86_64-pc-linux-gnu, applying to trunk. commit ccd4031ebdabf02fe0d54bb43a68c0fa72ec2708 Author: Jason Merrill Date: Thu May 17 17:16:28 2018 -0400

Re: [C++ Patch] PR 84588 ("[8 Regression] internal compiler error: Segmentation fault (contains_struct_check())")​ (Take 2)

On Thu, May 17, 2018 at 5:54 PM, Paolo Carlini wrote: > On 17/05/2018 16:58, Jason Merrill wrote: >> >> On Thu, May 17, 2018 at 10:27 AM, Paolo Carlini >> wrote: >>> >>> PS: maybe better using function_declarator_p? >> >> I think so, yes. The

[Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822 --- Comment #3 from Yuri Gribov --- It seems these lines in is_masked_range_test should be removed: if (wi::neg_p (val, TYPE_SIGN (type))) std::swap (*low, *high); Sadly there were no tests which tested negative constants. I'll bootstrap

[Bug target/85492] riscv64: endless loop when throwing an exception from a constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85492 --- Comment #10 from Andrew Waterman --- Thanks for the suggestion. Let's go with the CFI-directive approach. On Sat, Apr 28, 2018 at 5:45 AM, aurelien at aurel32 dot net wrote: >

[Bug c++/85825] New: Incorrect selection of method in template class specialization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85825 Bug ID: 85825 Summary: Incorrect selection of method in template class specialization. Product: gcc Version: 7.3.0 Status: UNCONFIRMED Severity: normal

Re: [PATCH 2/2, RISC-V] Optimize switch with sign-extended index.

On Wed, May 2, 2018 at 3:05 PM, Jim Wilson wrote:> > * config/riscv/riscv.c (riscv_extend_comparands): In unsigned QImode > test, check for sign extended subreg and/or constant operands, and > do a sign extend in that case. > > gcc/testsuite/ >

Re: [PATCH 1/2, expr.c] Optimize switch with sign-extended index.

On Thu, May 17, 2018 at 12:25 AM, Eric Botcazou wrote: > The patch looks OK to me, modulo: > >> + && ! (INTVAL (range) & (HOST_WIDE_INT_1U << (width - 1 > > I'd use UINTVAL instead of INTVAL here. Thanks. Committed with that change. Jim

gcc-7-20180517 is now available

Snapshot gcc-7-20180517 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20180517/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7

[Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris SPARC when parsing a simple character class

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

[Bug c++/80485] rejects-valid: constexpr static_cast of pointer-to-member-function to bool

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

[Bug c++/80485] rejects-valid: constexpr static_cast of pointer-to-member-function to bool

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

[Bug c++/85823] Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression

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

Re: [C++ Patch] PR 84588 ("[8 Regression] internal compiler error: Segmentation fault (contains_struct_check())")​ (Take 2)

Hi, On 17/05/2018 16:58, Jason Merrill wrote: On Thu, May 17, 2018 at 10:27 AM, Paolo Carlini wrote: PS: maybe better using function_declarator_p? I think so, yes. The relevant rule seems to be "The declarator shall not specify a function or an array.", so let's

[Bug tree-optimization/85803] [6/7/8/9 Regression] DSE removes live global store

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

[Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |8.2

Re: [Patch] Do not call the linker if we are creating precompiled header files

Ping. Steve Ellcey sell...@cavium.com On Wed, 2018-05-02 at 12:47 -0700, Steve Ellcey wrote: > This is a new version of a patch I sent out last year to stop gcc from > trying to do a link when creating precompiled headers and a linker > flag is also given. > > When I build and test GCC I also

Re: [PATCH , rs6000] Add missing builtin test cases, fix arguments to match specifications.

On Thu, 2018-05-17 at 15:31 -0500, Segher Boessenkool wrote: > Hi! > > On Wed, May 16, 2018 at 12:53:13PM -0700, Carl Love wrote: > > diff --git a/gcc/testsuite/gcc.target/powerpc/altivec-12.c > > b/gcc/testsuite/gcc.target/powerpc/altivec-12.c > > index b0267b5..1f3175f 100644 > > ---

[Bug c++/85823] Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823 --- Comment #2 from Andrew Pinski --- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80485

[Bug fortran/78797] It is time perhaps to implement -std=f2015

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797 janus at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

Re: Auto-generated .rodata contents and __attribute__((section))

On Thu, May 17, 2018 at 06:10:13PM +0200, Michael Matz wrote: > On Wed, 16 May 2018, Richard Biener wrote: > > > Are constant pool entries merged at compile time or at link time? I > > > would presume it should be done at link time because otherwise you're > > > only merging entries within a

[Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822 Yuri Gribov changed: What|Removed |Added CC||tetra2005 at gmail dot com --- Comment #2

Re: [PATCH , rs6000] Add missing builtin test cases, fix arguments to match specifications.

On 5/17/18 3:31 PM, Segher Boessenkool wrote: > On Wed, May 16, 2018 at 12:53:13PM -0700, Carl Love wrote: >> @@ -27,21 +27,21 @@ >> /* { dg-final { scan-assembler-times "vmulosb" 1 } } */ >> >> // For LE platforms P9 and later, we generate the lxv insn instead of >> lxvd2x. >> -/* { dg-final

[Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris-sparc when parsing a simple character class

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824 --- Comment #2 from Wanying Luo --- (In reply to Wanying Luo from comment #0) > When I ran this test on a Linux machine with GCC 4.9.2, glibc's strxfrm() > converts 0x80 to 6 bytes. Pasting my test on Linux with the same version of GCC for

Business intelligence of Accounting Software

Hello, Would you be interested in acquiring newly released Accounting Software Contact Information? Our entire list comes with complete contact information including direct phone numbers and emails. We also have other specialist such as: Ø QuickBooks Software Users Ø Financial

[Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris-sparc when parsing a simple character class

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824 --- Comment #1 from Wanying Luo --- Here's GDB backtrace at the time of crash. #0 0xf56fe7a0 in __lwp_sigqueue () from /lib/libc.so.1 #1 0xf56a1e90 in raise () from /lib/libc.so.1 #2 0xf567a274 in abort () from /lib/libc.so.1 #3 0xff2f2d70

Re: [PATCH , rs6000] Add missing builtin test cases, fix arguments to match specifications.

Hi! On Wed, May 16, 2018 at 12:53:13PM -0700, Carl Love wrote: > diff --git a/gcc/testsuite/gcc.target/powerpc/altivec-12.c > b/gcc/testsuite/gcc.target/powerpc/altivec-12.c > index b0267b5..1f3175f 100644 > --- a/gcc/testsuite/gcc.target/powerpc/altivec-12.c > +++

[Bug libstdc++/85824] New: regex constructor crashes under UTF-8 locale on Solaris-sparc when parsing a simple character class

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824 Bug ID: 85824 Summary: regex constructor crashes under UTF-8 locale on Solaris-sparc when parsing a simple character class Product: gcc Version: 4.9.2 Status:

[Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814 rsandifo at gcc dot gnu.org changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822 --- Comment #1 from Marc Glisse --- _2 = x.0_1 & -281474976710656; if (_2 == -281474976710656) goto ; [20.24%] [...] x.0_11 = ASSERT_EXPR ; x.0_12 = ASSERT_EXPR

[Bug lto/82229] GCC7's LTO underperforms compared to GCC6

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82229 --- Comment #28 from krzysio.kurek at wp dot pl --- I mean the relative performance is worse but still Profiled GCC6 is faster than GCC 7 or GCC 8.

[Bug c++/85823] Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823 Marek Polacek changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/85823] New: Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823 Bug ID: 85823 Summary: Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression Product: gcc Version: 8.1.1

Cybersecurity Software Users Contact List

Hi, Hope you having a great day! I just wanted to be aware if you would be interested in acquiring Cybersecurity Software Users Contact List for marketing your product or service. These are the fields that we provide for each contacts: Names, Title, Email, Contact Number, Company Name,

Re: [PATCH][AArch64] Unify vec_set patterns, support floating-point vector modes properly

On Thu, May 17, 2018 at 09:26:37AM -0500, Kyrill Tkachov wrote: > > On 17/05/18 14:56, Kyrill Tkachov wrote: > > > > On 17/05/18 09:46, Kyrill Tkachov wrote: > >> > >> On 15/05/18 18:56, Richard Sandiford wrote: > >>> Kyrill Tkachov writes: > Hi all, > >

Re: Are the extended algorithms in the header file going to be supported by gcc ?

There is work ongoing to complete C++17 support in libstdc++, this includes providing support for the C++17 parallel algorithms. Marco Ippolito writes: > Hi, > > the good book "C++17 STL Cookbook" in chapter 9 "Parallelism and > Concurrency" describes some of the 69 algorithms that were

Re: [PATCH rs6000] Fix PR85698

On Thu, May 17, 2018 at 07:58:20PM +0200, Richard Biener wrote: > On May 17, 2018 6:04:36 PM GMT+02:00, Segher Boessenkool > wrote: > >On Thu, May 17, 2018 at 10:42:46AM -0500, Pat Haugen wrote: > >> The following patch fixes a problem that resulted in incorrect code

[Bug ipa/85817] [9 Regression] ICE in expand_call at gcc/calls.c:4291

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817 H.J. Lu changed: What|Removed |Added CC||hjl.tools at gmail dot com --- Comment #3

[Bug tree-optimization/85820] [9 Regression] internal compiler error: Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820 H.J. Lu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150

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

[Bug tree-optimization/85822] New: [8/9 Regression] Maybe wrong code in VRP since r249150

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822 Bug ID: 85822 Summary: [8/9 Regression] Maybe wrong code in VRP since r249150 Product: gcc Version: unknown Status: UNCONFIRMED Keywords: wrong-code Severity: normal

Documentation patch for -floop-interchange and -floop-unroll-and-jam.

The documentation of both options is still inconsistent, in both the trunk and the gcc-8 branch. The following is my suggestion to clear this up (and move -floop-unroll-and-jam close to -floop-interchange. ChangeLog: 2018-05-17 Toon Moene * doc/invoke.texi: Move

[Bug tree-optimization/78969] bogus snprintf truncation warning due to missing range info

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

Are the extended algorithms in the header file going to be supported by gcc ?

Hi, the good book "C++17 STL Cookbook" in chapter 9 "Parallelism and Concurrency" describes some of the 69 algorithms that were extended to accept execution policies in order to run parallel on multiple cores. And, according to the provided examples, they all greatly simplify some aspects of

Re: [PATCH rs6000] Fix PR85698

On May 17, 2018 6:04:36 PM GMT+02:00, Segher Boessenkool wrote: >On Thu, May 17, 2018 at 10:42:46AM -0500, Pat Haugen wrote: >> The following patch fixes a problem that resulted in incorrect code >generation for the CPU2017 benchmark 525.x264_r. The fix correctly

[Bug middle-end/41475] common variables cannot be expected to be aligned

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41475 Andrey Tarasevich changed: What|Removed |Added CC||atarasevich at comcast dot net ---

Re: PING^1: [PATCH] C/C++: Add -Waddress-of-packed-member

On Mon, May 14, 2018 at 8:00 PM, Martin Sebor wrote: > On 05/14/2018 01:10 PM, H.J. Lu wrote: >> >> On Mon, May 14, 2018 at 10:40 AM, H.J. Lu wrote: >> >> $ cat c.i >> struct B { int i; }; >> struct C { struct B b; } __attribute__ ((packed));

[Bug libstdc++/85812] [7/8 Regression] make_exception_ptr can leak the allocated exception if construction throws

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

[Bug libstdc++/85812] [7/8 Regression] make_exception_ptr can leak the allocated exception if construction throws

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812 --- Comment #5 from Jonathan Wakely --- Author: redi Date: Thu May 17 17:26:44 2018 New Revision: 260331 URL: https://gcc.gnu.org/viewcvs?rev=260331=gcc=rev Log: PR libstdc++/85812 fix memory leak in std::make_exception_ptr PR

[Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'

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

[Bug libstdc++/85821] Chrono literal operators do not follow the standard declarataions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85821 --- Comment #1 from Jonathan Wakely --- The simple answer is of course "don't do that". Writing 1s works fine, or if you want to be explicit, std::chrono::seconds(1).

[Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813 --- Comment #8 from Jonathan Wakely --- (In reply to Mathias Stearn from comment #7) > > Simply returning an empty exception_ptr is what happened before the PR 64241 > > change, so what we do now retains that behaviour. That might be the main >

[Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813 --- Comment #7 from Mathias Stearn --- > Simply returning an empty exception_ptr is what happened before the PR 64241 > change, so what we do now retains that behaviour. That might be the main > reason for it. Silently dropping errors always

[Bug libstdc++/85821] New: Chrono literal operators do not follow the standard declarataions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85821 Bug ID: 85821 Summary: Chrono literal operators do not follow the standard declarataions Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal

[Bug c++/85763] Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763 --- Comment #3 from Jonathan Wakely --- OK thanks for following up.

[Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions

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

[Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813 --- Comment #5 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #4) > (In reply to Mathias Stearn from comment #3) > > My assumption was that if E(...) throws and it can't be caught, it should be > > treated as any other case

[Bug tree-optimization/85820] [9 Regression] internal compiler error: Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820 --- Comment #1 from prathamesh3492 at gcc dot gnu.org --- This is most likely dup of PR85817. Could you check if the fix in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817#c1 works ? Thanks, Prathamesh

[Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813 --- Comment #4 from Jonathan Wakely --- (In reply to Mathias Stearn from comment #3) > My assumption was that if E(...) throws and it can't be caught, it should be > treated as any other case when an -fno-exceptions TU calls a throwing >

Re: So what's the status of the Git migration?

Richard Earnshaw (lists) : > Another year; another release; and still no sign of progress on the git > migration. > > Any ideas on how much longer this is going to take? > > R. I'm still working on it. It's a slow process because the repo is so huge that full

[Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698 Pat Haugen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

Re: PR83648

On Mon, May 14, 2018 at 11:11 PM, Prathamesh Kulkarni wrote: > On 12 January 2018 at 18:26, Richard Biener wrote: >> On Fri, 12 Jan 2018, Prathamesh Kulkarni wrote: >> >>> On 12 January 2018 at 05:02, Jeff Law wrote: >>> > On

[Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698 --- Comment #9 from Pat Haugen --- Author: pthaugen Date: Thu May 17 16:19:16 2018 New Revision: 260329 URL: https://gcc.gnu.org/viewcvs?rev=260329=gcc=rev Log: PR target/85698 * config/rs6000/rs6000.c

[Bug tree-optimization/85820] New: [9 Regression] internal compiler error: Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820 Bug ID: 85820 Summary: [9 Regression] internal compiler error: Segmentation fault Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818 --- Comment #2 from Jonathan Wakely --- Author: redi Date: Thu May 17 16:10:26 2018 New Revision: 260328 URL: https://gcc.gnu.org/viewcvs?rev=260328=gcc=rev Log: PR libstdc++/85818 ensure path::preferred_separator is defined Because path.cc is

[Bug libstdc++/85812] [7/8 Regression] make_exception_ptr can leak the allocated exception if construction throws

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812 --- Comment #3 from Jonathan Wakely --- Author: redi Date: Thu May 17 16:10:20 2018 New Revision: 260327 URL: https://gcc.gnu.org/viewcvs?rev=260327=gcc=rev Log: PR libstdc++/85812 fix memory leak in std::make_exception_ptr PR

Re: Auto-generated .rodata contents and __attribute__((section))

Hi, On Wed, 16 May 2018, Richard Biener wrote: > > Are constant pool entries merged at compile time or at link time? I > > would presume it should be done at link time because otherwise you're > > only merging entries within a single compilation unit (which doesn't > > sound that useful in a

Re: [PATCH rs6000] Fix PR85698

On Thu, May 17, 2018 at 10:42:46AM -0500, Pat Haugen wrote: > The following patch fixes a problem that resulted in incorrect code > generation for the CPU2017 benchmark 525.x264_r. The fix correctly checks the > "dest" operand, which is the memory operand. > > Bootstrap/regtest on powerp64le

[Bug fortran/85816] [8/9 Regression] nested spread fails with "Integer overflow in xmallocarray"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85816 Dominique d'Humieres changed: What|Removed |Added Priority|P3 |P4

Re: [PATCH GCC][4/6]Support regional coalesce and live range computation

On Thu, May 17, 2018 at 3:04 PM, Richard Biener wrote: > On Tue, May 15, 2018 at 5:44 PM Bin.Cheng wrote: > >> On Fri, May 11, 2018 at 1:53 PM, Richard Biener >> wrote: >> > On Fri, May 4, 2018 at 6:23 PM, Bin Cheng

[Bug fortran/82617] Internal compiler error in expand_expr_real_1 when compiling the attached file

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82617 Dominique d'Humieres changed: What|Removed |Added Priority|P3 |P4 CC|

[PATCH rs6000] Fix PR85698

The following patch fixes a problem that resulted in incorrect code generation for the CPU2017 benchmark 525.x264_r. The fix correctly checks the "dest" operand, which is the memory operand. Bootstrap/regtest on powerp64le and powerpc64 (-m32/-m64) with no new regressions. Ok for trunk? -Pat

[Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818 --- Comment #1 from Jonathan Wakely --- Author: redi Date: Thu May 17 15:36:25 2018 New Revision: 260326 URL: https://gcc.gnu.org/viewcvs?rev=260326=gcc=rev Log: PR libstdc++/85818 ensure path::preferred_separator is defined Because path.cc is

[PATCH] PR libstdc++/85818 ensure path::preferred_separator is defined

Because path.cc is compiled with -std=gnu++17 the static constexpr data member is implicitly 'inline' and so no definition gets emitted unless it gets used in that translation unit. Other translation units built as C++11 or C++14 still require a namespace-scope definition of the variable, so mark

[PATCH] PR libstdc++/85812 fix memory leak in std::make_exception_ptr

As the PR points out, the constructor called in the placement new expression can throw, in which case the allocation would be leaked. Separating the two implementations makes it much easier to read what the code is doing. PR libstdc++/85812 * libsupc++/cxxabi_init_exception.h

[Bug fortran/82814] ICE from submodule character function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814 Paul Thomas changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug fortran/82814] ICE from submodule character function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814 --- Comment #7 from Paul Thomas --- Author: pault Date: Thu May 17 15:31:42 2018 New Revision: 260325 URL: https://gcc.gnu.org/viewcvs?rev=260325=gcc=rev Log: 2017-05-17 Paul Thomas PR fortran/82814 *

Re: So what's the status of the Git migration?

On Thu, 17 May 2018, Richard Earnshaw (lists) wrote: > Another year; another release; and still no sign of progress on the git > migration. > > Any ideas on how much longer this is going to take? See git://thyrsus.com/repositories/gcc-conversion.git for the current version of the conversion

Re: [PATCH][AArch64] Unify vec_set patterns, support floating-point vector modes properly

Kyrill Tkachov wrote: > That patch would look like the attached. Is this preferable? > For the above example it generates the desired: > foo_v4sf: >   ldr s0, [x0] >   ldr s1, [x1, 8] >   ins v0.s[1], v1.s[0] >   ld1 {v0.s}[2], [x2] >   ld1 {v0.s}[3], [x3]

[Bug fortran/57160] short-circuit IF only with -ffrontend-optimize

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57160 Dominique d'Humieres changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/85599] Prevent short-circuiting of logical expressions for non-pure functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599 Dominique d'Humieres changed: What|Removed |Added CC||Joost.VandeVondele at mat dot

[Bug fortran/82814] ICE from submodule character function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814 --- Comment #6 from Paul Thomas --- Author: pault Date: Thu May 17 15:17:43 2018 New Revision: 260324 URL: https://gcc.gnu.org/viewcvs?rev=260324=gcc=rev Log: 2017-05-17 Paul Thomas PR fortran/82814 *

[Bug fortran/66694] Failure in function returning an allocated CHARACTER array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694 --- Comment #2 from Dominique d'Humieres --- This PR seems fixed by the patch at https://gcc.gnu.org/ml/fortran/2018-05/msg00046.html, likely a duplicate of pr82923. On darwin the executable hangs due to pr30617.

[Bug c++/85763] Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763 Josh Marshall changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug c++/85763] Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763 --- Comment #2 from Josh Marshall --- Created attachment 44143 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44143=edit Example file I got to making an example, but it seems that this is no longer a problem. I'm going to close this one

Re: Rb_tree constructor optimization

On 15/05/18 07:30 +0200, François Dumont wrote: Here it is again even more simplified. Should I backport the Debug mode fix to 8 branch ? Yes, please do backport the include/debug/* changes.     * include/bits/stl_tree.h     (_Rb_tree_impl(_Rb_tree_impl&&, _Node_allocator&&)): New.    

[Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814 --- Comment #5 from Vittorio Zecca --- I confirm I get the ICE on trunk 260152 and on a sanitized version I also get ../../gcc/gcc/tree-ssa-strlen.c:721:11: runtime error: member access within null pointer of type 'struct strinfo' Thank you

[Bug libstdc++/85812] [7/8/9 Regression] make_exception_ptr can leak the allocated exception if construction throws

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812 --- Comment #2 from Jonathan Wakely --- Author: redi Date: Thu May 17 15:03:29 2018 New Revision: 260323 URL: https://gcc.gnu.org/viewcvs?rev=260323=gcc=rev Log: PR libstdc++/85812 fix memory leak in std::make_exception_ptr PR

[Bug c++/85783] alloc-size-larger-than fires incorrectly with new[] and can't be disabled

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

Re: [C++ Patch] PR 84588 ("[8 Regression] internal compiler error: Segmentation fault (contains_struct_check())")​ (Take 2)

On Thu, May 17, 2018 at 10:27 AM, Paolo Carlini wrote: > PS: maybe better using function_declarator_p? I think so, yes. The relevant rule seems to be "The declarator shall not specify a function or an array.", so let's check for arrays, too. Jason

Re: [PING] [PATCH] Avoid excessive function type casts with splay-trees

On 05/17/18 15:39, Richard Biener wrote: > On Thu, May 17, 2018 at 3:21 PM Bernd Edlinger > wrote: > >> Ping... > > So this makes all traditional users go through the indirect > splay_tree_compare_wrapper > and friends (which is also exported for no good reason?).

Re: [C++ Patch] PR 84588 ("[8 Regression] internal compiler error: Segmentation fault (contains_struct_check())")​ (Take 2)

PS: maybe better using function_declarator_p??? I think I regression tested that variant too, at some point. Paolo.

Re: [PATCH][AArch64] Unify vec_set patterns, support floating-point vector modes properly

On 17/05/18 14:56, Kyrill Tkachov wrote: On 17/05/18 09:46, Kyrill Tkachov wrote: On 15/05/18 18:56, Richard Sandiford wrote: Kyrill Tkachov writes: Hi all, We've a deficiency in our vec_set family of patterns. We don't support directly loading a vector

[Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813 --- Comment #3 from Mathias Stearn --- My assumption was that if E(...) throws and it can't be caught, it should be treated as any other case when an -fno-exceptions TU calls a throwing function. In this case that would mean calling terminate()

[C++ Patch] PR 84588 ("[8 Regression] internal compiler error: Segmentation fault (contains_struct_check())")​ (Take 2)

Hi, thus I had to revert my first try, when it caused c++/85713. I added two testcases for the latter (the second one covering what I learned from yet another defective try which I attached to the trail of c++/84588 yesterday) and finally figured out that the problem was that I was

  1   2   3   >