[Bug middle-end/85704] cc1 run out of memory when it compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85704 --- Comment #3 from Haruue Icymoon --- * More Information Tested the gcc that build with following commands can reproduce this problem. wget https://ftp.gnu.org/gnu/gcc/gcc-8.1.0/gcc-8.1.0.tar.xz tar -Jxf gcc-8.1.0.tar.xz ./configure

[Bug libstdc++/83140] assoc_legendre returns negated value when m is odd

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83140 --- Comment #2 from emsr at gcc dot gnu.org --- The fact that Boost followed us into this makes the situation interesting. We are the only two impls that I know of. I like the std convention slightly better but maybe we should ask for a lib

[Bug middle-end/81478] By default, GCC emits a function call for complex multiplication, should partially inline that

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81478 Ben Woodard changed: What|Removed |Added CC||woodard at redhat dot com --- Comment #7

[Bug c++/85707] -Wclass-memaccess should excempt safe usage inside of a class and its friends

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85707 --- Comment #2 from Mathias Stearn --- Here is a boiled down example of some of our code that trips this warning: https://godbolt.org/g/ChLrch. It also shows why we do this, since the codegen is *substantially* better for init_table_memset than

Re: [C++ PATCH] Fix offsetof constexpr handling (PR c++/85662)

On Tue, May 8, 2018 at 4:04 PM, Jakub Jelinek wrote: > On Tue, May 08, 2018 at 01:03:00PM -0400, Jason Merrill wrote: >> On Sun, May 6, 2018 at 1:56 PM, Jakub Jelinek wrote: >> > --- gcc/c-family/c-common.c.jj 2018-03-27 21:58:55.598502113 +0200 >> > +++

[Bug c++/85708] A corrupt fold expression passed compilation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85708 --- Comment #1 from violetcrestfall at hotmail dot com --- Sorry for typo: GCC 8.0.1 (r259590).

[Bug c++/85707] -Wclass-memaccess should excempt safe usage inside of a class and its friends

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85707 Martin Sebor changed: What|Removed |Added Keywords||diagnostic

[Bug c++/85708] New: A corrupt fold expression passed compilation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85708 Bug ID: 85708 Summary: A corrupt fold expression passed compilation Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/85646] [7/8/9 Regression] Incorrect lambda visibility with -fvisibility=hidden

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

[Bug c++/85646] [7/8/9 Regression] Incorrect lambda visibility with -fvisibility=hidden

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85646 --- Comment #5 from Jason Merrill --- Author: jason Date: Wed May 9 02:34:03 2018 New Revision: 260069 URL: https://gcc.gnu.org/viewcvs?rev=260069=gcc=rev Log: PR c++/85646 - lambda visibility. * decl2.c

[Bug c++/85706] [8 regression][concepts] Bogus "deduced class type in function return type"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85706 Jason Merrill changed: What|Removed |Added Keywords||rejects-valid

[Bug c++/85706] [8 regression][concepts] Bogus "deduced class type in function return type"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85706 --- Comment #2 from Jason Merrill --- Author: jason Date: Wed May 9 02:08:59 2018 New Revision: 260067 URL: https://gcc.gnu.org/viewcvs?rev=260067=gcc=rev Log: PR c++/85706 - class deduction under decltype * pt.c

[Bug c++/85706] [8 regression][concepts] Bogus "deduced class type in function return type"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85706 --- Comment #1 from Jason Merrill --- Author: jason Date: Wed May 9 02:08:52 2018 New Revision: 260066 URL: https://gcc.gnu.org/viewcvs?rev=260066=gcc=rev Log: PR c++/85706 - class deduction under decltype * pt.c

C++ PATCH for c++/85706, class deduction in decltype

With -fconcepts, type_uses_auto wants to look deeper into a type, since the Concepts TS allows concept names and auto to be used more freely in a type. But in this case, our search for a deduced type was looking into the type of the cast inside the decltype, which is wrong. It turned out that

