[Bug target/48595] score-elf fails to build with --enable-werror-always

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48595 Eric Gallager changed: What|Removed |Added Keywords||build Status|UNCONFIRMED

[Bug c++/80078] Incorrect classification of address of volatile as not constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80078 --- Comment #3 from Christopher Head --- I tried 9.1 at gcc.godbolt.org and it looks like this is fixed. Anyone else care to take a look? If there are no further comments, I guess I’ll close this ticket in a few days.

[Bug c++/91397] -Wstringop-overflow specified bound 18446744073709551615 exceeds maximum object size 9223372036854775807

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

Re: [PATCH] fix and improve strlen conditional handling of merged stores (PR 91183, 91294, 91315)

On 7/31/19 6:36 PM, Martin Sebor wrote: > More extensive testing of the last week's strlen patch for > PR91183 on various non-mainstream targets and with better tests > has exposed a few gaps and a couple of bugs.  The attached patch > addresses all in one change.  I considered splitting it up but

[Bug c++/90473] gcc does not call function in comma operator for default argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90473 Marek Polacek changed: What|Removed |Added Keywords||patch --- Comment #4 from Marek Polacek

C++ PATCH for c++/90473 - wrong code with nullptr in default argument

This is a wrong-code bug where we are throwing away the function call in the default argument here: void fn1 (void* p = (f(), nullptr)) { } and thus dropping the possible side-effects of that call to the floor. That happens because check_default_argument returns nullptr_node when it sees a

Re: Start implementing -frounding-math

On Mon, 24 Jun 2019, Marc Glisse wrote: > > OK, fair enough. I just hoped that global > > > > double x = 1.0/3.0; > > > > do not become runtime initializers with -frounding-math ... > > Ah, I wasn't thinking of globals. Ignoring the new pragma fenv_round, which I > guess could affect this

[PATCH,Fortran] -- Tidy up the BOZ rewrite

The attach patch has been regression tested on x86_64-*-freebsd. It does a number of things. 1) It tightens the adherence to F2018 Fortran standard. For example, this program and execute with gfortran 9 and older. program foo integer i data i/z'40490adf'/ ! Explicit

Re: Expansion of narrowing math built-ins into power instructions

