[Bug c++/85662] New: regression since 6: "error: non-constant condition for static assertion" from __builtin_offsetof in C++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85662 Bug ID: 85662 Summary: regression since 6: "error: non-constant condition for static assertion" from __builtin_offsetof in C++ Product: gcc Version: unknown Status:

[Bug c/85661] New: double comparison illegally statically reduced

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85661 Bug ID: 85661 Summary: double comparison illegally statically reduced Product: gcc Version: 7.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug demangler/85660] New: Signed Integer Overflow (79257474)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85660 Bug ID: 85660 Summary: Signed Integer Overflow (79257474) Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: demangler

[Bug c++/85618] [8/9 Regression] Zero initialized non constant stack array causes internal compile error

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

[Bug c++/85659] New: ICE with inline assembly inside virtual function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85659 Bug ID: 85659 Summary: ICE with inline assembly inside virtual function Product: gcc Version: 6.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug bootstrap/85658] gcc-8.0.1 stopped validating --with-arch= flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85658 --- Comment #2 from Sergei Trofimovich --- Created attachment 44074 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44074=edit 93_all_arm-arch.patch

[Bug bootstrap/85658] gcc-8.0.1 stopped validating --with-arch= flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85658 --- Comment #1 from Sergei Trofimovich --- Looks like the bug is in operator precedence in awk between '!' and 'in'. This makes above tests to recover: diff --git a/gcc/config/arm/parsecpu.awk b/gcc/config/arm/parsecpu.awk index

Re: [PATCH] Backport of RISC-V support for libffi

On 03/20/2018 03:50 AM, Andreas Schwab wrote: This is a backport of (the only difference to upstream is s/FFI_ALIGN/ALIGN/, as we don't have commit bd72848c7a). This is needed for libgo. OK. You might have to update the patch, as at least

gcc-8-20180504 is now available

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

[Bug driver/85658] New: gcc-8.0.1 stopped validating --with-arch= flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85658 Bug ID: 85658 Summary: gcc-8.0.1 stopped validating --with-arch= flag Product: gcc Version: 8.0.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

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

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 patch work, I had to add 4 new emulations because we have 6 ABIs. This

[Bug target/85657] Make __ibm128 a separate type, even if long double uses the IBM double-double format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85657 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/85657] New: Make __ibm128 a separate type, even if long double uses the IBM double-double format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85657 Bug ID: 85657 Summary: Make __ibm128 a separate type, even if long double uses the IBM double-double format Product: gcc Version: 9.0 Status: UNCONFIRMED

ANN: gcc-python-plugin 0.16

gcc-python-plugin is a plugin for GCC 4.6 onwards which embeds the CPython interpreter within GCC, allowing you to write new compiler warnings in Python, generate code visualizations, etc. This releases adds support for gcc 7 and gcc 8 (along with continued support for gcc 4.6, 4.7, 4.8, 4.9, 5

[Bug fortran/85407] Replace gcc_assert in module.c:read_module by more helpful diagnostics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85407 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug c++/85587] [8/9 Regression] bogus error: ‘F’ was not declared in this scope

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

[Bug c++/85305] Parameter pack expression in lambda capture list fails as part of a fold expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85305 --- Comment #3 from Jason Merrill --- Author: jason Date: Fri May 4 20:20:16 2018 New Revision: 259959 URL: https://gcc.gnu.org/viewcvs?rev=259959=gcc=rev Log: PR c++/85305 - pack in lambda init-capture. * parser.c

[Bug c++/85305] Parameter pack expression in lambda capture list fails as part of a fold expression

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

[PATCH, aarch64] Patch to update pipeline descriptions in thunderx2t99.md

Now that we are in stage 1 again, here is an update to my earlier t99 scheduling file patch for thunderx2t99.md.  There were some instruction types (mostly asimd) that did not have schedules and other types that had duplicate schedules. With this patch there should be one schedule for every type

Re: [RFA][fortran] Fix # handling in the Fortran front-end

On Fri, May 04, 2018 at 02:05:11PM -0600, Jeff Law wrote: > On 05/04/2018 01:55 PM, Steve Kargl wrote: > > On Fri, May 04, 2018 at 01:32:00PM -0600, Jeff Law wrote: > >> > >> The Fortran front end has its own code to parse # > >> directives. We've run into a case where it does not function