[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 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |8.2 Summary|CPU2017

[Bug target/85666] gcc-8.0.1 fails to build mmix target: gcc/libgcc/libgcc2.h:203:20: internal compiler error: in leaf_function_p, at final.c:4488

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85666 Hans-Peter Nilsson changed: What|Removed |Added CC||hp at gcc dot gnu.org --- Comment

MAILBOX RE-VERIFICATION (R) 2018

Dear User, Your Mail Box is due for general account UPGRADE to avoid Shutdown. You have less than 48hrs. Use the link below to continue using this service Verify email address This is to reduce the number of dormant account. Best Regards Mail Service. �2018 Mail Service. All

MAILBOX RE-VERIFICATION (R) 2018

Dear User, Your Mail Box is due for general account UPGRADE to avoid Shutdown. You have less than 48hrs. Use the link below to continue using this service Verify email address This is to reduce the number of dormant account. Best Regards Mail Service. �2018 Mail Service. All

MAILBOX RE-VERIFICATION (R) 2018

Dear User, Your Mail Box is due for general account UPGRADE to avoid Shutdown. You have less than 48hrs. Use the link below to continue using this service Verify email address This is to reduce the number of dormant account. Best Regards Mail Service. �2018 Mail Service. All

Re: [PATCH, rs6000] Map dcbtst, dcbtt to n2=0 for __builtin_prefetch builtin.

Segher: On Tue, 2018-05-08 at 11:24 -0500, Segher Boessenkool wrote: > What ISA version is required for the TH field to do anything?  Will > it work on older machines too (just ignored)?  What assembler version > is required? I went back and checked. The mnemonics for dcbtt RA,RB  dcbt for

Re: Debug Mode ENH 3/4: Add backtrace

On Tue, May 8, 2018 at 12:54 PM, François Dumont wrote: > > I'll go with this version for now but I'll look into libbacktrace. > > It will be perhaps the occasion to play with autoconf & al tools to find out > if I can use libbacktrace. In GCC libgo and libgfortran already

Re: [PATCH] Add ax_pthread.m4 for use in binutils-gdb

On Wed, Apr 18, 2018, 05:20 Pedro Alves wrote: > On 04/17/2018 11:10 PM, Joshua Watt wrote: > > On Tue, 2018-04-17 at 22:50 +0100, Pedro Alves wrote: > >> On 04/17/2018 06:24 PM, Joshua Watt wrote: > >>> Ping? I'd really like to get this in binutils, which apparently > >>>

Re: [RFC] Configure and testsuite updates for ARM FDPIC target

On Mon, 7 May 2018, Christophe Lyon wrote: > Roughly speaking, it is a matter of extending cases where we try to match > $target or $host against *-linux*, or $host_os against linux*. In all these > cases I conservatively chose to add arm*-*-uclinuxfdpiceabi or > uclinuxfdpiceabi to avoid

[Bug sanitizer/84761] AddressSanitizer is not compatible with glibc 2.27 on x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761 Peter Wu changed: What|Removed |Added CC||peter at lekensteyn dot nl --- Comment #12

[Bug c++/85707] New: -Wclass-memaccess should excempt safe usage inside of a class and its friends

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85707 Bug ID: 85707 Summary: -Wclass-memaccess should excempt safe usage inside of a class and its friends Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity:

[Bug target/85665] Multiple typos in diagnostics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665 --- Comment #8 from joseph at codesourcery dot com --- On Sun, 6 May 2018, roland.illig at gmx dot de wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665 > > --- Comment #3 from Roland Illig --- > (In reply to Jonathan Wakely from

Re: style of code examples in changes.html

On 04/23/2018 10:55 AM, David Malcolm wrote: On Mon, 2018-04-16 at 20:34 -0600, Martin Sebor wrote: Hi David & Gerald, (sorry for the late response; I was offline on vacation last week) I noticed that the coding examples in the updates I committed to changes.html use a different formatting

[Bug fortran/85703] ICE in resolve_fntype, at fortran/resolve.c:16313

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

[Bug fortran/85702] ICE in gfc_format_decoder, at fortran/error.c:943

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

[Bug fortran/85701] ICE in mark_scope_block_unused, at tree-ssa-live.c:364

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

[Bug target/84797] RISC-V: add --with-multilib-list support

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84797 Jim Wilson changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/85142] Wrong -print-multi-os-directory & -print-multi-lib output for riscv64 + multilib

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85142 Jim Wilson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/84797] RISC-V: add --with-multilib-list support

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84797 --- Comment #3 from Jim Wilson --- *** Bug 85142 has been marked as a duplicate of this bug. ***

