Re: gdb 8.x - g++ 7.x compatibility

On 4 February 2018 at 19:17, Martin Sebor wrote: > I think this message would be the most meaningful if the "auto" > part were replaced with the deduced type. With that, the suffix > of the constant isn't important, just as in other contexts. > > I didn't consider the use of auto as a template

Re: gdb 8.x - g++ 7.x compatibility

On 5 February 2018 at 09:16, Stephan Bergmann wrote: > On 05.02.2018 06:06, Simon Marchi wrote: >> >> On 2018-02-04 02:17 PM, Martin Sebor wrote: >>> >>> Printing the suffix is unhelpful because it leads to unnecessary >>> differences in diagnostics (even in non-template contexts). For >>>

Resolving LTO symbols for static library boundary

Hello GCC In trying to make it possible to use LTO for distro-builds of Qt, I have again hit the problem of static libraries. In Qt in general we for LTO rely on a library boundary, where LTO gets resolved when generating the library but no LTO-symbols are exported in the shared library. This

Re: Debugging optimizer problems

On 02/02/18 23:03, jacob navia wrote: > Le 02/02/2018 à 22:11, Florian Weimer a écrit : >> * jacob navia: >> >>> I have in my small C compiler introduced the following construct: >>> >>> #pragma optimize(on/off,push/pop) >> Not sure what you are after. GCC has something quite similar: >> >>

Re: gdb 8.x - g++ 7.x compatibility

On 02/04/2018 10:06 PM, Simon Marchi wrote: Hi Martin, Thanks for the reply. On 2018-02-04 02:17 PM, Martin Sebor wrote: Printing the suffix is unhelpful because it leads to unnecessary differences in diagnostics (even in non-template contexts). For templates with non-type template

Re: gdb 8.x - g++ 7.x compatibility

On 2018-02-05 11:45, Martin Sebor wrote: Yes, with auto, the type of the constant does determine the type of the specialization of the template in the source code. In non-type template arguments, and more to the point I was making, in diagnostics, the suffix shouldn't or doesn't need to be what

Re: gdb 8.x - g++ 7.x compatibility

On 05.02.2018 06:06, Simon Marchi wrote: On 2018-02-04 02:17 PM, Martin Sebor wrote: Printing the suffix is unhelpful because it leads to unnecessary differences in diagnostics (even in non-template contexts). For templates with non-type template parameters there is no difference between, say

Re: Resolving LTO symbols for static library boundary

Dne 2018-02-05 18:44, Richard Biener napsal: On February 5, 2018 12:26:58 PM GMT+01:00, Allan Sandfeld Jensen wrote: Hello GCC In trying to make it possible to use LTO for distro-builds of Qt, I have again hit the problem of static libraries. In Qt in general we for LTO

ICE in stage 2 during libgcc configure on x86_64-w64-mingw32, rev. 257390

Today I get an ICE during configuration of libgcc in stage 2 on x86_64-w64-mingw32. That's rev. 257390. configure:3688: /opt/devel/SCRATCH/tmp.Sbg1TmFqa7/gcc-8.0.0/gcc-8.0.0/./gcc/xgcc -B/opt/devel/SCRATCH/tmp.Sbg1TmFqa7/gcc-8.0.0/gcc-8.0.0/./gcc/

Re: gdb 8.x - g++ 7.x compatibility

Interestingly RTTI name also gives no guarantees: http://en.cppreference.com/w/cpp/types/type_info/name << Returns an implementation defined null-terminated character string containing the name of the type. No guarantees are given; in particular, the returned string can be identical for several

Re: gdb 8.x - g++ 7.x compatibility

On 5 February 2018 at 17:44, Roman Popov wrote: > Interestingly RTTI name also gives no guarantees: > http://en.cppreference.com/w/cpp/types/type_info/name > > << Returns an implementation defined null-terminated character string > containing the name of the type. No guarantees are given; in

Re: gdb 8.x - g++ 7.x compatibility

On 5 February 2018 at 20:10, Roman Popov wrote: > Do you mean that g++ guarantees uniqueness of mangled names for types? And Of course. The mangled name is determined by the ABI and must be stable, predictable and unique, so that linking works. > uses name compare for operator== ? Yes.

Re: gdb 8.x - g++ 7.x compatibility

On 02/05/2018 09:59 AM, Simon Marchi wrote: On 2018-02-05 11:45, Martin Sebor wrote: Yes, with auto, the type of the constant does determine the type of the specialization of the template in the source code. In non-type template arguments, and more to the point I was making, in diagnostics,