Re: [RFA][fortran] Fix # handling in the Fortran front-end

On 05/04/2018 01:55 PM, Steve Kargl wrote: > On Fri, May 04, 2018 at 01:32:00PM -0600, Jeff Law wrote: >> >> The Fortran front end has its own code to parse # >> directives. We've run into a case where it does not function correctly. >> In particular when the directive changes the current

Re: [RFA][fortran] Fix # handling in the Fortran front-end

On Fri, May 04, 2018 at 01:32:00PM -0600, Jeff Law wrote: > > The Fortran front end has its own code to parse # > directives. We've run into a case where it does not function correctly. > In particular when the directive changes the current file, subsequent > diagnostics still refer to the

Re: [C++ PATCH] Fix value initialized decltype(nullptr) in constexpr (PR c++/85553)

On Fri, May 4, 2018 at 2:06 PM, Paolo Carlini wrote: > Hi, > > > On 04/05/2018 19:45, Jason Merrill wrote: >> >> On Sun, Apr 29, 2018 at 3:23 AM, Paolo Carlini >> wrote: >>> >>> Hi, >>> >>> On 28/04/2018 18:41, Jason Merrill wrote: On

[Bug go/85629] GCC 8.1.0: FTBFS: make check fails in Go part

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85629 --- Comment #5 from Stefan --- (In reply to Ian Lance Taylor from comment #4) > Which version of which linker are you running? # ld -v GNU ld version 2.20.51.0.2-5.47.el6_9.1 20100205 > For that matter, which version of which assembler? # as

Re: [PATCH 8/8] [BRIGFE] Fix handling of NOPs

Committed as r259958. On Fri, May 4, 2018 at 5:02 PM, Pekka Jääskeläinen wrote: > --- > gcc/brig/brigfrontend/brig-basic-inst-handler.cc | 10 +- > 1 file changed, 5 insertions(+), 5 deletions(-) >

Re: [PATCH 7/8] [BRIGFE] phsa-specific optimizations

Committed as r259957. On Fri, May 4, 2018 at 5:02 PM, Pekka Jääskeläinen wrote: > Add flag -fassume-phsa that is on by default. If -fno-assume-phsa > is given, these optimizations are disabled. > > With this flag, gccbrig can generate GENERIC that assumes we are > targeting a

Re: [C++ PATCH] Fix value initialized decltype(nullptr) in constexpr (PR c++/85553)

... thinking more about the issue, probably the best thing to do would be wrapping instead in a COMPOUND_EXPR, which would be also consistent with cp_convert_to_pointer. Thus I'm finishing testing the below (past g++.dg). How about it? Thanks! Paolo. / Index: cvt.c

[RFA][fortran] Fix # handling in the Fortran front-end

The Fortran front end has its own code to parse # directives. We've run into a case where it does not function correctly. In particular when the directive changes the current file, subsequent diagnostics still refer to the original filename. Concretely take this code and compile it with

[Bug ada/85638] [8/9 regression] build failure for Ada runtime with SJLJ exceptions on x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85638 --- Comment #12 from Eric Botcazou --- > I wonder why this doesn't seem to happen with DWARF-2 exception handling. OK, the difference is that dw2_build_landing_pads does: lp->landing_pad = gen_label_rtx (); emit_label

[Bug go/85629] GCC 8.1.0: FTBFS: make check fails in Go part

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85629 --- Comment #4 from Ian Lance Taylor --- Thanks. Which version of which linker are you running? For that matter, which version of which assembler? I don't see the warnings and errors that you are seeing, with GNU as 2.30 and GNU gold

[Bug go/85629] GCC 8.1.0: FTBFS: make check fails in Go part

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85629 --- Comment #3 from Stefan --- Created attachment 44073 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44073=edit gotools/cmd_vet-testlog

[Bug fortran/85407] Replace gcc_assert in module.c:read_module by more helpful diagnostics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85407 --- Comment #2 from Harald Anlauf --- (In reply to Dominique d'Humieres from comment #1) > The trunk is now at 9.0. The patch can be committed if accepted. It was my understanding that Steve OK'd it and said that he'd commit, but then did not.