On Thu, 8 Aug 2019, Segher Boessenkool wrote: > These current patterns all take the same mode for all inputs and outputs > (that's what 3 indicates, say, fadddf3). You will need to define > something that takes two SFs in and produces a DF. That cannot really For example, md.texi describes

[PATCH] rs6000: Add ordered compares (PR58684)

This adds ordered compares to most unordered compares, in rs6000. It does not handle the XL_COMPAT double-double compares yet (that is the pattern with 16 operands). It also does not handle the vector compare instructions; those only exist as unordered, for the equality comparisons, or as

[Bug driver/80545] option -Wstringop-overflow not recognized by Fortran

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

[Bug ada/82813] warning: '.builtin_memcpy' writing between 2 and 6 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82813 Bug 82813 depends on bug 80545, which changed state. Bug 80545 Summary: option -Wstringop-overflow not recognized by Fortran https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80545 What|Removed |Added

[Bug tree-optimization/89176] Vectorizer fails to consider narrower vector width for res[i] = v1[i] < v2[i] ? v2[i] : v1[i]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89176 H.J. Lu changed: What|Removed |Added CC||crazylht at gmail dot com --- Comment #2 from

gcc-7-20190808 is now available

Snapshot gcc-7-20190808 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20190808/ 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

Re: [PATCH] Sync MIPS support from libffi master repository

On 8/8/19 4:18 PM, Aurelien Jarno wrote: > > It is used by libgo, but it seems to be the last user. Ah, yes, I should have remembered libgo. And it links via ../../blahblah. Thanks for digging into it. So, yea, we need it. So I think the best path forward is to just resync everything to the

Re: [PATCH] Sync MIPS support from libffi master repository

On 2019-08-08 15:00, Jeff Law wrote: > On 8/8/19 2:56 PM, Aurelien Jarno wrote: > > On 2019-08-08 14:41, Jeff Law wrote: > >> On 8/5/19 2:33 PM, Aurelien Jarno wrote: > >>> This updates the libffi MIPS support up to commit 746dbe3a6a79, with the > >>> exception of commit bd72848c7af9 which

[Bug c++/90473] gcc does not call function in comma operator for default argument

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

Re: [Patch, ira] Invalid assert in reload1.c::finish_spills?

On 8/7/19 8:15 AM, Vladimir Makarov wrote: > On 8/7/19 7:36 AM, senthilkumar.selva...@microchip.com wrote: >> Hi, >> >>    gcc/testsuite/c-c++-common/pr60101.c fails with an ICE for the >>    avr target, because of a gcc_assert firing at reload1.c:4233 >> >>    The assert (in the patch below)

Re: [PATCH 2/9] ifcvt: Use enum instead of transform_name string.

On 8/6/19 2:42 PM, Richard Sandiford wrote: > Robin Dapp writes: >> This patch introduces an enum for ifcvt's various noce transformations. >> As the transformation might be queried by the backend, I find it nicer >> to allow checking for a proper type instead of a string comparison. > > TBH I

Re: [PATCH v2] Use edge->indirect_unknown_callee in cgraph_edge::make_direct (PR ipa/89330).

On 8/8/19 1:41 AM, Martin Liška wrote: > On 8/8/19 12:08 AM, Jeff Law wrote: >> Would this possibly be the cause of this error building the kernel: > > Probably yes. You see the same as H.J.: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91334 > > Can you please create a pre-processed source

[Bug c++/90473] gcc does not call function in comma operator for default argument

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

[Bug c++/91394] C++ ABI incompatibility (stdexcept)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91394 --- Comment #4 from Jonathan Wakely --- Some programs which happen to not use any new features might work with an older version of libstdc++.so but that is not guaranteed, and definitely not supported. Removing one or two functions from a

[Bug driver/91406] New: gcc -Q -v lies about what flags are enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91406 Bug ID: 91406 Summary: gcc -Q -v lies about what flags are enabled Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [PATCH] i386: Roundeven expansion for SSE4.1+

On 7/27/19 3:04 AM, Uros Bizjak wrote: > On Wed, Jul 24, 2019 at 12:43 PM Tejas Joshi wrote: >> >> Hi. >> This is a patch that Uros suggested for roundeven expansion, here. >> Thanks for the heads up. >> >> I have rerun the testsuite on

Re: [PATCH] Provide proper error message for -flto=abcd.

On 7/29/19 7:36 AM, Martin Liška wrote: > Hi. > > The patch is about proper error message for situations where > user give a wrong argument to -flto option. > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? > Thanks, > Martin > >

Re: [PATCH] [MIPS] Add missing const qualifier in MSA ld intrinsic documentation

On 7/26/19 3:12 AM, Mihailo Stojanovic wrote: > From: Mihailo Stojanovic > > The documentation is not reflecting the fact that the first argument of > MSA ld intrinsics is a const void pointer. > > gcc/ > > * doc/extend.texi: Add const qualifier to ld intrinsics. THanks. Installed. jeff

Re: [PATCH] Sync MIPS support from libffi master repository

On 8/8/19 2:56 PM, Aurelien Jarno wrote: > On 2019-08-08 14:41, Jeff Law wrote: >> On 8/5/19 2:33 PM, Aurelien Jarno wrote: >>> This updates the libffi MIPS support up to commit 746dbe3a6a79, with the >>> exception of commit bd72848c7af9 which prefixes the ALIGN macro with >>> FFI_ for all ports.

Re: [PATCH] Sync MIPS support from libffi master repository

On 2019-08-08 14:41, Jeff Law wrote: > On 8/5/19 2:33 PM, Aurelien Jarno wrote: > > This updates the libffi MIPS support up to commit 746dbe3a6a79, with the > > exception of commit bd72848c7af9 which prefixes the ALIGN macro with > > FFI_ for all ports. > > > > These patches, with the exception

Re: [PATCH] Add --with-static-standard-libraries to the top level

On 8/5/19 12:02 PM, Tom Tromey wrote: > gdb should normally not be linked with -static-libstdc++. Currently > this has not caused problems, but it's incompatible with catching an > exception thrown from a shared library -- and a subsequent patch > changes gdb to do just this. > > This patch adds

[Bug target/47779] Problem cross-compiling trunk for bfin

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47779 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

Re: [PATCH] Sync MIPS support from libffi master repository

On 8/5/19 2:33 PM, Aurelien Jarno wrote: > This updates the libffi MIPS support up to commit 746dbe3a6a79, with the > exception of commit bd72848c7af9 which prefixes the ALIGN macro with > FFI_ for all ports. > > These patches, with the exception of the softfloat one, have been used > on the

Re: Use predicates for RTL objects

On 8/8/19 12:46 PM, Jakub Jelinek wrote: > On Thu, Aug 08, 2019 at 02:35:27PM -0400, Arvind Sankar wrote: >> Surely there's general agreement on using REG_P etc? I don't see anyone > > No objections from me for using REG_P and other *_P macros more. Right. These are convenience macros and I

Re: Use predicates for RTL objects

On 8/8/19 11:42 AM, Arvind Sankar wrote: > On Thu, Aug 08, 2019 at 10:04:14AM -0500, Segher Boessenkool wrote: >> On Wed, Aug 07, 2019 at 02:58:12PM -0400, Arvind Sankar wrote: >> code does is cheap. With "x->is_a (PLUS)", who knows what is happening That's not my point -- my point was

[Bug c++/91394] C++ ABI incompatibility (stdexcept)

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

Re: Use predicates for RTL objects

On 8/8/19 11:06 AM, Arvind Sankar wrote: > On Thu, Aug 08, 2019 at 08:31:28AM -0600, Jeff Law wrote: >> True, but they could be. When David was working in this space a few >> years ago I concluded that the main value in sub-classing the various >> RTL operators just wansn't worth the effort.

[Bug libgcc/91379] internal compiler error __gcov_fork

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91379 --- Comment #4 from Clinton Bunch --- Setting the CFLAGS and CXXFLAGS to -O0 -g as suggested didn't help. It still blew up at the same point building libgcc. Interestingly, I noticed that it doesn't blow up if the code is compiled in -mlp64

Re: Expansion of narrowing math built-ins into power instructions

Hi! On Fri, Aug 09, 2019 at 12:14:54AM +0530, Tejas Joshi wrote: > > In GCC (in rs6000.md) we have the "*add3_fpr" and similar insns, > > which could be extended to allow DF inputs with an SF output; it doesn't > > yet allow it. > > This might be very lousy but I am confused with the optabs and

Re: Indirect memory addresses vs. lra

On 8/8/19 1:19 PM, Segher Boessenkool wrote: > On Thu, Aug 08, 2019 at 01:30:41PM -0400, Paul Koning wrote: >> >> >>> On Aug 8, 2019, at 1:21 PM, Segher Boessenkool >>> wrote: >>> >>> On Thu, Aug 08, 2019 at 12:43:52PM -0400, Paul Koning wrote: > On Aug 8, 2019, at 12:25 PM, Vladimir Makarov

[PATCH 1/2] rs6000: Use iterators in more DFP patterns

I noticed some patterns in dfp.md could use the D64_D128 iterator but don't yet. This converts all remaining simple cases. Tested on powerpc64-linux {-m32,-m64}; committing to trunk. Segher 2019-08-08 Segher Boessenkool * config/rs6000/dfp.md (D64_D128): Move earlier in the file.

[PATCH 2/2] rs6000: Rename DFP iterator and attr to DDTD and q

This is more in line with the other iterators we have, and a bit easier to read and write. Tested on powerpc64-linux {-m32,-m64}; committing to trunk. Segher 2019-08-08 Segher Boessenkool * config/rs6000/dfp.md (D64_D128): Rename to ... (DDTD): ... this, throughout.

[Bug c++/91405] [concepts] internal compiler error: in synthesize_implicit_template_parm, at cp/parser.c:41206

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91405 --- Comment #1 from Michael de Lang --- Correction, the reported line number for 7.4.0 is cp.parser.c:38874

[Bug c++/91405] New: [concepts] internal compiler error: in synthesize_implicit_template_parm, at cp/parser.c:41206

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91405 Bug ID: 91405 Summary: [concepts] internal compiler error: in synthesize_implicit_template_parm, at cp/parser.c:41206 Product: gcc Version: 9.1.0

Re: C++ PATCH for c++/91264 - detect modifying const objects in constexpr

On Thu, Aug 08, 2019 at 11:06:17AM -0400, Jason Merrill wrote: > On 8/6/19 3:20 PM, Marek Polacek wrote: > > On Mon, Aug 05, 2019 at 03:54:19PM -0400, Jason Merrill wrote: > > > On 7/31/19 3:26 PM, Marek Polacek wrote: > > > > One of the features of constexpr is that it doesn't allow UB; and such

[Bug tree-optimization/91227] pointer relational expression not folded but equivalent inequality is

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91227 --- Comment #19 from Martin Sebor --- That's a valid concern. Issuing a warning (either at the same time as or in lieu of the folding) would be a way to detect and prevent these kinds of problems. Exposing it to enough code (like in a whole

Re: Indirect memory addresses vs. lra

On Thu, Aug 08, 2019 at 01:30:41PM -0400, Paul Koning wrote: > > > > On Aug 8, 2019, at 1:21 PM, Segher Boessenkool > > wrote: > > > > On Thu, Aug 08, 2019 at 12:43:52PM -0400, Paul Koning wrote: > >>> On Aug 8, 2019, at 12:25 PM, Vladimir Makarov wrote: > >>> The old reload (reload[1].c)

Re: Indirect memory addresses vs. lra

On Thu, Aug 08, 2019 at 01:25:27PM -0400, Paul Koning wrote: > > On Aug 8, 2019, at 1:21 PM, Segher Boessenkool > > wrote: > > On Thu, Aug 08, 2019 at 12:43:52PM -0400, Paul Koning wrote: > >> Indirect addressing is a key feature in size-optimized code. > > > > That doesn't mean that LRA has to

[Bug target/91229] RISC-V ABI problem with zero-length bit-fields and float struct fields

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

[Bug target/91229] RISC-V ABI problem with zero-length bit-fields and float struct fields

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91229 --- Comment #3 from Jim Wilson --- Author: wilson Date: Thu Aug 8 19:04:56 2019 New Revision: 274215 URL: https://gcc.gnu.org/viewcvs?rev=274215=gcc=rev Log: RISC-V: Fix C ABI for flattened struct with 0-length bitfield. gcc/

[Bug tree-optimization/91403] GCC fails with ICE.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91403 Serge Belyshev changed: What|Removed |Added CC||belyshev at depni dot sinp.msu.ru ---

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 01:26:42PM -0500, Segher Boessenkool wrote: > LABEL_REF_P works out nicely because it is referring to something that > is data, is not an operator. "Leaves" in an RTL expression, if you want > to look at it that way. > > Predicates for other RTX codes aren't always as

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 02:35:27PM -0400, Arvind Sankar wrote: > Surely there's general agreement on using REG_P etc? I don't see anyone No objections from me for using REG_P and other *_P macros more. > objecting to it, and that's all the patchset does: to avoid any > confusion the second half

Re: Indirect memory addresses vs. lra

On 2019-08-08 12:43 p.m., Paul Koning wrote: On Aug 8, 2019, at 12:25 PM, Vladimir Makarov wrote: On 2019-08-04 3:18 p.m., John Darrington wrote: I'm trying to write a back-end for an architecture (s12z - the ISA you can download from [1]). This arch accepts indirect memory addresses.

Re: Expansion of narrowing math built-ins into power instructions

Hi. It took some time for me to finish with the folding part for fadd variants and till it is reviewed, I want to move ahead with power8/9 expansions on top of the current fadd patch. > In GCC (in rs6000.md) we have the "*add3_fpr" and similar insns, > which could be extended to allow DF inputs

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 08:14:01PM +0200, Jakub Jelinek wrote: > On Thu, Aug 08, 2019 at 01:12:33PM -0400, Arvind Sankar wrote: > > On Thu, Aug 08, 2019 at 03:04:53PM +, Michael Matz wrote: > > > Hi, > > > > > > On Wed, 7 Aug 2019, Arvind Sankar wrote: > > > > > > > => x->is_a (REG)

[Bug tree-optimization/91403] GCC fails with ICE.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91403 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org,

[Bug c++/91334] [10 Regression] ICE in propagate_necessity at gcc/tree-ssa-dce.c:813 since r273791

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

[Bug ipa/91404] New: [10 Regression] internal compiler error: Segmentation fault

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

[Bug c++/91402] PowerPC unecessary -Wignored-attriubte warnings on template specialization with -mlongcall

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91402 --- Comment #1 from Andrew Kaster --- As a note, I was able to reproduce using godbolt, but they don't have very recent versions of gcc for powerpc: https://godbolt.org/z/20lNhf Of the available compilers: No warnings: power64le clang (trunk)

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 01:42:40PM -0400, Arvind Sankar wrote: > On Thu, Aug 08, 2019 at 10:04:14AM -0500, Segher Boessenkool wrote: > But there is really nothing more or less obvious about it. That depends on what you are used to seeing, a lot. > It's easy to > go look at the code, as you

[Bug tree-optimization/91403] New: GCC fails with ICE.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91403 Bug ID: 91403 Summary: GCC fails with ICE. Product: gcc Version: tree-ssa Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization

[Bug tree-optimization/91178] [9 Regression] Infinite recursion in split_constant_offset in slp after r260289

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91178 --- Comment #17 from Vsevolod Livinskiy --- (In reply to Serge Belyshev from comment #16) > (In reply to Vsevolod Livinskiy from comment #15) > > I don't know if it is the same error or not, but the reproducer looks > > similar. > > This one is

[Bug go/86535] FreeBSD/PowerPC64 - Building Go Frontend support for gcc 7.3.0 fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86535 --- Comment #23 from Ian Lance Taylor --- Look for _kern in runtime.inc. See what struct it is part of. The struct is likely defined in the generated file runtime_sysinfo.go. You may need to modify libgo/mkrsysinfo.sh to not add that struct

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 01:12:33PM -0400, Arvind Sankar wrote: > On Thu, Aug 08, 2019 at 03:04:53PM +, Michael Matz wrote: > > Hi, > > > > On Wed, 7 Aug 2019, Arvind Sankar wrote: > > > > > => x->is_a (REG) > > > > Oh god, please no. Currently at least the RTL parts of GCC still have >

[Bug c++/79520] Spurious caching for constexpr arguments

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

[Bug c++/79520] Spurious caching for constexpr arguments

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79520 --- Comment #3 from Marek Polacek --- Author: mpolacek Date: Thu Aug 8 17:54:58 2019 New Revision: 274214 URL: https://gcc.gnu.org/viewcvs?rev=274214=gcc=rev Log: PR c++/79520 * g++.dg/cpp1y/constexpr-79520.C: New test. Added:

C++ PATCH to add test for c++/79520

Fixed by r255788. Tested on x86_64-linux, applying to trunk. 2019-08-08 Marek Polacek PR c++/79520 * g++.dg/cpp1y/constexpr-79520.C: New test. --- /dev/null +++ gcc/testsuite/g++.dg/cpp1y/constexpr-79520.C @@ -0,0 +1,11 @@ +// PR c++/79520 +// { dg-do compile { target c++14

[Bug c++/91402] New: PowerPC unecessary -Wignored-attriubte warnings on template specialization with -mlongcall

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91402 Bug ID: 91402 Summary: PowerPC unecessary -Wignored-attriubte warnings on template specialization with -mlongcall Product: gcc Version: 7.4.0 Status: UNCONFIRMED

[Bug c++/79520] Spurious caching for constexpr arguments

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

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 10:04:14AM -0500, Segher Boessenkool wrote: > On Wed, Aug 07, 2019 at 02:58:12PM -0400, Arvind Sankar wrote: > > > > > code does is cheap. With "x->is_a (PLUS)", who knows what is > > > > > happening > > > That's not my point -- my point was that it is *obvious* the way

Re: Indirect memory addresses vs. lra

> On Aug 8, 2019, at 1:21 PM, Segher Boessenkool > wrote: > > On Thu, Aug 08, 2019 at 12:43:52PM -0400, Paul Koning wrote: >>> On Aug 8, 2019, at 12:25 PM, Vladimir Makarov wrote: >>> The old reload (reload[1].c) supports such addressing. As modern >>> mainstream architectures have no

[Bug c++/88330] Implement P0542R5, P1289R1, C++20 contract based programming.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88330 Marek Polacek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c++/88323] implement C++20 language features.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323 Bug 88323 depends on bug 88330, which changed state. Bug 88330 Summary: Implement P0542R5, P1289R1, C++20 contract based programming. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88330 What|Removed |Added