Re: Resolving LTO symbols for static library boundary

On February 5, 2018 12:26:58 PM GMT+01:00, Allan Sandfeld Jensen wrote: >Hello GCC > >In trying to make it possible to use LTO for distro-builds of Qt, I >have again >hit the problem of static libraries. In Qt in general we for LTO rely >on a >library boundary, where LTO

Re: gdb 8.x - g++ 7.x compatibility

Do you mean that g++ guarantees uniqueness of mangled names for types? And uses name compare for operator== ? 2018-02-05 12:08 GMT-08:00 Jonathan Wakely : > On 5 February 2018 at 17:44, Roman Popov wrote: > > Interestingly RTTI name also gives no guarantees: > >

Re: Debugging optimizer problems

On 02/02/2018 12:29 PM, jacob navia wrote: Hi I am confronted with a classical problem: a program gives correct results when compiled with optimizations off, and gives the wrong ones with optimization (-O2) on. I have isolated the probem in a single file but now there is no way that I can

Copyright Assignment

Hi, I've written to this list previously to mention I'm working on implementing p0515 (the spaceship operator) for C++. Although I'm still far from finished I'd like to make sure that when I am, I will be able to contribute my changes to GCC. Please tell me what I should do to take care of the

Re: gdb 8.x - g++ 7.x compatibility

Well, if ABI has specification for type naming, why not to put this name to debug_info so debugger can use it? In this case argument that "each producer has its own naming conventions" no longer works. Any producer for given ABI must use ABI-specified names. 2018-02-05 12:12 GMT-08:00

[Bug target/84209] New: [avr] Don't split SP in split2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84209 Bug ID: 84209 Summary: [avr] Don't split SP in split2 Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

[Bug target/84209] [avr] Don't split SP in split2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84209 Georg-Johann Lay changed: What|Removed |Added Keywords||wrong-code Target|

[Bug sanitizer/84210] New: __ubsan_handle_builtin_unreachable shoun't be const

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84210 Bug ID: 84210 Summary: __ubsan_handle_builtin_unreachable shoun't be const Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3

Re: [Arm] GCC crash in cprop_hardreg when targeting v8-A Thumb

Hi Michael, On 04/02/18 02:52, Michael Collison wrote: This patches fixes a bug affecting two patterns in arm/thumb2.md where the split condition was insufficient and allowed illegal rtl to be generated. The split condition for patterns "*thumb2_mov_negscc "and "*thumb_mov_notscc " allowed

[Bug lto/81004] [7/8 Regression] linking failed with -flto and static libboost_program_options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81004 --- Comment #20 from Martin Liška --- It's really fixed on trunk since r257023.

[committed][AArch64] Remove SVE XFAILs

These tests started passing after r257293, which had the side-effect of renumbering the SSA names and leaving the COND_EXPRs in their natural order. This does show a deeper underlying issue that code generation is too sensitive to internal things like SSA_NAME versions, but it no longer affects

[Bug c++/84171] [8 Regression] ICE with -Wsign-compare

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84171 Richard Biener changed: What|Removed |Added Priority|P3 |P4

[Bug c++/82782] ICE: nested template alias and specialized template with auto template parameter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82782 Paolo Carlini changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/84209] [avr] Don't split SP in split2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84209 Georg-Johann Lay changed: What|Removed |Added Status|ASSIGNED|NEW Assignee|gjl at gcc