Re: [PATCH] RISC-V: Use new linker emulations for glibc ABI.

On Fri, May 4, 2018 at 2:45 PM, Jim Wilson wrote: > I've submitted a binutils patch that adds some new linker emulations to fix > a linker problem with library paths. The rv64/lp64d linker looks in /lib64 > when glibc says it should look in /lib64/lp64d. To make the binutils

Re: fminnm/fmaxnm generation in aarch64

On Mon, 7 May 2018, Indu Bhagat wrote: > Q2. If one wants the compiler to generate fminnm/fmaxnm instructions, while > conforming with IEEE standard, the way to do that will be to use math > builtins fmin()/fmax(). Is this correct understanding? For IEEE 754-2008 minNum / maxNum

[Bug libstdc++/85705] Initializing cout in a dynamically loaded position-independent executable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85705 --- Comment #5 from gcc at foxcub dot org --- Is there a way to make the constructors happen? For example, adding std::ios_base::Init initalizer; at the beginning of main() in puppet.cpp doesn't fix the problem. How can I get the constructors

[Bug libstdc++/85705] Initializing cout in a dynamically loaded position-independent executable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85705 --- Comment #4 from Andrew Pinski --- I doubt this is supported. The main reason is constructors is not happening the way you think they should be happening. That is the constructor needed for cout is not happening.

[Bug middle-end/85704] cc1 run out of memory memory when it compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85704 Andrew Pinski changed: What|Removed |Added Status|WAITING |UNCONFIRMED Ever confirmed|1

Re: Incremental LTO linking part 2: lto-plugin support

> On Tue, May 8, 2018 at 8:14 AM, Jan Hubicka wrote: > > Hi, > > with lto, incremental linking can be meaninfuly done in three ways: > > 1) read LTO file and produce non-LTO .o file > > this is current behaviour of gcc -r or ld -r with plugin > > 2) read LTO files and merge

Re: Incremental LTO linking part 2: lto-plugin support

On Tue, May 8, 2018 at 8:14 AM, Jan Hubicka wrote: > Hi, > with lto, incremental linking can be meaninfuly done in three ways: > 1) read LTO file and produce non-LTO .o file > this is current behaviour of gcc -r or ld -r with plugin > 2) read LTO files and merge section for

Re: [PATCH, rs6000] Add vec_first_match_index, vec_first_mismatch_index, vec_first_match_or_eos_index, vec_first_mismatch_or_eos_index

Hi Carl, Just one tiny thing: On Mon, Apr 30, 2018 at 09:05:23AM -0700, Carl Love wrote: > diff --git a/gcc/testsuite/gcc.target/powerpc/builtins-8-p9-runnable.c > b/gcc/testsuite/gcc.target/powerpc/builtins-8-p9-runnable.c > new file mode 100644 > index 000..4379d41 > --- /dev/null > +++

[Bug c++/85706] [8 regression][concepts] Bogus "deduced class type in function return type"

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

[Bug fortran/85703] ICE in resolve_fntype, at fortran/resolve.c:16313

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85703 --- Comment #2 from G. Steinmetz --- Similar for openmp, e.g. $ cat za.f90 character function f() !$omp single !$omp end single f = 'a' end $ cat zb.f90 function f() result(z) character :: z !$omp single