Re: Indirect memory addresses vs. lra

> On Aug 8, 2019, at 1:21 PM, Segher Boessenkool > wrote: > > On Thu, Aug 08, 2019 at 12:43:52PM -0400, Paul Koning wrote: >>> On Aug 8, 2019, at 12:25 PM, Vladimir Makarov wrote: >>> The old reload (reload[1].c) supports such addressing. As modern >>> mainstream architectures have no

Re: Indirect memory addresses vs. lra

On Thu, Aug 08, 2019 at 12:43:52PM -0400, Paul Koning wrote: > > On Aug 8, 2019, at 12:25 PM, Vladimir Makarov wrote: > > The old reload (reload[1].c) supports such addressing. As modern > > mainstream architectures have no this kind of addressing, it was not > > implemented in LRA. > > Is

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 03:04:53PM +, Michael Matz wrote: > Hi, > > On Wed, 7 Aug 2019, Arvind Sankar wrote: > > > => x->is_a (REG) > > Oh god, please no. Currently at least the RTL parts of GCC still have > mostly a consistent and obvious style, which is a good thing. I have no >

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 08:31:28AM -0600, Jeff Law wrote: > True, but they could be. When David was working in this space a few > years ago I concluded that the main value in sub-classing the various > RTL operators just wansn't worth the effort. Instead we focused on > starting to tear apart