[Bug target/68028] [6/7/8 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028 --- Comment #11 from Nick Clifton --- Hi Richard, > If the backend doesn't support mixing of -msingle-float/-mno-single-float > within a compilation unit then this will only work if the user didn't mix TUs > with conflicting setting at

Re: [PATCH] PowerPC PR target/84154, fix floating point to small integer conversion regression

On Mon, Feb 05, 2018 at 05:57:25AM -0600, Segher Boessenkool wrote: > On Thu, Feb 01, 2018 at 02:31:17PM -0500, Michael Meissner wrote: > > This patch fixes the optimization regression that occurred on GCC 7 where > > conversions from the various floating point types to small integers would at > >

[Bug lto/81004] [7/8 Regression] linking failed with -flto and static libboost_program_options

for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. but not with $ ~/8-install-slow/bin/g++ --version g++ (GCC) 8.0.1 20180205 (experimental) Copyright (C) 2018 Free Software Foundation, Inc. This is free software; see the source

[Bug tree-optimization/38785] [6/7/8 Regression] huge performance regression on EEMBC bitmnp01

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38785 Richard Biener changed: What|Removed |Added Status|REOPENED|NEW Last reconfirmed|2010-02-19

[Bug lto/70929] [6/7/8 regression] Cross-module inlining for functions having argument passed by reference is no longer working.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70929 --- Comment #8 from rguenther at suse dot de --- On Mon, 5 Feb 2018, hubicka at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70929 > > --- Comment #7 from Jan Hubicka --- > Hmm, this actually looks reasonable for me

[Bug ipa/57218] [6/7/8 Regression] Excessive inlining even at -Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57218 --- Comment #13 from Aldy Hernandez --- (In reply to Jan Hubicka from comment #12) > Set component as IPA so it stays at my radar. It is probably too late for > GCC 8 but I will try to finally take a look next stage1. Inlining those >

[Bug target/84172] option "-O3" create slower code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84172 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/84204] [8 Regression] [graphite] ICE in set_codegen_error, at graphite-isl-ast-to-gimple.c:206

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

[Bug tree-optimization/84205] [8 Regression] [graphite] ICE in set_codegen_error, at graphite-isl-ast-to-gimple.c:206

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

[Bug c/84190] [7/8 Regression] double arithmetic on x86 no longer rounds to nearest

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84190 Richard Biener changed: What|Removed |Added CC||jsm28 at gcc dot gnu.org --- Comment

[Bug sanitizer/84210] __ubsan_handle_builtin_unreachable shoun't be const

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84210 --- Comment #2 from Andrey Ryabinin --- (In reply to Richard Biener from comment #1) > Confirmed. Note that I'm not sure it makes no sense - it just means the > function has no side-effect besides not returning ;) > Well, GCC docs say that

[Bug sanitizer/84208] fsanitize-address-use-after-scope Not working for ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84208 --- Comment #4 from Akhilesh Kumar --- Please find Patch and test Case I tried but unable to attached patch as Attachment :( My Changes for address-use-after-scope which is working for X86 but not for ARM target --- gcc/asan.c |

[Bug tree-optimization/39612] [6/7/8 Regression] LIM inserts loads from uninitialized local memory

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39612 Richard Biener changed: What|Removed |Added Last reconfirmed|2009-10-05 20:09:44 |2018-2-5 --- Comment #30 from Richard

[PATCH] Cherry-pick libsanitizer pointer-pair tristate option.

Hi. This is upstream backport of libsanitizer which makes detect-invalid-pointer-pair a tristate option. Patch is preapproved by Jakub. Patch can bootstrap on ppc64le-redhat-linux and survives regression tests. Martin gcc/ChangeLog: 2018-02-05 Martin Liska *

[Bug tree-optimization/13962] [tree-ssa] make "fold" use alias information to optimize pointer comparisons

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13962 --- Comment #14 from Richard Biener --- *** Bug 84188 has been marked as a duplicate of this bug. ***

[Bug tree-optimization/84188] assume non-null malloc pointers are distinct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84188 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug middle-end/84200] [8 Regression] r256888 causes 30% performance regression of 519.lbm_r at -Ofast generic tuning on Zen

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84200 Richard Biener changed: What|Removed |Added Keywords||missed-optimization

[Bug tree-optimization/84106] loop distribution cost-model needs work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84106 --- Comment #6 from Daniel Fruzynski --- When you will be revisiting your cost-model for loops, please also take a look on this code. test2 has one assignment moved to separate loops, and it is about twice as

[Bug target/84209] [avr] Don't split SP in split2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84209 --- Comment #1 from Georg-Johann Lay --- Created attachment 43338 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43338=edit Proposed patch against v7

Re: [PATCH] PowerPC PR target/84154, fix floating point to small integer conversion regression