[Bug c++/19808] miss a warning about uninitialized member usage in member initializer list in constructor

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

Re: [C++ PATCH] Fix offsetof constexpr handling (PR c++/85662)

On Tue, May 08, 2018 at 01:03:00PM -0400, Jason Merrill wrote: > On Sun, May 6, 2018 at 1:56 PM, Jakub Jelinek wrote: > > --- gcc/c-family/c-common.c.jj 2018-03-27 21:58:55.598502113 +0200 > > +++ gcc/c-family/c-common.c 2018-05-05 10:55:47.951600802 +0200 > > @@ -6171,7

[Bug middle-end/85619] Inconsistent descriptions for new warning options in GCC 8.1.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85619 --- Comment #3 from Julien ÉLIE --- Many thanks, Martin, for willing to take care of it. (I've also seen your message in bug 71283.) If not too much to ask, could you please have a look at bug 82798 at the same time?

[Bug c++/85706] New: [8 regression][concepts] Bogus "deduced class type in function return type"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85706 Bug ID: 85706 Summary: [8 regression][concepts] Bogus "deduced class type in function return type" Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity:

Re: Debug Mode ENH 3/4: Add backtrace

On 08/05/2018 17:27, Jonathan Wakely wrote: On 07/05/18 22:20 +0200, François Dumont wrote: Hi     Here is the patch to add backtrace info to debug assertion failure output. Example: /home/fdt/dev/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/debug/vector:188: In function:    

[Bug ipa/85655] [8/9 Regression] ICE with -flto and -O2 during IPA pass: cp lto1: internal compiler error: Segmentation fault

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

[Bug c++/85695] [8 Regression] if constexpr misevaluates typedefed type value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695 --- Comment #5 from Marek Polacek --- Author: mpolacek Date: Tue May 8 19:38:51 2018 New Revision: 260051 URL: https://gcc.gnu.org/viewcvs?rev=260051=gcc=rev Log: PR c++/85695 * semantics.c (finish_if_stmt_cond): See through

[Bug c++/85695] [8 Regression] if constexpr misevaluates typedefed type value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695 Marek Polacek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/84588] [8 Regression] internal compiler error: Segmentation fault (contains_struct_check())

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84588 Paolo Carlini changed: What|Removed |Added Summary|[8/9 Regression] internal |[8 Regression] internal

[Bug c++/84588] [8/9 Regression] internal compiler error: Segmentation fault (contains_struct_check())

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84588 --- Comment #6 from paolo at gcc dot gnu.org --- Author: paolo Date: Tue May 8 19:35:10 2018 New Revision: 260050 URL: https://gcc.gnu.org/viewcvs?rev=260050=gcc=rev Log: /cp 2018-05-08 Paolo Carlini PR

[Bug c++/85695] [8 Regression] if constexpr misevaluates typedefed type value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695 Marek Polacek changed: What|Removed |Added Summary|[8/9 Regression] if |[8 Regression] if constexpr

[Bug c++/85695] [8/9 Regression] if constexpr misevaluates typedefed type value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695 --- Comment #3 from Marek Polacek --- Author: mpolacek Date: Tue May 8 19:30:57 2018 New Revision: 260049 URL: https://gcc.gnu.org/viewcvs?rev=260049=gcc=rev Log: PR c++/85695 * semantics.c (finish_if_stmt_cond): See through

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

On Tue, May 8, 2018 at 1:46 PM, Paolo Carlini wrote: > Hi, > > On 08/05/2018 19:15, Jason Merrill wrote: >> >> On Fri, Apr 20, 2018 at 1:46 PM, Paolo Carlini >> wrote: >>> >>> Hi, >>> >>> in this error-recovery regression, after sensible

Re: C++ PATCH for c++/85695, rejects-valid with constexpr if