Re: [PATCH PR other/77609] Let the assembler choose ELF section types for miscellaneous named sections

On Sat, Apr 28, 2018 at 2:42 AM, Roland McGrath wrote: > I'm back for stage 1! > > The same patch from https://gcc.gnu.org/ml/gcc-patches/2018-02/msg01549.html > rebases cleanly and I didn't change anything but the date on the log entry > since what I posted there. The fresh

[gomp5] simd if/nontemporal clauses parsing and cancel if modifier

Hi! This patch adds parsing of if and nontemporal clauses for simd construct and also adds parsing of (optional) cancel modifier for if clause on cancel directive. While nontemporal clause is just an optimization (we still want to use non-temporal stores (or even loads?) for those vars, what is

Re: [PATCH PR other/77609] Let the assembler choose ELF section types for miscellaneous named sections

ping On Sat, Apr 28, 2018 at 2:42 AM Roland McGrath wrote: > I'm back for stage 1! > The same patch from https://gcc.gnu.org/ml/gcc-patches/2018-02/msg01549.html > rebases cleanly and I didn't change anything but the date on the log entry > since what I posted there. The

Re: [C++ PATCH] Fix value initialized decltype(nullptr) in constexpr (PR c++/85553)

Hi, On 04/05/2018 19:45, Jason Merrill wrote: On Sun, Apr 29, 2018 at 3:23 AM, Paolo Carlini wrote: Hi, On 28/04/2018 18:41, Jason Merrill wrote: On Fri, Apr 27, 2018 at 7:26 PM, Paolo Carlini wrote: Hi again, I'm now pretty sure that we

Re: [PATCH 5/8] [BRIGFE] do not allow optimizations based on known C builtins

Committed as r259949. On Fri, May 4, 2018 at 5:00 PM, Pekka Jääskeläinen wrote: > This can break inputs that have similarly names functions. > --- > gcc/brig/brig-lang.c | 16 +++- > 1 file changed, 7 insertions(+), 9 deletions(-) >

Re: [PATCH 4/8] [BRIGFE] allow controlling strict aliasing from cmd line

Committed as r259948. On Fri, May 4, 2018 at 4:59 PM, Pekka Jääskeläinen wrote: > --- > gcc/brig/brig-lang.c | 12 +--- > 1 file changed, 9 insertions(+), 3 deletions(-) > >

libgo patch committed: On AIX, pass -X64 first to ar

This patch by Tony Reix passes -X64 first to the ar command on AIX, not after the rc command. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline and GCC 8 branch. Ian Index: gcc/go/gofrontend/MERGE ===

Re: [C++ PATCH] Fix value initialized decltype(nullptr) in constexpr (PR c++/85553)

On Sun, Apr 29, 2018 at 3:23 AM, Paolo Carlini wrote: > Hi, > > On 28/04/2018 18:41, Jason Merrill wrote: >> >> On Fri, Apr 27, 2018 at 7:26 PM, Paolo Carlini >> wrote: >>> >>> Hi again, >>> >>> I'm now pretty sure that we have a latent issue

[Bug ada/85638] [8/9 regression] build failure for Ada runtime with SJLJ exceptions on x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85638 --- Comment #11 from xantares09 at hotmail dot com --- Oh, ok

[Bug ada/85638] [8/9 regression] build failure for Ada runtime with SJLJ exceptions on x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85638 --- Comment #10 from Eric Botcazou --- > Yes, I applied your patch, now the build fails with another error: This one is yours, you need to compile the 8.1 cross with the 8.1 native.

[Bug ada/85638] [8/9 regression] build failure for Ada runtime with SJLJ exceptions on x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85638 --- Comment #9 from xantares09 at hotmail dot com --- Yes, I applied your patch, now the build fails with another error: gcc -c -I./ -I/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.1/adalib/../adainclude -I/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.1/adalib

[Bug go/85630] GCC 8.1.0: Filesystem pollution during build: .cache dir in $HOME

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85630 Ian Lance Taylor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug go/85630] GCC 8.1.0: Filesystem pollution during build: .cache dir in $HOME

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85630 --- Comment #3 from ian at gcc dot gnu.org --- Author: ian Date: Fri May 4 17:07:20 2018 New Revision: 259945 URL: https://gcc.gnu.org/viewcvs?rev=259945=gcc=rev Log: PR go/85630 * Makefile.am (CHECK_ENV): Set GOCACHE.