On Thu, Feb 01, 2018 at 02:31:17PM -0500, Michael Meissner wrote: > This patch fixes the optimization regression that occurred on GCC 7 where > conversions from the various floating point types to small integers would at > times generate a store and a load. [ snip big explanation; thanks for

[Bug tree-optimization/82518] [8 regression] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb since r252917

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518 --- Comment #12 from Aldy Hernandez --- (In reply to Christophe Lyon from comment #11) > My setup uses armeb-none-linux-gnueabihf (as opposed to armeb-eabi as you > report). I have never tried armeb-eabi. > > I am also using qemu as simulator

[Bug target/84211] New: [avr] Perform a post-reload register optimization pass

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84211 Bug ID: 84211 Summary: [avr] Perform a post-reload register optimization pass Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3

[Bug sanitizer/84210] __ubsan_handle_builtin_unreachable shoun't be const

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84210 Martin Liška changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org --- Comment

[Bug lto/84212] New: -Wno-* does not disable warnings from -flto link stage

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84212 Bug ID: 84212 Summary: -Wno-* does not disable warnings from -flto link stage Product: gcc Version: 7.2.0 Status: UNCONFIRMED Severity: normal Priority: P3

[patch][i386] Adding pconfig, wbnoinvd and wbinvd intrinsics

Hi, This patch adds new intrinsics: pconfig, wbnoinvd and wbinvd. 05.02.2018 Olga Makhotina  gcc/ * common/config/i386/i386-common.c (OPTION_MASK_ISA_PCONFIG_SET, OPTION_MASK_ISA_PCONFIG_UNSET, OPTION_MASK_ISA_WBNOINVD_SET,

[Bug tree-optimization/82518] [8 regression] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb since r252917

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518 --- Comment #13 from Nick Clifton --- Hi Aldy, > pc: 8ca4, instr: e1c520fc > pc: 4, instr: ea00089b > > I took a peek at the executable being run with "/my-arm-build/objdudump -D > the-executable.exe", and I see we are failing in >

[Bug middle-end/64501] Unreachable catch BB for try blocks that cannot create an exception of specific type

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

[PATCH][OBVIOUS] Fix GCOV documentation (PR gcov-profile/84137).

Hello. Very simple patch fixes documentation. I'm going to install it to all active branches. Martin gcc/ChangeLog: 2018-02-05 Martin Liska PR gcov-profile/84137 * doc/gcov.texi: Fix typo in documentation. --- gcc/doc/gcov.texi | 2 +- 1 file changed, 1

[Bug target/27855] [6/7/8 regression] reassociation causes the RA to be confused

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27855 --- Comment #55 from Richard Biener --- I think the original report is about x87 math vs. SSE math. It's a bit hard to benchmark this through the releases given changes in tuning and vector feature sets (-march=native is out of the question).

[Bug target/27855] [6/7/8 regression] reassociation causes the RA to be confused

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27855 --- Comment #57 from rguenther at suse dot de --- On Mon, 5 Feb 2018, aldyh at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27855 > > --- Comment #56 from Aldy Hernandez --- > (In reply to Richard Biener from comment

[Bug c/84179] -save-temps breaks implicit-fallthrough comment heuristic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84179 Richard Biener changed: What|Removed |Added Keywords||diagnostic Version|unknown

[Bug target/27855] [6/7/8 regression] reassociation causes the RA to be confused

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27855 Aldy Hernandez changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/27827] [4.0 Regression] gcc 4 produces worse x87 code on all platforms than gcc 3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27827 Bug 27827 depends on bug 27855, which changed state. Bug 27855 Summary: [6/7/8 regression] reassociation causes the RA to be confused https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27855 What|Removed |Added

[Bug c/84190] [7/8 Regression] double arithmetic on x86 no longer rounds to nearest

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

[Bug c++/84196] [6/7/8 Regression] invalid call to a function template with a vector argument silently accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84196 Richard Biener changed: What|Removed |Added Target Milestone|--- |6.5

[PATCH][GCC][ARM] Silence ARM_ARCH redefinition warning and keep better track of architecturs already emitted.

Hi All, This patch silences the warnings that were emitted when certain ACLE macros were being redefined when using the new target pragma or attribute to change architecture level. It also keeps better track of which arch directives have already been emitted. This allows special cases that

[Bug target/84211] [avr] Perform a post-reload register optimization pass

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84211 Georg-Johann Lay changed: What|Removed |Added Keywords||missed-optimization

[Bug lto/81004] [7/8 Regression] linking failed with -flto and static libboost_program_options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81004 --- Comment #21 from Jan Hubicka --- > It's really fixed on trunk since r257023. Seems like it just went latent. I do not see how that change can fix the problem. Honza

[Bug middle-end/63311] [6/7/8 Regression] -O1 optimization introduces valgrind warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63311 Aldy Hernandez changed: What|Removed |Added Last reconfirmed|2014-09-22 00:00:00 |2018-2-5 CC|

[Bug c++/84197] Segmentation fault when setting -g

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84197 Marek Polacek changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org --- Comment

[Bug c++/84196] [6/7/8 Regression] invalid call to a function template with a vector argument silently accepted

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

[Bug gcov-profile/84137] Typo in gcov online documentation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84137 Martin Liška changed: What|Removed |Added Known to work||8.0 Known to fail|

[Bug gcov-profile/84137] Typo in gcov online documentation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84137 --- Comment #2 from Martin Liška --- Author: marxin Date: Mon Feb 5 09:59:16 2018 New Revision: 257384 URL: https://gcc.gnu.org/viewcvs?rev=257384=gcc=rev Log: Fix GCOV documentation (PR gcov-profile/84137). 2018-02-05 Martin Liska

[Bug target/27855] [6/7/8 regression] reassociation causes the RA to be confused

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27855 --- Comment #56 from Aldy Hernandez --- (In reply to Richard Biener from comment #55) > Note the original report used -O and Aldhy used -O2 but we are talking > about a benchmark and when you use -ffast-math you also use -O3. Thanks, I will

[Bug c++/82782] ICE: nested template alias and specialized template with auto template parameter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82782 --- Comment #2 from paolo at gcc dot gnu.org --- Author: paolo Date: Mon Feb 5 11:15:55 2018 New Revision: 257388 URL: https://gcc.gnu.org/viewcvs?rev=257388=gcc=rev Log: 2018-02-05 Paolo Carlini PR

[Bug c++/70401] [c++1z on mingw]compile variadic template failed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70401 Paolo Carlini changed: What|Removed |Added CC||jyong at gcc dot gnu.org --- Comment #2

[Bug c++/84192] [7/8 Regression] ICE with statement expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84192 Richard Biener changed: What|Removed |Added Version|unknown |7.3.1 Target Milestone|---

[Bug c++/84197] Segmentation fault when setting -g

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84197 Richard Biener changed: What|Removed |Added Keywords||ice-on-valid-code

[Bug sanitizer/84210] __ubsan_handle_builtin_unreachable shoun't be const

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

Re: [patch, libfortran] Use flexible array members for array descriptor

On Sun, Feb 4, 2018 at 9:49 PM, Thomas Koenig wrote: > Hello world, > > in the attached patch, I have used flexible array members for > using the different descriptor types (following Richi's advice). > This does not change the binary ABI, but the library code > maches what

[Bug sanitizer/84208] fsanitize-address-use-after-scope Not working for ARM

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

[Bug tree-optimization/84204] [8 Regression] [graphite] ICE in set_codegen_error, at graphite-isl-ast-to-gimple.c:206

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84204 --- Comment #2 from Richard Biener --- The limit you set to scev-max-expr-size is quite low but I expect it just needs a more complicated testcase to trigger this with larger values. We apply this limit in tree-chrec.c very inconsequential so I

[Bug ipa/81360] [8 Regression] ice in estimate_edge_growth, at ipa-inline.h:86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81360 --- Comment #15 from Martin Liška --- Should(In reply to Christophe Lyon from comment #14) > The new test fails on arm and aarch64: > FAIL: g++.dg/torture/pr81360.C -O2 -flto -fuse-linker-plugin > -fno-fat-lto-objects scan-ipa-dump icf

[Bug sanitizer/84210] __ubsan_handle_builtin_unreachable shoun't be const

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84210 --- Comment #4 from Marek Polacek --- I don't remember if the const was needed. I guess if the testcases added in r217553 still pass even without the const then we can get rid of it.

[Bug tree-optimization/82518] [8 regression] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb since r252917

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518 --- Comment #14 from Aldy Hernandez --- (In reply to Nick Clifton from comment #13) > Hi Aldy, > > > > pc: 8ca4, instr: e1c520fc > > pc: 4, instr: ea00089b > > > > I took a peek at the executable being run with "/my-arm-build/objdudump -D > >

[Bug lto/81004] [7/8 Regression] linking failed with -flto and static libboost_program_options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81004 --- Comment #23 from Jan Hubicka --- Created attachment 43340 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43340=edit Patch in am testing This patch transitions the info to merged tree and adds sanity check that we miss no resolutions.

[Bug tree-optimization/82518] [8 regression] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb since r252917

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518 --- Comment #17 from Christophe Lyon --- (In reply to Aldy Hernandez from comment #12) > along with the isub8 subroutine, and continue chopping things similarly > upward until you get to the abort that fails. Then see if you can chop >

Re: [PATCH] Fix PR83008

On 31 January 2018 at 16:01, Richard Biener wrote: > On Wed, 31 Jan 2018, Christophe Lyon wrote: > > > On 30 January 2018 at 11:47, Jakub Jelinek wrote: > > > On Tue, Jan 30, 2018 at 11:07:50AM +0100, Richard Biener wrote: > > >> > > >> I have been asked to

Do not lose track of resolution info due to tree merging

Hi, in the testcase of PR81004 we produce wrong code (reference to optimized out comdat symbol) due to strange sequence of events that is initiated by fact that after streaming in a comdat group we sed one of resolution infos to LDPR_UNKNOWN. This is because of tree merging with earlier unit that

[Bug lto/81004] [7/8 Regression] linking failed with -flto and static libboost_program_options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81004 --- Comment #22 from Jan Hubicka --- OK, the bug reproduces with tree.c changes reverted and I see what is going on. We have two files in res file we get: 2 lines.o 7 245 4d647b2020ca5815 PREVAILING_DEF_IRONLY _Z8validatev 334 4d647b2020ca5815

[Bug c++/84186] nested template qualified-id not parsed correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84186 --- Comment #3 from Jonathan Wakely --- Yes, I would have thought it's needed too. The other compilers I tried accept it with or without the 'template' keyword.

[Bug libstdc++/84170] std::find_if performance issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84170 --- Comment #1 from Jonathan Wakely --- When the code was written it was definitely beneficial to manually unroll, as measurements at the time showed. Any change would have to be based on measurements, not just unverified assumptions.

[Bug lto/84213] New: 521.wrf_r from SPEC 2017 fails to build (link) with LTO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84213 Bug ID: 84213 Summary: 521.wrf_r from SPEC 2017 fails to build (link) with LTO Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/82518] [8 regression] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb since r252917

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518 --- Comment #15 from Aldy Hernandez --- (In reply to Aldy Hernandez from comment #14) > (In reply to Nick Clifton from comment #13) > > Hi Aldy, > > > > > > > pc: 8ca4, instr: e1c520fc > > > pc: 4, instr: ea00089b > > > > > > I took a peek at

[Bug middle-end/84200] [8 Regression] r256888 causes 30% performance regression of 519.lbm_r at -Ofast generic tuning on Zen

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84200 --- Comment #3 from Martin Liška --- (In reply to Sebastian Peryt from comment #1) > I'm not sure if that can be treated as duplicate but that performance > degradation looks like is related to PR84149. I guess it will be a different story as

Re: [PATCH] PowerPC PR target/84154, fix floating point to small integer conversion regression

On Mon, Feb 05, 2018 at 07:54:58AM -0500, Michael Meissner wrote: > On Mon, Feb 05, 2018 at 05:57:25AM -0600, Segher Boessenkool wrote: > > On Thu, Feb 01, 2018 at 02:31:17PM -0500, Michael Meissner wrote: > > > This patch fixes the optimization regression that occurred on GCC 7 where > > >

[Bug target/68028] [6/7/8 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028 --- Comment #12 from rguenther at suse dot de --- On Mon, 5 Feb 2018, nickc at redhat dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028 > > --- Comment #11 from Nick Clifton --- > Hi Richard, > > > If the backend doesn't

[Bug lto/63688] all_symbols_read_handler: Assertion `lto_wrapper_argv' failed.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63688 Allan Jensen changed: What|Removed |Added CC||linux at carewolf dot com --- Comment #2

[Bug ipa/84149] [8 Regression] SPEC CPU2017 505.mcf/605.mcf ~10% performance regression with r256888

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

[Bug middle-end/84214] New: recip and slp passes conflict

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84214 Bug ID: 84214 Summary: recip and slp passes conflict Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end

[Bug tree-optimization/82518] [8 regression] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb since r252917

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518 --- Comment #18 from Aldy Hernandez --- (In reply to Christophe Lyon from comment #17) > (In reply to Aldy Hernandez from comment #12) > > > along with the isub8 subroutine, and continue chopping things similarly > > upward until you get to the

[Bug c++/84191] Compiler ICEs when trying to resolve impossible arithmetic operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84191 Marek Polacek changed: What|Removed |Added Keywords||needs-bisection, |

[Bug middle-end/84200] [8 Regression] r256888 causes 30% performance regression of 519.lbm_r at -Ofast generic tuning on Zen

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

  1   2   3   >