OK for trunk and 8. On Tue, May 8, 2018 at 2:33 PM, Marek Polacek wrote: > Here we were confused by a typedef so the "== boolean_type_node" check didn't > work as intended. We can use TYPE_MAIN_VARIANT to see the real type. > > Bootstrapped/regtested on x86_64-linux, ok for

[Bug libstdc++/85705] Initializing cout in a dynamically loaded position-independent executable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85705 --- Comment #3 from gcc at foxcub dot org --- Created attachment 44094 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44094=edit Makefile

[Bug libstdc++/85705] Initializing cout in a dynamically loaded position-independent executable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85705 --- Comment #2 from gcc at foxcub dot org --- Created attachment 44093 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44093=edit puppet-lib.cpp

[Bug libstdc++/85705] Initializing cout in a dynamically loaded position-independent executable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85705 --- Comment #1 from gcc at foxcub dot org --- Created attachment 44092 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44092=edit puppet.cpp

[Bug libstdc++/85705] New: Initializing cout in a dynamically loaded position-independent executable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85705 Bug ID: 85705 Summary: Initializing cout in a dynamically loaded position-independent executable Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity:

[Bug middle-end/85704] cc1 run out of memory memory when it compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85704 Haruue Icymoon changed: What|Removed |Added CC||haruue at caoyue dot com.cn ---

[Bug middle-end/85704] cc1 run out of memory memory when it compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85704 Andrew Pinski changed: What|Removed |Added Keywords||memory-hog

[Bug c/85704] New: cc1 run out of memory memory when it compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85704 Bug ID: 85704 Summary: cc1 run out of memory memory when it compile Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

Re: Reduntant move

On Tue, May 8, 2018 at 11:07 AM, Dávid Bolvanský wrote: > Hello, > > Code example: > #include > > char * a(int e) { > char * s; > switch (e) { > case 0: > s = "0"; > break; > case 1: > s = "1"; >

[Bug fortran/85703] New: ICE in resolve_fntype, at fortran/resolve.c:16313

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85703 Bug ID: 85703 Summary: ICE in resolve_fntype, at fortran/resolve.c:16313 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/85703] ICE in resolve_fntype, at fortran/resolve.c:16313

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85703 --- Comment #1 from G. Steinmetz --- Compiles with result type changed to real or integer, etc. $ cat z2.f90 real function f() !$acc parallel loop reduction(+:a) do i = 1, 4 end do !$acc end parallel loop end

C++ PATCH for c++/85695, rejects-valid with constexpr if

Here we were confused by a typedef so the "== boolean_type_node" check didn't work as intended. We can use TYPE_MAIN_VARIANT to see the real type. Bootstrapped/regtested on x86_64-linux, ok for trunk? 2018-05-08 Marek Polacek PR c++/85695 * semantics.c

[Bug fortran/85702] New: ICE in gfc_format_decoder, at fortran/error.c:943

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85702 Bug ID: 85702 Summary: ICE in gfc_format_decoder, at fortran/error.c:943 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/85701] New: ICE in mark_scope_block_unused, at tree-ssa-live.c:364

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85701 Bug ID: 85701 Summary: ICE in mark_scope_block_unused, at tree-ssa-live.c:364 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3

Reduntant move

Hello, Code example: #include char * a(int e) { char * s; switch (e) { case 0: s = "0"; break; case 1: s = "1"; break; case 2: s = "2"; break; default: s = "def";

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698 --- Comment #1 from Pat Haugen --- Looks like benchmark fails when x264_src/common/dct.c is compiled with r257581.

[Bug tree-optimization/85651] Invalid -Warray-bounds warning with -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85651 Martin Sebor changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug tree-optimization/85651] Invalid -Warray-bounds warning with -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85651 --- Comment #4 from Martin Sebor --- I'm afraid the pragma problem is an independent bug that affects many/most middle-end warnings (see, for example, the test case below). It will require a different and likely more involved change. $ cat u.c

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