Re: gotools patch committed: Set GOCACHE during tests

On Fri, May 4, 2018 at 9:25 AM, Jakub Jelinek wrote: > On Fri, May 04, 2018 at 09:23:54AM -0700, Ian Lance Taylor wrote: >> This patch to the gotools Makefile sets the GOCACHE variable while >> running the gotools tests. This avoids creating a cache in the >> default location,

Re: [PATCH 3/8] [BRIGFE] The modulo in ID computation should not be needed.

Commited in r259944. On Fri, May 4, 2018 at 4:58 PM, Pekka Jääskeläinen wrote: > The case where a dim is greater than the grid size doesn't seem > to be mentioned in the specs nor tested by PRM test suite. > --- > gcc/brig/brigfrontend/brig-code-entry-handler.cc | 10

Re: [PATCH 2/8] [BRIGFE] Enable whole program optimizations

Committed as r259943. On Fri, May 4, 2018 at 4:57 PM, Pekka Jääskeläinen wrote: > HSA assumes all program scope HSAIL symbols can be queried from > the host runtime API, thus cannot be removed by the IPA. > > Getting some inlining happening in the finalized binary

Re: [PATCH 1/8] [BRIGFE] fix an alloca stack underflow

Committed as r259942. On Fri, May 4, 2018 at 4:56 PM, Pekka Jääskeläinen wrote: > We didn't preserve additional space for the alloca frame pointers that > are needed to be saved in the alloca space.

[Bug target/85512] [8/9 Regression] gcc generating non-existing sshr with immh == 0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85512 --- Comment #13 from ktkachov at gcc dot gnu.org --- Author: ktkachov Date: Fri May 4 16:37:30 2018 New Revision: 259941 URL: https://gcc.gnu.org/viewcvs?rev=259941=gcc=rev Log: [AArch64] PR target/85512: Tighten SIMD right shift immediate

[Bug target/82518] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518 --- Comment #60 from ktkachov at gcc dot gnu.org --- Author: ktkachov Date: Fri May 4 16:35:32 2018 New Revision: 259940 URL: https://gcc.gnu.org/viewcvs?rev=259940=gcc=rev Log: [arm] PR target/82518: Return false in ARRAY_MODE_SUPPORTED_P for

[Bug fortran/85575] Acceptance of invalid code: ordering of declaration statements with implicit typing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85575 --- Comment #10 from Jürgen Reuter --- (In reply to Dominique d'Humieres from comment #9) > AFAICT > > (1) The behavior is present even without module: add > > implicit none > integer :: cl > > to the test in comment 4 and it compiles if

Re: gotools patch committed: Set GOCACHE during tests

On Fri, May 04, 2018 at 09:23:54AM -0700, Ian Lance Taylor wrote: > This patch to the gotools Makefile sets the GOCACHE variable while > running the gotools tests. This avoids creating a cache in the > default location, which is the user's home directory. This should fix > PR 85630.

[Bug ada/85638] [8/9 regression] build failure for Ada runtime with SJLJ exceptions on x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85638 --- Comment #8 from Eric Botcazou --- Another (checking) assertion triggers in fix_up_crossing_landing_pad: rtx_insn *insn = BB_END (e->src); rtx note = find_reg_note (insn, REG_EH_REGION, NULL_RTX); gcc_assert (note !=

[Bug go/85630] GCC 8.1.0: Filesystem pollution during build: .cache dir in $HOME

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85630 --- Comment #2 from ian at gcc dot gnu.org --- Author: ian Date: Fri May 4 16:23:51 2018 New Revision: 259937 URL: https://gcc.gnu.org/viewcvs?rev=259937=gcc=rev Log: PR go/85630 * Makefile.am (CHECK_ENV): Set GOCACHE.

[PATCH GCC][6/6]Restrict predcom using register pressure information