[Bug c++/88102] Implement P0542R5, C++20 contracts

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

[Bug c++/88323] implement C++20 language features.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323 Bug 88323 depends on bug 88102, which changed state. Bug 88102 Summary: Implement P0542R5, C++20 contracts https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88102 What|Removed |Added

[Bug c/91398] Possible missed optimization: Can a pointer be passed as hidden pointer in x86-64 System V ABI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91398 --- Comment #1 from joseph at codesourcery dot com --- ABI question: is a function that returns a value through such a hidden pointer required not to write anything to the storage pointed to until it knows that it will definitely be returning

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 10:42:06AM -0600, Jeff Law wrote: > On 8/5/19 12:29 PM, Segher Boessenkool wrote: > > On Mon, Aug 05, 2019 at 02:14:50PM -0400, Arvind Sankar wrote: > >> On Mon, Aug 05, 2019 at 12:48:46PM -0500, Segher Boessenkool wrote: > >>> First: do you have a copyright assignment?

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 10:42:06AM -0600, Jeff Law wrote: > On 8/5/19 12:29 PM, Segher Boessenkool wrote: > > On Mon, Aug 05, 2019 at 02:14:50PM -0400, Arvind Sankar wrote: > >> On Mon, Aug 05, 2019 at 12:48:46PM -0500, Segher Boessenkool wrote: > >>> First: do you have a copyright assignment?