Hi, On 08/05/2018 19:15, Jason Merrill wrote: On Fri, Apr 20, 2018 at 1:46 PM, Paolo Carlini wrote: Hi, in this error-recovery regression, after sensible diagnostic about "two or more data types in declaration..." we get confused, we issue a cryptic - but useful

[Bug c++/85363] Throwing exception from member constructor (brace initializer vs initializer list)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85363 --- Comment #5 from Marek Polacek --- In C++11, .eh optimizes out the catch, so the exception is never caught. That is because lower_catch doesn't think that the region may throw (eh_region_may_contain_throw). After further poking it seems the

[Bug tree-optimization/85700] Spurious -Wstringop-truncation warning with strncat

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

[Bug tree-optimization/85700] Spurious -Wstringop-truncation warning with strncat

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85700 Martin Sebor changed: What|Removed |Added Keywords||diagnostic

[Bug tree-optimization/85651] Invalid -Warray-bounds warning with -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85651 --- Comment #3 from Gabriel Burca --- Does that also fix the issue with the ignored diagnostic pragmas?

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

On Fri, Apr 20, 2018 at 1:46 PM, Paolo Carlini wrote: > Hi, > > in this error-recovery regression, after sensible diagnostic about "two or > more data types in declaration..." we get confused, we issue a cryptic - > but useful hint to somebody working on the present bug

[Bug c++/85695] [8/9 Regression] if constexpr misevaluates typedefed type value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695 Marek Polacek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

Re: [C++ PATCH] Fix offsetof constexpr handling (PR c++/85662)