Hi, This patch restricts predcom pass using register pressure information. In case of high register pressure, we now prune additional chains as well as disable unrolling in predcom. In generally, I think this patch set is useful. Bootstrap and test on x86_64 ongoing. Any comments? Thanks, bin

gotools patch committed: Set GOCACHE during tests

This patch to the gotools Makefile sets the GOCACHE variable while running the gotools tests. This avoids creating a cache in the default location, which is the user's home directory. This should fix PR 85630. Bootstrapped and ran gotools tests on x86_64-pc-linux-gnu. Committed to mainline. I

[PATCH GCC][5/6]implement live range, reg pressure computation class

Hi, Based on previous patch, this one implements live range, reg pressure computation class in tree-ssa-live.c. The user would only need to instantiate the class and call the computation interface as in next patch. During the work, I think it's also worthwhile to classify all live range and

[Bug fortran/85575] Acceptance of invalid code: ordering of declaration statements with implicit typing

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

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

Hi, Following Jeff's suggestion, I am now using existing tree-ssa-live.c and tree-ssa-coalesce.c to compute register pressure, rather than inventing another live range solver. The major change is to record region's basic blocks in var_map and use that information in computation, rather than

[PATCH GCC][3/6]Delete unnecessary function live_merge_and_clear

HI, This is an obvious patch removing the unnecessary function. Bootstrap and test on x86_64 and AArch64 ongoing. Is it OK? Thanks, bin 2018-04-27 Bin Cheng * tree-ssa-live.h (live_merge_and_clear): Delete.From ba6e47da7faba9a31c776a6d06ef052b1ed392a8 Mon Sep 17

[PATCH GCC][2/6]Compute available register for each register classes

Hi, This is the second patch computing available/clobber registers for register classes. It's the same as the original patch posted @https://gcc.gnu.org/ml/gcc-patches/2017-05/msg01022.html Bootstrap and test on x86_64 and AArch64 ongoing. Any comments? Thanks, bin 2017-04-27 Bin Cheng

[PATCH GCC][1/6]Compute type mode and register class mapping

Hi, This is the updated version patch set computing register pressure on TREE SSA and use that information to direct other loop optimizers (predcom only for now). This version of change is to follow Jeff's comment that we should reuse existing tree-ssa-live.c infrastructure for live range

[Bug go/85629] GCC 8.1.0: FTBFS: make check fails in Go part

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85629 --- Comment #2 from Ian Lance Taylor --- What are the contents of gotools/cmd_vet-testlog?

[Bug middle-end/38960] Wrong floating point reorder

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38960 --- Comment #5 from joseph at codesourcery dot com --- Since any non-const function can examine floating-point state, I'd expect significant effects on code generation. (Whether this also applies to asms depends on the architecture; some

[Bug ada/85635] typo in link.c for BSD platforms

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85635 --- Comment #13 from Eric Botcazou --- > Those "many" people don't build gnat. Very few people do according to the > testsuite results page. That's a clear misconception. The Ada compiler is regularly built and tested on Linux, Darwin,

Re: [PATCH, i386]: AVX false dependencies fix

> This is the same patch I posted a few days ago, a bit modified according to > Uros' > recommendation. > > Patch fixes false dependencies for vmovss, vmovsd, vrcpss, vrsqrtss, vsqrtss > and vsqrtsd > instructions. > Tested on x86-64/Linux, no new test fails, some SPEC 2006/2017 performance >

Re: [PATCH, rs6000] Add missing vec_max tests

Hi! On Fri, May 04, 2018 at 07:59:37AM -0700, Carl Love wrote: > > Why does the patch remove these two vec_sel?  If that is wanted, the > > changelog should mention this. > No clue why I removed the vec_sel test. Been sitting on the testsuite > patch set too long, I don't recall. I put it back

[Bug target/85616] ARM target using -O2 may cause unaligned access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85616 --- Comment #3 from ktkachov at gcc dot gnu.org --- Though the example code given breaks C's strict aliasing rules, doesn't it? bug_start is an array of chars (byte-aligned) but the stores to it are done as ints, which expect word alignment, so

[Bug ipa/85656] New: gcc.dg/ipa/ipa-icf-38.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656 Bug ID: 85656 Summary: gcc.dg/ipa/ipa-icf-38.c FAILs Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ipa

