Re: [PATCH] RX TARGET_RTX_COSTS function

On Thu, 2018-02-22 at 15:41 +, Nick Clifton wrote: > > > gcc/ChangeLog: > > > * config/rx/rx.c (rx_rtx_costs): New function. > > > (TARGET_RTX_COSTS): Override to use rx_rtx_costs. > Approved - please apply. > Thanks.  Committed as r257905. Cheers, Oleg

[PATCH] Correct debug for -mcall-ms2sysv-xlogues stubs (PR target/83917, take 2)

Hi! On Sat, Jan 20, 2018 at 06:01:16PM -0600, Daniel Santos wrote: > Thanks.  I like the idea of commonizing the macros for consistency. Didn't see a progress on this P3 for a while, so I've written this version of the patch; no tests though, what I've been using in testing was: /* { dg-do

Re: [PATCH] avoid bogus -Wstringop-truncation when inlining (PR 84480)

On 02/21/2018 07:53 PM, Jeff Law wrote: On 02/21/2018 02:19 PM, Martin Sebor wrote: The attached patch eliminates -Wstringop-truncation false positives reported in bug 84480 - bogus -Wstringop-truncation despite assignment with an inlined string literal. It does that by delegating early

[Bug tree-optimization/84515] missed optimization: expected loop merging

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84515 ktkachov at gcc dot gnu.org changed: What|Removed |Added Keywords||missed-optimization

[Bug target/79926] i386: untranslated placeholder "exception/interrupt" in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79926 Eric Gallager changed: What|Removed |Added Keywords||diagnostic, easyhack, patch

Re: PING: [PATCH] i386: Add TARGET_INDIRECT_BRANCH_REGISTER

On Thu, Feb 22, 2018 at 6:38 AM, Jan Hubicka wrote: >> >> >> >> Hi Jan, >> >> >> >> https://gcc.gnu.org/ml/gcc-patches/2018-01/msg02233.html >> >> >> >> Is OK for trunk? >> > >> > I see that using register makes the problem go away and pushing address to >> > stack >> > seemed

[Bug target/83964] [8 Regression] ICE in extract_insn, at recog.c:2304

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83964 Jakub Jelinek changed: What|Removed |Added CC||carll at gcc dot gnu.org --- Comment #4

[Bug target/84176] Need a different thunk for -mindirect-branch=thunk-extern -fcf-protection -mcet

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84176 --- Comment #1 from hjl at gcc dot gnu.org --- Author: hjl Date: Thu Feb 22 17:09:06 2018 New Revision: 257909 URL: https://gcc.gnu.org/viewcvs?rev=257909=gcc=rev Log: i386: Add __x86_indirect_thunk_nt_reg for -fcf-protection -mcet nocf_check

[Bug c++/80955] Macros expanded in definition of user-defined literals

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80955 --- Comment #7 from Jonathan Wakely --- Moved to PR 84517

[Bug preprocessor/84517] New: [8 Regression] "string literal"__FILE__ no longer accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84517 Bug ID: 84517 Summary: [8 Regression] "string literal"__FILE__ no longer accepted Product: gcc Version: 8.0 Status: UNCONFIRMED Keywords: diagnostic

[Bug tree-optimization/84480] [8 Regression] bogus -Wstringop-truncation despite assignment with an inlined string literal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84480 --- Comment #6 from Romain Geissler --- Thanks ;)

[Bug tree-optimization/84480] [8 Regression] bogus -Wstringop-truncation despite assignment with an inlined string literal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84480 --- Comment #4 from Martin Sebor --- Author: msebor Date: Thu Feb 22 17:35:29 2018 New Revision: 257910 URL: https://gcc.gnu.org/viewcvs?rev=257910=gcc=rev Log: PR tree-optimization/84480 - bogus -Wstringop-truncation despite assignment with an

[Bug target/83964] [8 Regression] ICE in extract_insn, at recog.c:2304

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83964 Segher Boessenkool changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #8 from Wilco --- (In reply to Jakub Jelinek from comment #7) > cfun->has_nonlocal_label instead of cfun->calls_setjmp would cover > __builtin_setjmp. > > aarch64_frame_pointer_required would force frame_pointer_needed and thus be >

[Bug c/84522] New: GCC does not generate cmpxchg16b when mcx16 is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84522 Bug ID: 84522 Summary: GCC does not generate cmpxchg16b when mcx16 is used Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3

[Bug target/84522] GCC does not generate cmpxchg16b when mcx16 is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84522 --- Comment #4 from Ruslan Nikolaev --- I guess, in this case you would have to fall-back to lock-based implementation for everything. But does C11 even require that atomic_load work on read-only memory?