Re: Use predicates for RTL objects

On Thu, Aug 08, 2019 at 10:42:06AM -0600, Jeff Law wrote: > -/* Predicate yielding true iff X is an rtx for a double-int. */ > +/* Predicate yielding true iff X is an rtx for a floating point > constant. */ > #define CONST_DOUBLE_AS_FLOAT_P(X) \ > (GET_CODE (X) ==

[PATCH 2/3] [og9] Fix configury for AMD GCN testing

This patch updates the configury for AMD GCN for version of the patch "Forward -foffload=[...] from the driver (compile-time) to libgomp (run-time)" currently applied to the og9 branch. This is necessary for OpenACC testing on AMD GCN to work properly, at least in our test environment. Julian

[PATCH 3/3] [og9] Use a single worker for OpenACC on AMD GCN

This patch sets the number of workers (per-gang) to 1 for AMD GCN, as a stop-gap measure until the middle-end transformations to enable multiple workers have been applied. Julian ChangeLog gcc/ * config/gcn/gcn.c (gcn_goacc_validate_dims): Ensure flag_worker_partitioning

[PATCH 1/3] [og9] Add missing exec_params libgomp plugin entry points

This patch adds two missing (dummy) entry points to the GCN libgomp plugin. These are not used at present, because we have not enabled the function parameter flattening transformation that uses these entry points on GCN. Julian ChangeLog libgomp/ * plugin/plugin-gcn.c