[Bug c++/85655] New: 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 Bug ID: 85655 Summary: ICE with -flto and -O2 during IPA pass: cp lto1: internal compiler error: Segmentation fault Product: gcc Version: 8.1.0 Status: UNCONFIRMED

[Bug target/85593] [5,6,7,8 Regression] GCC on ARM allocates R3 for local variable when calling naked function with O2 optimizations enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85593 Ramana Radhakrishnan changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug tree-optimization/85654] gcc.dg/vect/pr85586.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85654 Rainer Orth changed: What|Removed |Added Version|8.0 |9.0 Target Milestone|---

[Bug tree-optimization/85654] New: gcc.dg/vect/pr85586.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85654 Bug ID: 85654 Summary: gcc.dg/vect/pr85586.c FAILs Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization

Re: [PATCH, rs6000] Add missing vec_max tests

Segher: > > -  *out++ = vec_sel (in0, in1, inl); > > -  *out++ = vec_sel (in0, in1, inb); > >    *out++ = vec_sub (in0, in1); > >    *out++ = vec_sqrt (in0); > >    *out++ = vec_trunc (in0); > > Why does the patch remove these two vec_sel?  If that is wanted, the > changelog should mention this.

[Bug libgomp/85649] [og7, nvptx, openacc] Too much workers chosen for launch

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85649 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/85575] Acceptance of invalid code: ordering of declaration statements with implicit typing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85575 --- Comment #8 from Jürgen Reuter --- module foo implicit none contains function constr_quark_loopline(ho,sho) result(cl) integer, dimension(sho), intent(in) :: ho integer, dimension(sho) :: hor integer, intent(in)

[Bug fortran/85575] Acceptance of invalid code: ordering of declaration statements with implicit typing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85575 --- Comment #7 from Dominique d'Humieres --- Please provide code showing the problem.

libgo patch committed: Fix unaligned read in unwind code

This patch by Than McIntosh fixes some unaligned reads in the Go unwinding code. Bootstrapped and ran a few Go tests on sparc-solaris11. Committed to mainline. Ian Index: gcc/go/gofrontend/MERGE === --- gcc/go/gofrontend/MERGE

[Bug target/85653] New: [nvptx] Work around subsequent bar.sync JIT/ptxas bug

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85653 Bug ID: 85653 Summary: [nvptx] Work around subsequent bar.sync JIT/ptxas bug Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3

[PATCH 7/8] [BRIGFE] phsa-specific optimizations

Add flag -fassume-phsa that is on by default. If -fno-assume-phsa is given, these optimizations are disabled. With this flag, gccbrig can generate GENERIC that assumes we are targeting a phsa-runtime based implementation, which allows us to expose the work-item context accesses to retrieve WI

[PATCH 8/8] [BRIGFE] Fix handling of NOPs

--- gcc/brig/brigfrontend/brig-basic-inst-handler.cc | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) >From fee48e53063309a58a9a3050df26395ae1615111 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pekka=20J=C3=A4=C3=A4skel=C3=A4inen?= Date: Thu, 12

[PATCH 6/8] [BRIGFE] skip multiple forward declarations of the same function

--- gcc/brig/brigfrontend/brig-function-handler.cc | 4 1 file changed, 4 insertions(+) >From 1c708e887073960b6142d716d3e85f3453d7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pekka=20J=C3=A4=C3=A4skel=C3=A4inen?= Date: Sat, 17 Feb 2018 08:59:25 +0200

[PATCH 5/8] [BRIGFE] do not allow optimizations based on known C builtins

This can break inputs that have similarly names functions. --- gcc/brig/brig-lang.c | 16 +++- 1 file changed, 7 insertions(+), 9 deletions(-) >From 105277ee937482ee1a55265b1ec45637bc1e7a0b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pekka=20J=C3=A4=C3=A4skel=C3=A4inen?=

[PATCH 4/8] [BRIGFE] allow controlling strict aliasing from cmd line

--- gcc/brig/brig-lang.c | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) >From c8a86773e877949fb9308d2dd448ea013be22c3e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pekka=20J=C3=A4=C3=A4skel=C3=A4inen?= Date: Mon, 12 Feb 2018 11:34:58 +0200

