Re: LTO vs GCC 8

On 11/05/18 17:49, Freddie Chopin wrote: > On Fri, 2018-05-11 at 13:06 +0200, David Brown wrote: >> For the Cortex-M devices (and probably many other RISC targets), >> -fdata-sections comes at a big cost - it effectively blocks >> -fsection-anchors and makes access to file-static data a lot

Re: Possible bug in cse.c affecting pre/post-modify mem access

On 05/12/2018 01:35 PM, Bernd Schmidt wrote: > On 05/12/2018 07:01 PM, Jeff Law wrote: > >> No. We're not supposed to have any auto-inc insns prior to the auto-inc >> pass. A stack push/pop early in the compiler would have to be >> represented by a PARALLEL. >> >> It's been this way forever.

Please support the _Atomic keyword in C++

In addition to the bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932 I wanted to add some comment: It would be very useful if the _Atomic keyword would be supported in C++. This way the header could be included inconditionally in C++ code. Even if it is not compatible with the C++ header,

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

Hi, I'm a firmware/embedded engineer and frequently run into cases where certain parts of the code need to be placed in a special memory area (for example, because the area that contains the other code is not yet initialized or currently inaccessible). My go-to method to solve this is to mark all

Re: Possible bug in cse.c affecting pre/post-modify mem access

On 05/14/2018 10:55 PM, Jeff Law wrote: > That does sound vaguely familiar. Did we put autoinc notes on the stack > pushes? Not as far as I recall. I only see REG_ARGS_SIZE notes in the dumps. > That makes me wonder if there is a latent bug though. Consider pushing > args to a pure function.

Re: Please support the _Atomic keyword in C++

On 14 May 2018 at 22:32, Rodrigo V. G. wrote: > In addition to the bug: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932 > I wanted to add some comment: > > It would be very useful if the _Atomic keyword would be supported in C++. > This way the header could be included

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #9 from Jan --- I'm using the clear linux gcc version well atleast the patches. Maybe thats the culprit. https://clearlinux.org/ But it should be easy to run that in a container. I reverted some of the patches and rebuild gcc. I

[Bug libstdc++/85768] [9 Regression] FreeBSD bootstrap fails due to undefined reference to 'backtrace'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85768 Richard Biener changed: What|Removed |Added Target Milestone|--- |9.0 --- Comment #1 from Richard Biener

[Bug target/85769] [8/9 Regression] ICE in extract_constrain_insn, at recog.c:2205 for -mcpu=thunderx

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

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #4 from Jan --- Created attachment 44127 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44127=edit preproccessed source and gcda

[Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899 --- Comment #22 from Marc Glisse --- (In reply to rguent...@suse.de from comment #21) > Note that in the strict C semantic thing __restrict on > this isn't valid as the following is valid C++: > > Foo() __restrict > { > Foo *x = this; >

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #3 from Martin Liška --- (In reply to Richard Biener from comment #2) > Please attach the preprocessed source. And profile file (*.gcda) that should be somewhere: find /var/tmp/portage/pgo/bash -name alias.gcda

[Bug c++/85761] [8/9 Regression] ICE on invalid in rtl with uncaptured constexpr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85761 Richard Biener changed: What|Removed |Added Priority|P3 |P2 Status|UNCONFIRMED

[Bug lto/48200] linking shared library with LTO results in different exported symbols

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200 --- Comment #21 from Xi Ruoyao --- I made up a (highly immature) patch in the days. This "thing" works with simple source code files but I believe there are many bugs in the patch. And I suggest to make "weakref" attribute to output ".symver"

Re: [PATCH 1/2] gcc_qsort: source code changes

On Mon, May 14, 2018 at 8:37 AM, Alexander Monakov wrote: > On Sun, 13 May 2018, H.J. Lu wrote: >> This breaks bootstrap on Fedora 28/i686: >> >> https://gcc.gnu.org/ml/gcc-regression/2018-05/msg00088.html >> >> ../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro

Re: PR85734

On 14 May 2018 at 14:46, Richard Biener wrote: > On Mon, 14 May 2018, Prathamesh Kulkarni wrote: > >> Hi, >> The attached patch tries to fix PR85734, by gating on >> !function_always_visible_to_compiler_p. >> Bootstrap+test in progress on x86_64. >> OK to commit if passes ? > >

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #10 from Martin Liška --- (In reply to Jan from comment #9) > I'm using the clear linux gcc version well atleast the patches. > Maybe thats the culprit. > https://clearlinux.org/ I thought you are using Gentoo system? > > But it

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 Martin Liška changed: What|Removed |Added Status|ASSIGNED|WAITING --- Comment #6 from Martin Liška

PR85734

Hi, The attached patch tries to fix PR85734, by gating on !function_always_visible_to_compiler_p. Bootstrap+test in progress on x86_64. OK to commit if passes ? Thanks, Prathamesh 2018-05-14 Prathamesh Kulkarni PR ipa/85734 * ipa-pure-const.c

[Bug c++/85747] suboptimal code without constexpr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85747 --- Comment #7 from Antony Polukhin --- (In reply to Jakub Jelinek from comment #6) > IMHO just use constexpr if you care about compile time evaluation > guarantees, that is what it has been added for. Fair point. Overcomplicated logic on the

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #7 from Jan --- I added the option same ICE.

Re: PR85734

On Mon, 14 May 2018, Prathamesh Kulkarni wrote: > Hi, > The attached patch tries to fix PR85734, by gating on > !function_always_visible_to_compiler_p. > Bootstrap+test in progress on x86_64. > OK to commit if passes ? This looks redundant - suggest_attribute does that very same check but

[Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899 --- Comment #21 from rguenther at suse dot de --- On Sat, 12 May 2018, glisse at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899 > > --- Comment #20 from Marc Glisse --- > Created attachment 44122 > -->

[Bug lto/48200] linking shared library with LTO results in different exported symbols

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200 --- Comment #22 from Xi Ruoyao --- Created attachment 44126 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44126=edit Patch to add symver attribute, highly experimental, C++ only

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #2 from Richard Biener --- Please attach the preprocessed source.

Re: PR85734

On Mon, 14 May 2018, Prathamesh Kulkarni wrote: > On 14 May 2018 at 14:46, Richard Biener wrote: > > On Mon, 14 May 2018, Prathamesh Kulkarni wrote: > > > >> Hi, > >> The attached patch tries to fix PR85734, by gating on > >> !function_always_visible_to_compiler_p. > >>

[Bug middle-end/85751] RFE: option to align code using breakpoint instructions when unreachable

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

[Bug tree-optimization/85762] [8/9 Regression] range-v3 abstraction overhead not optimized away

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

[Bug lto/48200] linking shared library with LTO results in different exported symbols

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200 --- Comment #23 from Martin Liška --- (In reply to Xi Ruoyao from comment #22) > Created attachment 44126 [details] > Patch to add symver attribute, highly experimental, C++ only That's great you did the prototype. I'll take a look.

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 Martin Liška changed: What|Removed |Added Status|WAITING |ASSIGNED Assignee|unassigned

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

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

[Bug target/85767] [9 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu in 64-bit mode (not in 32-bit mode)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85767 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug target/85756] [9 regression] wrong code at -Os on x86-64-linux-gnu in 32-bit mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85756 --- Comment #2 from Martin Liška --- *** Bug 85767 has been marked as a duplicate of this bug. ***

[Bug tree-optimization/85758] questionable bitwise folding (missing single use check?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85758 --- Comment #2 from Richard Biener --- (In reply to Alexander Monakov from comment #0) > However since m_3 is used, this is more costly. Shouldn't this folding check > for single use of the intermediate expr? From a quick look, this is probably

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #8 from Martin Liška --- (In reply to Jan from comment #7) > I added the option same ICE. I see. Well would it be possible to provide build steps that will utilize a gentoo docker container and can help me to reproduce that?

[Bug tree-optimization/85757] tree optimizers fail to fully clean up fixed-size memcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85757 Richard Biener changed: What|Removed |Added CC||kugan at gcc dot gnu.org,

[Bug target/85769] [8/9 Regression] ICE in extract_constrain_insn, at recog.c:2205 for -mcpu=thunderx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85769 ktkachov at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW CC|

Re: [PATCH 1/2] gcc_qsort: source code changes

On Sun, 13 May 2018, H.J. Lu wrote: > This breaks bootstrap on Fedora 28/i686: > > https://gcc.gnu.org/ml/gcc-regression/2018-05/msg00088.html > > ../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’ > REORDER_45 (8, 8, 0); > ^~ >

[Bug target/85769] New: ICE in extract_constrain_insn, at recog.c:2205 for -mcpu=thunderx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85769 Bug ID: 85769 Summary: ICE in extract_constrain_insn, at recog.c:2205 for -mcpu=thunderx Product: gcc Version: unknown Status: UNCONFIRMED Keywords:

[Bug target/85756] [9 regression] wrong code at -Os on x86-64-linux-gnu in 32-bit mode

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

[Bug c++/85764] [8/9 Regression] bogus ‘this’ was not captured for this lambda function error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85764 Richard Biener changed: What|Removed |Added Keywords||rejects-valid Target Milestone|---

[Bug c++/85765] [8/9 Regression] Missing SFINAE in default template argument

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

[Bug rtl-optimization/85745] variable with asm register assignment allocated in wrong reg

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85745 --- Comment #3 from Bernd Edlinger --- just in case someone runs into the same issue, this would be the linux patch that Jakub suggested: commit 20dfb4d2eb648bd947adbb729d963f78df75ffee Author: Bernd Edlinger Date:

[Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899 --- Comment #23 from rguenther at suse dot de --- On Mon, 14 May 2018, glisse at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899 > > --- Comment #22 from Marc Glisse --- > (In reply to rguent...@suse.de from

[Bug libstdc++/84118] filesystem::path concat does not accept value_type

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

[Bug libstdc++/85772] New: __gnu_cxx::__versa_string doesn't support C++11 allocators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85772 Bug ID: 85772 Summary: __gnu_cxx::__versa_string doesn't support C++11 allocators Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: enhancement

[Bug libstdc++/85773] New: Embedded nulls in filesystem::path cause problems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85773 Bug ID: 85773 Summary: Embedded nulls in filesystem::path cause problems Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug libstdc++/71301] std::tuple move constructor

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

[PATCH] DWARF: Use DW_OP_addrx and DW_OP_constx for DWARF5.

For older DWARF and -gsplit-dwarf we want to emit DW_OP_GNU_addr_index and DW_OP_GNU_const_index, but for DWARF5 we should use DW_OP_addrx and DW_OP_constx. gcc/ChangeLog: * dwarf2out.c (dwarf_OP): Handle DW_OP_addrx and DW_OP_constx. (size_of_loc_descr): Likewise.

[Bug libstdc++/62119] dangling reference : gslice_array's copy constructor

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

[Bug libstdc++/85772] __gnu_cxx::__versa_string doesn't support C++11 allocators

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

[Bug libstdc++/85772] __gnu_cxx::__versa_string doesn't support C++11 allocators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85772 --- Comment #1 from Jonathan Wakely --- Also review it for noexcept, so that for example the copy constructor is noexcept when using the COW base: diff --git a/libstdc++-v3/include/ext/rc_string_base.h

[Bug libstdc++/85771] `std::variant<...>` insanely slow to compile compared to `union` (256 types)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85771 --- Comment #1 from Jonathan Wakely --- This should be completely unsurprising, obviously std::variant is different to a union. The type safety and other features come at a cost, and 2s isn't insane.

[PATCH 1/3] Introduce auto_string_vec class.

First part with introduction of auto_string_vec class. Martin >From c05ad6d3715fcc99e94dbe2fd3fa1ef94552bea4 Mon Sep 17 00:00:00 2001 From: marxin Date: Mon, 14 May 2018 14:00:07 +0200 Subject: [PATCH 1/3] Introduce auto_string_vec class. gcc/ChangeLog: 2018-05-14 Martin Liska

Re: [PATCH] Disallow minus in mem {+,-,&,|,^}= x; mem != 0 peepholes (PR target/85756)

On Mon, May 14, 2018 at 02:54:18PM +0200, Uros Bizjak wrote: > > --- gcc/config/i386/i386.md.jj 2018-05-11 18:44:32.0 +0200 > > +++ gcc/config/i386/i386.md 2018-05-14 13:50:28.100482520 +0200 > > @@ -19397,11 +19397,11 @@ > > (set (match_dup 0) (match_dup 2))]) > >

[Bug libstdc++/81263] Work around CWG issue 1558 (guarantee SFINAE when using `void_t`)

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

[Bug sanitizer/85774] New: Incorrect stack-use-after-scope caused by missing cleanup of shadow bytes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85774 Bug ID: 85774 Summary: Incorrect stack-use-after-scope caused by missing cleanup of shadow bytes Product: gcc Version: 8.1.1 Status: UNCONFIRMED Severity:

[PATCH 2/3] Refactoring to opt-suggestions.[ch].

Second part refactors function from gcc.c into a new class option_proposer. Martin >From c42bb9072242ab44884a71effee9398c6bcf998e Mon Sep 17 00:00:00 2001 From: marxin Date: Mon, 14 May 2018 11:47:08 +0200 Subject: [PATCH 2/3] Refactoring to opt-suggestions.[ch]. gcc/ChangeLog:

[PATCH 3/3] Come up with new --completion option.

Main part where I still need to write ChangeLog file and gcc.sh needs to be moved to bash-completions project. Martin >From cb544b3136559eb3710790dcd582d7bbf36d3792 Mon Sep 17 00:00:00 2001 From: marxin Date: Mon, 14 May 2018 11:49:52 +0200 Subject: [PATCH 3/3] Come up with new

[Bug libstdc++/67011] division by zero in std::exponential_distribution

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

[Bug libstdc++/85184] Remove __glibcxx_assert uses from std::variant

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

[Bug libstdc++/85319] std::char_traits::length does not always function in constexpr context

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

[Bug target/85770] New: [9 Regression] ICE: in lra_eliminate, at lra-eliminations.c:1439 with -march=nano-1000

x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-260223-checking-yes-rtl-df-extra-nobootstrap-amd64 Thread model: posix gcc version 9.0.0 20180514 (experimental) (GCC)

Re: [RFC] Improve tree DSE

On Mon, May 14, 2018 at 5:32 AM, Kugan Vivekanandarajah wrote: > Hi Richard, > >>> Given the simple testcases you add I wonder if you want a cheaper >>> implementation, >>> namely check that when reaching a loop PHI the only aliasing stmt in >>> its use-chain

[Bug libstdc++/85773] Embedded nulls in filesystem::path cause problems

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

[Bug libstdc++/72830] istream::seekg should not reset eofbit if -std=c++98

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

[Bug libstdc++/82452] defines macros for getc and putc

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

[Bug c++/85775] New: False positive with -Wparentheses

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85775 Bug ID: 85775 Summary: False positive with -Wparentheses Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

Re: PR85734

On 14 May 2018 at 15:06, Richard Biener wrote: > On Mon, 14 May 2018, Prathamesh Kulkarni wrote: > >> On 14 May 2018 at 14:46, Richard Biener wrote: >> > On Mon, 14 May 2018, Prathamesh Kulkarni wrote: >> > >> >> Hi, >> >> The attached patch tries to fix

[PATCH][AArch64] Implement usadv16qi and ssadv16qi standard names

Hi all, This patch implements the usadv16qi and ssadv16qi standard names. See the thread at on g...@gcc.gnu.org [1] for background. The V16QImode variant is important to get right as it is the most commonly used pattern: reducing vectors of bytes into an int. The midend expects the optab to

Re: RFC: bash completion

On 05/14/2018 02:41 PM, Martin Liška wrote: > Yes, I will work on that as soon as GCC's part is ready. Hi. I've just done branch of bash-completion where I implemented that: https://github.com/marxin/bash-completion/tree/gcc-completion Martin

Re: [PATCH] Disallow minus in mem {+,-,&,|,^}= x; mem != 0 peepholes (PR target/85756)

On Mon, May 14, 2018 at 2:48 PM, Jakub Jelinek wrote: > Hi! > > The last peephole I've recently added is as the testcase shows fundamentally > incompatible with non-commutative operations, because we need to swap the > operands. > > The pattern right before this one already is:

[Bug libstdc++/71098] uniform initialization for nested tuples work in c++11/14 mode but should only work >=c++17

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

[Bug libstdc++/69191] Wrong equality comparison between error_code and error_condition + segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191 --- Comment #17 from Jonathan Wakely --- (In reply to Chip Salzenberg from comment #16) > Still happening in 7.2 What is?

Re: [PATCH] DWARF: Emit DWARF5 forms for indirect addresses and string offsets.

On Mon, 2018-04-30 at 14:35 +0200, Mark Wielaard wrote: > We already emit DWARF5 attributes and tables for indirect addresses > and string offsets, but still use GNU forms. Add a new helper function > dwarf_FORM () for emitting the right form. > > Currently we only use the uleb128 forms. But

[Bug libstdc++/81522] c++17/old-abi/cygwin empty stringstream invalid memory access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81522 --- Comment #1 from Jonathan Wakely --- Possibly related to PR 82172 (which was due to a binutils bug) but that apparently only occurs when using LTO.

[PATCH] Adjust match.pd :s docs

Committed. Richard. 2018-05-14 Richard Biener * doc/match-and-simplify.texi: Adjust :s documentation. diff --git a/gcc/doc/match-and-simplify.texi b/gcc/doc/match-and-simplify.texi index 6bc2c47bee7..024d747cafd 100644 --- a/gcc/doc/match-and-simplify.texi +++

[Bug libstdc++/85768] [9 Regression] FreeBSD bootstrap fails due to undefined reference to 'backtrace'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85768 --- Comment #2 from Jonathan Wakely --- Yes I did suggest that. For now I think we should just disable the use of backtrace anywhere except GNU/Linux.

[PATCH] Merge SLP and non-SLP vectorization costing

One difficulty in vectorizer costing is currently that SLP and non-SLP go a different path and while the latter is costed during vectorizable_* the former is done in a separate walk over the SLP trees. This leads to defects in the former for example costing all "operations" the same rather than

[Bug libstdc++/85771] New: `std::variant<...>` insanely slow to compile compared to `union` (256 types)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85771 Bug ID: 85771 Summary: `std::variant<...>` insanely slow to compile compared to `union` (256 types) Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity:

[Bug libstdc++/62119] dangling reference : gslice_array's copy constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62119 --- Comment #4 from Jonathan Wakely --- PR 63314 points out the same problem exists in mask_array and indirect_array.

[Bug libstdc++/63314] valarray mask/indices refers to temporary

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

[Bug libstdc++/62119] dangling reference : gslice_array's copy constructor

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

Re: [PATCH] PR 85075, Fix PowerPC __float182/__ibm128 types and mangling

On Tue, Apr 24, 2018 at 05:42:39PM +, Joseph Myers wrote: > On Mon, 16 Apr 2018, Segher Boessenkool wrote: > > > > The manglings that are now used are: > > > > > > For -mabi=ieeelongdouble: > > > > > > __float128 "u10__float128" > > > __ibm128"u8__ibm128" > > > long

Re: [PATCH] DWARF: Add header for .debug_str_offsets table for dwarf_version 5.

On Mon, 2018-04-30 at 14:34 +0200, Mark Wielaard wrote: > DWARF5 defines a small header for .debug_str_offsets.  Since we only use > it for split dwarf .dwo files we don't need to keep track of the actual > index offset in an attribute. Ping. gcc/ChangeLog: * dwarf2out.c

[Bug libstdc++/81256] basic_filebuf::close doesn't propagate exceptions

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

[Bug libstdc++/83891] std::filesystem::path::is_absolute for Windows

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

[Bug target/85769] [8/9 Regression] ICE in extract_constrain_insn, at recog.c:2205 for -mcpu=thunderx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85769 --- Comment #2 from Tamar Christina --- It's not r250673, That was committed 2017-07-28 and a GCC built 2017-08-17 does the correct thing for non-Armv8.2-a. It promotes the fp16 values to 32 bits does the operations and converts them back to

[PATCH] Disallow minus in mem {+,-,&,|,^}= x; mem != 0 peepholes (PR target/85756)

Hi! The last peephole I've recently added is as the testcase shows fundamentally incompatible with non-commutative operations, because we need to swap the operands. The pattern right before this one already is: (define_peephole2 [(parallel [(set (match_operand:SWI 0 "register_operand")

Re: [PATCH] Disallow minus in mem {+,-,&,|,^}= x; mem != 0 peepholes (PR target/85756)

On Mon, May 14, 2018 at 2:48 PM, Jakub Jelinek wrote: > Hi! > > The last peephole I've recently added is as the testcase shows fundamentally > incompatible with non-commutative operations, because we need to swap the > operands. > > The pattern right before this one already is:

[Bug libstdc++/67554] runtime error in valarray (NULL passed to memcpy)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67554 Jonathan Wakely changed: What|Removed |Added Keywords||wrong-code

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

On Wed, Apr 25, 2018 at 7:54 PM, H.J. Lu wrote: > When address of packed member of struct or union is taken, it may result > in an unaligned pointer value. This patch adds -Waddress-of-packed-member > to check alignment at pointer assignment and warn unaligned address as >

[Bug libstdc++/82966] node_handle swap fails to compile

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

[PATCH, rs6000] Improved Documentation of Built-in Functions Part 2

The focus of this patch is to restructure the section headers within the PowerPC portion of the extend.texi documentation file. Restructuring section headers prepares the foundation for subsequent documentation improvements which will be delivered in follow-on patches. I have bootstrapped and

Re: [Patch / RFC] Rename POINTER_TYPE_P to INDIRECT_TYPE_P ?

On 05/11/2018 11:06 AM, Jakub Jelinek wrote: If any change needs to be done, yeah. For the middle-end, having POINTER_TYPE_P including reference type is highly desirable, otherwise people will just forget to handle REFERENCE_TYPE; after all, useless_type_conversion_p says that POINTER_TYPE <->

[Bug sanitizer/85777] [7/8 Regression] -fsanitize=undefined makes a -Wmaybe-uninitialized warning disappear

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777 --- Comment #1 from Vincent Lefèvre --- I've cleaned up the testcase: int d; int h(void); void e(void) { int f[2]; int g = 0; if (d) g++; if (d == 1) f[g++] = 2; (void) (f[0] || (g && h())); } Now: cventin% gcc-snapshot

[Bug libstdc++/67554] runtime error in valarray (NULL passed to memcpy)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67554 --- Comment #1 from Jonathan Wakely --- Author: redi Date: Mon May 14 15:35:06 2018 New Revision: 260229 URL: https://gcc.gnu.org/viewcvs?rev=260229=gcc=rev Log: PR libstdc++/67554 Do not pass null pointers to memcpy PR libstdc++/67554

[PATCH] PR libstdc++/67554 Do not pass null pointers to memcpy

PR libstdc++/67554 * include/bits/valarray_array.h (_Array_copy_ctor<_Tp, true>) (_Array_copier<_Tp, true>): Do not pass null pointers to memcpy. Tested powerpc64le-linux, committed to trunk. Backports to follow. There's no new test for this, as we're not able to use

Re: [PATCH] Disallow minus in mem {+,-,&,|,^}= x; mem != 0 peepholes (PR target/85756)

On Mon, May 14, 2018 at 5:08 PM, Marek Polacek wrote: > On Mon, May 14, 2018 at 03:07:54PM +0200, Jakub Jelinek wrote: >> On Mon, May 14, 2018 at 02:54:18PM +0200, Uros Bizjak wrote: >> > > --- gcc/config/i386/i386.md.jj 2018-05-11 18:44:32.0 +0200 >> > > +++

Re: PR85734

On May 14, 2018 2:30:27 PM GMT+02:00, Prathamesh Kulkarni wrote: >On 14 May 2018 at 15:06, Richard Biener wrote: >> On Mon, 14 May 2018, Prathamesh Kulkarni wrote: >> >>> On 14 May 2018 at 14:46, Richard Biener wrote: >>> >

  1   2   >