[Bug fortran/84523] New: [8 Regression] Runtime crash deallocating allocatable array within derived type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84523 Bug ID: 84523 Summary: [8 Regression] Runtime crash deallocating allocatable array within derived type Product: gcc Version: 8.0.1 Status: UNCONFIRMED

[Bug target/82851] [8 regression] g++.dg/vect/slp-pr56812.cc, i386/avx2-vpaddq-3.c, i386/avx2-vpsubq-3.c fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82851 --- Comment #7 from Jakub Jelinek --- Author: jakub Date: Thu Feb 22 21:27:44 2018 New Revision: 257916 URL: https://gcc.gnu.org/viewcvs?rev=257916=gcc=rev Log: PR target/82851 * gcc.target/i386/avx2-vpaddq-3.c: Add

[Bug target/83335] [8 regression][aarch64,ilp32] gcc.target/aarch64/asm-2.c ICEs since 255481

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83335 Steve Ellcey changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/83964] [8 Regression] ICE in extract_insn, at recog.c:2304

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83964 --- Comment #9 from Carl Love --- This test case is in the list in PR 84422 . Working on a patch.

[Bug target/84522] GCC does not generate cmpxchg16b when mcx16 is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84522 Andrew Pinski changed: What|Removed |Added Component|c |target --- Comment #1 from Andrew

[Bug c++/70468] [6/7/8 Regression] ICE on invalid code on x86_64-linux-gnu in emit_mem_initializers, at cp/init.c:1109

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70468 --- Comment #7 from Jakub Jelinek --- It is the expand_member_init's current_template_parms check that matters here, with - if (current_template_parms - || same_type_p (basetype, current_class_type)) - return basetype; +

[Bug fortran/84511] [6/7/8 Regression] Internal compiler error from directly printing return of C_LOC

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

[Bug go/84484] libgo configure tests fail to find -latomic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #17 from ian at gcc dot gnu.org --- Author: ian Date: Thu Feb 22 19:49:04 2018 New Revision: 257914 URL: https://gcc.gnu.org/viewcvs?rev=257914=gcc=rev Log: PR go/84484 libgo: add support for riscv64 Patch by

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #6 from Wilco --- (In reply to Jakub Jelinek from comment #5) > (completely untested) would require frame pointers for all setjmp calls, not > just __builtin_setjmp. That's the correct approach indeed, however

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #7 from Jakub Jelinek --- cfun->has_nonlocal_label instead of cfun->calls_setjmp would cover __builtin_setjmp. aarch64_frame_pointer_required would force frame_pointer_needed and thus be true in that case too. But sure, if it

[Bug fortran/83148] [8 regression] ICE: crash_signal from toplev.c:325

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83148 --- Comment #6 from Thomas Koenig --- The problem seems to be that gfc_conv_initalizer does not look through (gdb) p *expr $1 = {expr_type = EXPR_STRUCTURE, ts = {type = BT_DERIVED, kind = 0, to (gdb) p

Re: [PATCH] adjust warning_n() to take uhwi (PR 84207)

On Thu, 22 Feb 2018, Martin Sebor wrote: > Ping: https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00858.html > > This is just a tweak to fix a translation bug introduced by > one of my warnings (calling warning() where warning_n() is > more appropriate), and to enhance warning_n() et al. to do >

[Bug c++/84516] bitfield temporaries > 32-bits have wrong type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84516 --- Comment #2 from joseph at codesourcery dot com --- See also bug 70733, another bug with these types being user-exposed for bit-fields for C++. For C++ (unlike C), the existence of these types internally in the compiler should never be

[Bug target/82851] [8 regression] g++.dg/vect/slp-pr56812.cc, i386/avx2-vpaddq-3.c, i386/avx2-vpsubq-3.c fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82851 Jakub Jelinek changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with setjmp/longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #3 from Andrew Pinski --- To me any use of __builtin_setjmp/__builtin_longjmp is almost always incorrect.

[PATCH] PR fortran/84511 -- Fix C_LOC in a transfer statement

All, The attached patch handles C_LOC in a transfer statement such as "print *, c_loc(xxx)". The bug report contains two files that must be compiled separately to exhibit the bug. I have no idea how to write a testcase for this situation. If someone can write a testcase, I'm fine with that.

[Bug target/81572] [7/8 Regression] gcc-7 regression: unnecessary vector regmove on compare

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81572 --- Comment #4 from Vladimir Makarov --- Author: vmakarov Date: Thu Feb 22 21:17:51 2018 New Revision: 257915 URL: https://gcc.gnu.org/viewcvs?rev=257915=gcc=rev Log: 2018-02-22 Vladimir Makarov PR target/81572