[PATCH 3/8] [BRIGFE] The modulo in ID computation should not be needed.

The case where a dim is greater than the grid size doesn't seem to be mentioned in the specs nor tested by PRM test suite. --- gcc/brig/brigfrontend/brig-code-entry-handler.cc | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) >From 99303afff584518c1fd17e3c6ebe965043dd58f0 Mon Sep

[PATCH 2/8] [BRIGFE] Enable whole program optimizations

HSA assumes all program scope HSAIL symbols can be queried from the host runtime API, thus cannot be removed by the IPA. Getting some inlining happening in the finalized binary required: * explicitly marking the 'prog' scope functions and the launcher function "externally_visible" to avoid the

[PATCH 1/8] [BRIGFE] fix an alloca stack underflow

We didn't preserve additional space for the alloca frame pointers that are needed to be saved in the alloca space. Fixes libgomp.c++/target-6.C execution test. --- libhsail-rt/rt/workitems.c | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git

[PATCH 0/8] [BRIGFE] various fixes and optimizations

Hi, I'm posting a series of patches that I will shortly commit to trunk as a maintainer of the BRIG frontend. All of them are build tested, the last one also with a bootstrap build. Best regards, -- Pekka

[Bug fortran/85575] Acceptance of invalid code: ordering of declaration statements with implicit typing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85575 --- Comment #6 from Jürgen Reuter --- In addition, it also throws the error Error: GNU Extension: Symbol ‘sho’ is used before it is typed at (1) for the case of a contained module procedure with implicit none as in comment #5.

[Bug fortran/85575] Acceptance of invalid code: ordering of declaration statements with implicit typing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85575 --- Comment #5 from Jürgen Reuter --- Yes, as external function the error is thrown, but not as module procedure. So do module foo implicit none contains function quark ... end function ... end module ... This will compile.

[Bug c++/85651] Invalid -Warray-bounds warning with -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85651 --- Comment #1 from Gabriel Burca --- I suspect the "for" loop in appendAux() is being optimized and replaced with a memcpy(), which then leads to the warning.

[Bug middle-end/85652] -Wformat-overflow warning silenced by -fpic/-fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85652 --- Comment #1 from Andrew Pinski --- I suspect this is due to inlining decision of b::h into f. In PIC mode, b::h is consider overwritable so it is not inclined while in non pic mode it is inlined.

Re: libffi PowerPC64 ELFv1 fp arg fixes

On Fri, May 04, 2018 at 06:02:27AM -0500, Segher Boessenkool wrote: > On Fri, May 04, 2018 at 07:40:20PM +0930, Alan Modra wrote: > > The attached patch has been accepted into upstream libffi. It fixes > > powerpc64-linux problems shown up by Bruno Haible's new libffi > > testsuite tests.

[Bug middle-end/85652] New: -Wformat-overflow warning silenced by -fpic/-fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85652 Bug ID: 85652 Summary: -Wformat-overflow warning silenced by -fpic/-fPIC Product: gcc Version: 8.1.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal

New Ukrainian PO file for 'gcc' (version 8.1.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the Ukrainian team of translators. The file is available at: http://translationproject.org/latest/gcc/uk.po (This file, 'gcc-8.1.0.uk.po', has

[Bug c++/85651] New: Invalid -Warray-bounds warning with -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85651 Bug ID: 85651 Summary: Invalid -Warray-bounds warning with -O3 Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug ada/85635] typo in link.c for BSD platforms

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85635 --- Comment #12 from John Marino --- yeah, my problem is that I was thinking cpp was complaining this whole time, but it was actually the c compiler. Once I realized that, the misconception cleared up. My fault, should've known better. And I

[Bug middle-end/85650] Additional warnings when -fsanitize=undefined is used with -Wstringop-truncation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85650 --- Comment #1 from Franz Sirl --- Created attachment 44068 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44068=edit testcase 2

[Bug middle-end/85650] New: Additional warnings when -fsanitize=undefined is used with -Wstringop-truncation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85650 Bug ID: 85650 Summary: Additional warnings when -fsanitize=undefined is used with -Wstringop-truncation Product: gcc Version: 8.1.0 Status: UNCONFIRMED

  1   2   >