[PATCH 0/3] [og9] Initial OpenACC fixes for AMD GCN

Hi, This patch series provides basic support for OpenACC on AMD GCN, using a single worker (per-gang) only. This is enough to improve test results significantly over the previous state on the og9 branch, but bugs still remain. Further commentary attached to individual patches. Tested with

[Bug middle-end/91395] Report an uninitialized variable on its initialization statement (setjmp)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91395 --- Comment #5 from joseph at codesourcery dot com --- It's *accessible objects* whose value on second return from setjmp is the same as when longjmp is called (unless non-volatile, automatic storage duration and changed between setjmp and

Re: [C] Fix bogus nested enum error message

On 8/5/19 3:00 AM, Richard Sandiford wrote: > For: > > enum a { A }; > enum a { B }; > > we emit a bogus error about nested definitions before the real error: > > foo.c:2:6: error: nested redefinition of ‘enum a’ > 2 | enum a { B }; > | ^ > foo.c:2:6: error: redeclaration

[Bug c++/81930] [meta-bug] Issues with -Weffc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81930 Bug 81930 depends on bug 57854, which changed state. Bug 57854 Summary: Would like to have a warning for virtual overrides without C++11 "override" keyword https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57854 What|Removed

[Bug c++/57854] Would like to have a warning for virtual overrides without C++11 "override" keyword

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57854 Marek Polacek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