[Bug fortran/84519] STOP and ERROR STOP statements with QUIET specifier

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84519 Janne Blomqvist changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org ---

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #4 from Jakub Jelinek --- Is the requirement just for functions that contain setjmp? If so, the backend could just force frame pointers in cfun->calls_setjmp functions. If not, even if the default is tweaked again to be

libgo patch committed: Add 64-bit RISC-V support

This patch by Andreas Schwab adds 64-bit RISC-V support to libgo. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian 2018-02-22 Andreas Schwab * go.test/go-test.exp (go-set-goarch): Recognize riscv64-*-*. Index:

patch to fix PR81572

The following patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81572 The patch was successfully bootstrapped and tested on ppc64. Committed as rev. 257915. Index: ChangeLog === --- ChangeLog (revision 257901) +++

[Bug c++/84518] [8 Regression] ICE with lambda capturing broken variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84518 David Malcolm changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug middle-end/21161] [6/7/8 Regression] "clobbered by longjmp" warning ignores the data flow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21161 Jeffrey A. Law changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |law at redhat dot com ---

[PATCH] PR 84519 Handle optional QUIET specifier for STOP and ERROR STOP

Fortran 2018 adds a new QUIET specifier for the STOP and ERROR STOP statements, in order to suppress the printing of signaling FP exceptions and the stop code. This patch adds the necessary library changes, but for now the new specifier is not parsed and the frontend unconditionally adds a false

[Bug go/84484] libgo configure tests fail to find -latomic

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

Re: [PATCH] PR 84519 Handle optional QUIET specifier for STOP and ERROR STOP

On Thu, Feb 22, 2018 at 09:42:02PM +0200, Janne Blomqvist wrote: > Fortran 2018 adds a new QUIET specifier for the STOP and ERROR STOP > statements, in order to suppress the printing of signaling FP > exceptions and the stop code. This patch adds the necessary library > changes, but for now the

[Bug tree-optimization/84515] missed optimization: expected loop merging

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

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

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

[Bug target/84522] GCC does not generate cmpxchg16b when mcx16 is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84522 --- Comment #2 from Ruslan Nikolaev --- Yes, but not having atomic_load is far less an issue. Oftentimes, algorithms that use 128-bit can simply use compare_and_exchange only (at least for x86-64).

[Bug c++/84453] [8 Regression] ICE in build_type_attribute_qual_variant, at attribs.c:1166

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

[Bug target/83964] [8 Regression] ICE in extract_insn, at recog.c:2304

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83964 --- Comment #10 from Carl Love --- These builtins were per a request from Steve Monroe. Not sure why he wanted them or if he actually ever used them.

[Bug fortran/84495] Incorrect result for concatenation of Fortran allocatable string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84495 Thomas Koenig changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/81116] Last character of allocatable-length string reset to blank in an assigment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81116 Thomas Koenig changed: What|Removed |Added CC||david.sagan at gmail dot com ---

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with setjmp/longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 David Malcolm changed: What|Removed |Added Keywords||wrong-code Priority|P3

Re: [PATCH] Tweak gcc.target/i386/avx2-vp{add,sub}q-3.c (PR target/82851)

On Thu, Feb 22, 2018 at 7:16 PM, Jakub Jelinek wrote: > Hi! > > These tests FAIL the vp.*q.*ymm insn scan with some tunings, e.g. > -mtune=silvermont or -mtune=atom, because vectorizing it using AVX2 > is based on costs considered too expensive. > E.g. for -mtune=silvermont I

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Jeffrey A. Law changed: What|Removed |Added Priority|P3 |P2 Assignee|unassigned at

[Bug target/84522] GCC does not generate cmpxchg16b when mcx16 is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84522 --- Comment #3 from Ruslan Nikolaev --- (In reply to Ruslan Nikolaev from comment #2) > Yes, but not having atomic_load is far less an issue. Oftentimes, algorithms > that use 128-bit can simply use compare_and_exchange only (at least for >

[Bug fortran/84346] Statement functions should not accept keywords

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84346 kargl at gcc dot gnu.org changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug c++/84424] [8 Regression] ICE on C++ code: tree check: expected record_type or union_type or qual_union_type, have vector_type in reduced_constant_expression_p, at cp/constexpr.c:1766

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

[Bug c++/84424] [8 Regression] ICE on C++ code: tree check: expected record_type or union_type or qual_union_type, have vector_type in reduced_constant_expression_p, at cp/constexpr.c:1766

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84424 --- Comment #5 from Jason Merrill --- Author: jason Date: Thu Feb 22 22:50:37 2018 New Revision: 257924 URL: https://gcc.gnu.org/viewcvs?rev=257924=gcc=rev Log: PR c++/84424 - ICE with constexpr and __builtin_shuffle. *