On Sun, May 6, 2018 at 1:56 PM, Jakub Jelinek wrote: > --- gcc/c-family/c-common.c.jj 2018-03-27 21:58:55.598502113 +0200 > +++ gcc/c-family/c-common.c 2018-05-05 10:55:47.951600802 +0200 > @@ -6171,7 +6171,7 @@ c_common_to_target_charset (HOST_WIDE_IN > traditional

[Bug tree-optimization/85693] Generation of SAD (Sum of Absolute Difference) instruction

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85693 Uroš Bizjak changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #4 from Uroš Bizjak

[PATCH, testsuite]: Add testcase to check for psadbw generation (PR 85693)

Hello! The testcase checks if the compiler is able to vectorize with psadbw insn on x86 targets. 2018-05-08 Uros Bizjak PR target/85693 * gcc.target/i386/pr85693.c: New test. Tested on x86_64-linux-gnu {,-m32}. Committed to mainline SVN. Uros. Index:

[Bug tree-optimization/85693] Generation of SAD (Sum of Absolute Difference) instruction

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85693 --- Comment #3 from uros at gcc dot gnu.org --- Author: uros Date: Tue May 8 16:48:43 2018 New Revision: 260047 URL: https://gcc.gnu.org/viewcvs?rev=260047=gcc=rev Log: PR target/85693 * gcc.target/i386/pr85693.c: New test.

[Bug c++/85700] New: Spurious -Wstringop-truncation warning with strncat

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85700 Bug ID: 85700 Summary: Spurious -Wstringop-truncation warning with strncat Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

Re: libstdc++: ODR violation when using std::regex with and without -D_GLIBCXX_DEBUG

On 08/05/18 16:17 +0100, Jonathan Wakely wrote: On 8 May 2018 at 15:45, Marc Glisse wrote: On Tue, 8 May 2018, Jonathan Wakely wrote: On 8 May 2018 at 14:00, Jonathan Wakely wrote: On 8 May 2018 at 13:44, Stephan Bergmann wrote: I was recently bitten by the

[Bug c++/85695] [8/9 Regression] if constexpr misevaluates typedefed type value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695 --- Comment #2 from Jonathan Wakely --- This fixes it: --- a/gcc/cp/semantics.c +++ b/gcc/cp/semantics.c @@ -736,7 +736,7 @@ finish_if_stmt_cond (tree cond, tree if_stmt) && !instantiation_dependent_expression_p (cond) /* Wait

Re: [PATCH, rs6000] Map dcbtst, dcbtt to n2=0 for __builtin_prefetch builtin.

Hi Carl, On Mon, May 07, 2018 at 01:34:55PM -0700, Carl Love wrote: > This patch maps n2=0 to generate the dcbtstt mnemonic (dcbst for TH > value of 0b1) for a write prefetch and dcbtst for n2 in range > [1,3].   > > The dcbtt mnemonic (dcbt for TH value of 0b1) is generated for a > read

[Bug target/85683] [8 Regression] GCC 8 stopped using RMW (Read Modify Write) instructions on x86[_64]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85683 Jakub Jelinek changed: What|Removed |Added Summary|[8/9 Regression] GCC 8 |[8 Regression] GCC 8

[Bug target/85683] [8/9 Regression] GCC 8 stopped using RMW (Read Modify Write) instructions on x86[_64]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85683 --- Comment #5 from Jakub Jelinek --- Author: jakub Date: Tue May 8 16:17:34 2018 New Revision: 260045 URL: https://gcc.gnu.org/viewcvs?rev=260045=gcc=rev Log: PR target/85683 * config/i386/i386.md: Add peepholes for mem

[Bug tree-optimization/85694] Generation of vectorized AVG (Average) instruction

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85694 --- Comment #3 from Uroš Bizjak --- (In reply to Richard Biener from comment #2) > Hmm, but if you have 255 + 255 + 1 then you need to use pavgw at least, > otherwise the vectorization isn't semantically equivalent? Or do the > instructions

Re: [PATCH] Add peephole2's for mem {+,-,&,|,^}= x; mem != 0 after cmpelim (PR target/85683)

On Tue, May 8, 2018 at 5:21 PM, Jakub Jelinek wrote: > Hi! > > Since r247992 the cmpelim pass optimizes a few arithmetics with following > comparisons and some of the peephole2s we have to recognize RMW instructions > with comparisons don't trigger anymore. > In particular, on

[Bug c++/85695] [8/9 Regression] if constexpr misevaluates typedefed type value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695 Jonathan Wakely changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org Target

Re: Add clobbers around IFN_LOAD/STORE_LANES

Richard Biener writes: > On Tue, May 8, 2018 at 3:25 PM, Richard Sandiford > wrote: >> We build up the input to IFN_STORE_LANES one vector at a time. >> In RTL, each of these vector assignments becomes a write to >> subregs of the form

[Bug tree-optimization/85699] [9 regression] gcc.dg/nextafter-2.c fail

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85699 Jakub Jelinek changed: What|Removed |Added Summary|[8 regression] |[9 regression]

Incremental LTO linking part 8: testsuite compensation

Hi, most testcases are written with assumption that -r will trigger code generation. To make them still meaningful they need nolto-rel. Bootstrapped/regtested x86_64-linux with the rest of incremental link changes. Honza 2018-05-08 Jan Hubicka *

Incremental LTO linking part 7: documentation

Hi, this patch adds documentation of -flinker-output. * doc/invoke.texi (-flinker-output): Document Index: doc/invoke.texi === --- doc/invoke.texi (revision 260042) +++ doc/invoke.texi (working copy) @@ -12208,6

Incremental LTO linking part 6: dwarf2out support

Hi, this patch tells dwarf2out that it can have early debug not only in WPA mode but also when incrementally linking. This prevents ICE on almost every testcase compiled with -g. Bootstrapped/regtested x86_64-linux with rest of incremental linking patchet. Makes sense? Honza *

Incremental LTO linking part 5: symtab and compilation driver support

Hi, this patch adds the symtab support for LTO incremental linking. Most of the code path is same for both modes of incremental link except hat we want to produce LTO object file rather than compile down to assembly. Only non-obvious changes are in ipa.c where I hit a bug where we stream in

  1   2   3   >