Re: [PATCH] issue a correct fix-it hint for bad argument in GCC diagnostics (PR 80619)

On 8/5/19 11:51 AM, Martin Sebor wrote: > When the argument to a directive with a length modifier like %lu > in a call to a GCC diagnostic function such as warning()) is not > of the right integer type, GCC suggests to replace the length > modifier in the directive with 'w'.  For instance: > >  

Re: Indirect memory addresses vs. lra

> On Aug 8, 2019, at 12:25 PM, Vladimir Makarov wrote: > > > On 2019-08-04 3:18 p.m., John Darrington wrote: >> I'm trying to write a back-end for an architecture (s12z - the ISA you can >> download from [1]). This arch accepts indirect memory addresses. That is >> to >> say, those of

[Bug c++/80061] error on constexpr function with an unevaluated throw

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

Re: Use predicates for RTL objects

On 8/5/19 12:29 PM, Segher Boessenkool wrote: > On Mon, Aug 05, 2019 at 02:14:50PM -0400, Arvind Sankar wrote: >> On Mon, Aug 05, 2019 at 12:48:46PM -0500, Segher Boessenkool wrote: >>> First: do you have a copyright assignment? See >>> https://gcc.gnu.org/contribute.html >>> for instructions.

[Bug tree-optimization/91227] pointer relational expression not folded but equivalent inequality is

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91227 --- Comment #18 from joseph at codesourcery dot com --- I don't expect people to do such comparisons with addresses of local variables directly. It is plausible that they have a memmove-like function, and once it gets inlined the compiler can

Re: Run the combine part of combine_and_move_insns even if -fsched-pressure

On 8/7/19 12:16 PM, Richard Sandiford wrote: > The main IRA routine includes the code: > > /* Don't move insns if live range shrinkage or register > pressure-sensitive scheduling were done because it will not > improve allocation but likely worsen insn scheduling. */ > if (optimize

Re: [Committed] PR fortran/54072 -- More fun with BOZ

On Thu, Aug 08, 2019 at 09:23:11AM -0700, Steve Kargl wrote: > On Thu, Aug 08, 2019 at 10:11:39AM +0100, Mark Eggleston wrote: > > > > >> Comparisons with BOZ constants was allowed using 9.1 with > > >> -Wconversion-extra: > > >> > > >>     5 | if (i4 .eq. z'1000') then > > >>   | 

Re: [PATCH] Implement -fopt-info support for IPA ICF.

On 8/8/19 7:04 AM, Martin Liška wrote: > Hi. > > As requested by Richi, I'm suggesting to use new dump_printf > optimization info infrastructure. > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? > Thanks, > Martin > > gcc/ChangeLog: > >

Re: Indirect memory addresses vs. lra

On 2019-08-04 3:18 p.m., John Darrington wrote: I'm trying to write a back-end for an architecture (s12z - the ISA you can download from [1]). This arch accepts indirect memory addresses. That is to say, those of the form (mem (mem (...))) and although my TARGET_LEGITIMATE_ADDRESS

Re: [Committed] PR fortran/54072 -- More fun with BOZ

On Thu, Aug 08, 2019 at 10:11:39AM +0100, Mark Eggleston wrote: > > >> Comparisons with BOZ constants was allowed using 9.1 with > >> -Wconversion-extra: > >> > >>     5 | if (i4 .eq. z'1000') then > >>   |    1 > >> Warning: Conversion from INTEGER(4) to INTEGER(16) at

  1   2   3   >