[Bug c++/70468] [6/7/8 Regression] ICE on invalid code on x86_64-linux-gnu in emit_mem_initializers, at cp/init.c:1109

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70468 Jason Merrill changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug c++/84424] [8 Regression] ICE on C++ code: tree check: expected record_type or union_type or qual_union_type, have vector_type in reduced_constant_expression_p, at cp/constexpr.c:1766

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84424 Jason Merrill changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

C++ PATCH for c++/84424, ICE with constexpr and __builtin_shuffle.

We were crashing when checking whether the value being created for v is constant, because TYPE_FIELDS is invalid for VECTOR_TYPE. But it's easy enough to just return false for a partially-initialized vector. Tested x86_64-pc-linux-gnu, applying to trunk. commit

[Bug c/84524] New: -O3 causes behavior change

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84524 Bug ID: 84524 Summary: -O3 causes behavior change Product: gcc Version: 5.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee:

[Bug target/84522] GCC does not generate cmpxchg16b when mcx16 is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84522 --- Comment #5 from Ruslan Nikolaev --- After more t(In reply to Andrew Pinski from comment #1) > IIRC this was done because there is no atomic load/stores or a way to do > backwards compatible. After more thinking about it... Should not it be

[Bug fortran/59781] [6 Regression] [F03] Incorrect initialisation of derived type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59781 --- Comment #18 from Thomas Koenig --- Author: tkoenig Date: Thu Feb 22 22:01:53 2018 New Revision: 257917 URL: https://gcc.gnu.org/viewcvs?rev=257917=gcc=rev Log: 2018-02-22 Thomas Koenig PR fortran/59781

[Bug fortran/59781] [6 Regression] [F03] Incorrect initialisation of derived type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59781 Thomas Koenig changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[PATCH] PR fortran/84346 -- Keywords invalid in statement functions

The attached patch fixes PR fortran/84346. A statement function always has an implicit interface. The use of keywords in a function with an implicit interface is invalid. Regression tested on x86_64-*-freebsd. OK to commit? 2018-02-22 Steven G. Kargl PR

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #12 from Wilco --- Note PR64242 is related (also frame pointer corruption by __builtin_longjmp).

Re: [PATCH] correct -Wrestrict handling of arrays of arrays (PR 84095)

On Friday 02 February 2018 05:15 AM, Martin Sebor wrote: > PR middle-end/84095 - false-positive -Wrestrict warnings for memcpy within > array > > gcc/ChangeLog: > > PR middle-end/84095 > * gimple-ssa-warn-restrict.c (builtin_memref::extend_offset_range): New. >

[Bug c++/84525] New: GCC7: generate movaps instruction when assign to unaligned __int128*

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84525 Bug ID: 84525 Summary: GCC7: generate movaps instruction when assign to unaligned __int128* Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[PATCH] Fix bogus function cast warning for functions with common arg subset

Libraries like gtk/glib[1] and python[2] use functions with common argument subsets to register callbacks. The working idea behind it is to have a flag in the structure (or some other pre-determined method) that specifies how the callback is cast and called. Fix this by not throwing a warning

Re: [RFC PATCH] avoid applying attributes to explicit specializations (PR 83871)

On 02/21/2018 06:03 PM, Martin Sebor wrote: On 02/13/2018 11:33 AM, Jason Merrill wrote: On Tue, Feb 13, 2018 at 1:00 PM, Martin Sebor wrote: On 02/13/2018 07:47 AM, Jason Merrill wrote: On Mon, Feb 12, 2018 at 6:39 PM, Martin Sebor wrote: I really

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #9 from Wilco --- (In reply to Jakub Jelinek from comment #7) > cfun->has_nonlocal_label instead of cfun->calls_setjmp would cover > __builtin_setjmp. Do non-local labels do the same odd thing? It seems to me if the mid-end

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #10 from Ramana Radhakrishnan --- (In reply to Jakub Jelinek from comment #4) > Is the requirement just for functions that contain setjmp? If so, the > backend could just force frame pointers in cfun->calls_setjmp functions. I

[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 --- Comment #11 from Wilco --- (In reply to Ramana Radhakrishnan from comment #10) > (In reply to Jakub Jelinek from comment #4) > > Is the requirement just for functions that contain setjmp? If so, the > > backend could just force frame

Re: [PATCH] PR fortran/84346 -- Keywords invalid in statement functions

Hi Steve, The attached patch fixes PR fortran/84346. A statement function always has an implicit interface. The use of keywords in a function with an implicit interface is invalid. Regression tested on x86_64-*-freebsd. OK to commit? OK. Thanks for the patch! Regards Thomas

[Bug c++/84525] GCC7: generate movaps instruction when assign to unaligned __int128*

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84525 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

Re: [PATCH PR81228][AARCH64][gcc-7] Backport r255625 : Fix ICE by adding LTGT

On 09/01/18 15:37, Sudakshina Das wrote: Hi This patch is only adding the missing LTGT to plug the ICE. This is a backport to r255625 of trunk. Testing done: Checked for regressions on bootstrapped aarch64-none-linux-gnu and added a new compile time test case that gives out LTGT to make

[Bug target/81228] [7 Regression] ICE in gen_vec_cmpv2dfv2di, at config/aarch64/aarch64-simd.md:2508

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81228 --- Comment #10 from sudi at gcc dot gnu.org --- Author: sudi Date: Thu Feb 22 15:01:05 2018 New Revision: 257901 URL: https://gcc.gnu.org/viewcvs?rev=257901=gcc=rev Log: Adding the missing LTGT to plug the ICE in PR81228. This is a backport of

[Bug target/81228] [7 Regression] ICE in gen_vec_cmpv2dfv2di, at config/aarch64/aarch64-simd.md:2508

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81228 sudi at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug c++/84516] New: bitfield temporaries > 32-bits have wrong type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84516 Bug ID: 84516 Summary: bitfield temporaries > 32-bits have wrong type Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [SFN+LVU+IEPM v4 9/9] [IEPM] Introduce inline entry point markers

On 21/02/18 10:11, Alexandre Oliva wrote: On Feb 15, 2018, Szabolcs Nagy wrote: i see assembler slow downs with these location view patches i opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84408 [LVU] reset view at function entry, omit views at line zero

[Bug bootstrap/84402] [meta] GCC build system: parallelism bottleneck

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84402 --- Comment #17 from Tom Tromey --- The results in comment #13 seem to be missing some compilations -- I would have expected to see more files from libcpp in there. As it is I only see directives.o and line-map.o.

[Bug sanitizer/84508] Load of misaligned address using _mm_load_sd

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84508 --- Comment #7 from Marc Glisse --- Unless vectors count as aggregates (more or less), in which case we can ignore my previous comment.

[Bug target/81572] [7/8 Regression] gcc-7 regression: unnecessary vector regmove on compare

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81572 --- Comment #3 from Vladimir Makarov --- I am working on this PR. The patch will be ready today or tomorrow. The problem is that the move insn has one alternative with early clobber and this move insn is processed on a fast path which

[Bug tree-optimization/84515] New: missed optimization: expected loop merging

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84515 Bug ID: 84515 Summary: missed optimization: expected loop merging Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: PING: [PATCH] i386: Add __x86_indirect_thunk_nt_reg for -fcf-protection -mcet

> On Fri, Feb 2, 2018 at 8:54 AM, H.J. Lu wrote: > > nocf_check attribute can be used with -fcf-protection -mcet to disable > > control-flow check by adding NOTRACK prefix before indirect branch. > > When -mindirect-branch=thunk-extern -mindirect-branch-register is added, >

Re: PING: [PATCH] i386: Add TARGET_INDIRECT_BRANCH_REGISTER

> On Sun, Jan 28, 2018 at 11:56 AM, H.J. Lu wrote: > > On Sat, Jan 27, 2018 at 2:12 PM, H.J. Lu wrote: > >> For > >> > >> --- > >> struct C { > >> virtual ~C(); > >> virtual void f(); > >> }; > >> > >> void > >> f (C *p) > >> { > >> p->f(); > >>

Re: PING: [PATCH] i386: Add TARGET_INDIRECT_BRANCH_REGISTER

On Thu, Feb 22, 2018 at 6:29 AM, Jan Hubicka wrote: >> On Sun, Jan 28, 2018 at 11:56 AM, H.J. Lu wrote: >> > On Sat, Jan 27, 2018 at 2:12 PM, H.J. Lu wrote: >> >> For >> >> >> >> --- >> >> struct C { >> >> virtual ~C(); >> >>

Re: PING: [PATCH] i386: Add TARGET_INDIRECT_BRANCH_REGISTER

> >> > >> Hi Jan, > >> > >> https://gcc.gnu.org/ml/gcc-patches/2018-01/msg02233.html > >> > >> Is OK for trunk? > > > > I see that using register makes the problem go away and pushing address to > > stack > > seemed bit odd anyway. However how does this work on other types of thunk? > > Kernel

<    1   2