[Bug libgomp/83589] [nvptx] mode-transitions.c and private-variables.{c,f90} execution FAILs at GOMP_NVPTX_JIT=-O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83589 --- Comment #3 from Tom de Vries --- (In reply to Tom de Vries from comment #2) > This looks like another nvidia driver problem (with driver version 384.111). Confirmed. The empty branch > @ %r36 bra $L5; > $L5: is translated into: ...

Re: [PATCH] Fix tree-emutls ADDR_EXPR handling (PR middle-end/83945)

On January 19, 2018 10:52:08 PM GMT+01:00, Jakub Jelinek wrote: >Hi! > >Before emutls lowering, expressions like _REF[(whatever)].a >for static __thread e is considered gimple invariant (after all, for >native TLS we do that too) and gimple invariants are shareable trees.

Re: [PATCH] Fix UMOD rtx simplification (PR target/83930)

On January 19, 2018 10:29:36 PM GMT+01:00, Jakub Jelinek wrote: >Hi! > >THis bug has been introduced 16.5 years ago. If >simplify_binary_operation_1 >is called with op1 (MEM) on which avoid_constant_pool_reference returns >something simpler, for UMOD simplification we check

[Bug fortran/83900] [8 Regression] ICE in gfc_simplify_matmul, at fortran/simplify.c:4593

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83900 --- Comment #6 from kargl at gcc dot gnu.org --- Author: kargl Date: Sat Jan 20 07:00:43 2018 New Revision: 256913 URL: https://gcc.gnu.org/viewcvs?rev=256913=gcc=rev Log: 2018-01-19 Steven G. Kargl PR

[Committed] PR fortran/83900 -- Remove bogus assert

The patch and testcase are sufficient to describe the problem. 2018-01-19 Steven G. Kargl PR fortran/83900 * simplify.c (gfc_simplify_matmul): Delete bogus assertion. 2018-01-19 Steven G. Kargl PR fortran/83900 *

[Bug fortran/83900] [8 Regression] ICE in gfc_simplify_matmul, at fortran/simplify.c:4593

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83900 --- Comment #5 from kargl at gcc dot gnu.org --- Author: kargl Date: Sat Jan 20 06:15:55 2018 New Revision: 256912 URL: https://gcc.gnu.org/viewcvs?rev=256912=gcc=rev Log: 2018-01-19 Steven G. Kargl PR

[Bug c++/83950] New: [8 regression] error: no matching function for call to ‘folly::dynamic::at(size_t&) const’

const int ::p() { m jpool; auto json = jpool.json; try { auto jservers = json.j(""); for (size_t i;;) jservers->at(i); } catch (int) { } } $ g++ --version g++ (GCC) 8.0.1 20180119 (experimental) Copyright (C) 2018 Free Software Foundation, Inc. This is fr

[Bug fortran/66310] Problems with intrinsic repeat for large number of copies

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66310 --- Comment #18 from Jerry DeLisle --- Can this be closed.

[PATCH v3, rs6000] Use $ instead of . for PC, use "crset 2" instead of "crset eq"

Hi, Here's another version of this patch incorporating the late-breaking news that the AIX assembler doesn't comprehend the "eq" symbol. Same as https://gcc.gnu.org/ml/gcc-patches/2018-01/msg01787.html but adding the change to use "crset 2" instead. This one is still regstrapping on BE/LE,

Re: [PATCH] C/C++: Add -Waddress-of-packed-member

On 01/19/2018 10:14 AM, Martin Sebor wrote: On 01/14/2018 07:29 AM, 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 warn it: $ cat x.i struct pair_t { char c; int i; }

[PATCH, rs6000] Requested cleanups for BE handling of -mno-speculate-indirect-jumps

Hi, Segher had previously requested some cleanups in https://gcc.gnu.org/ml/gcc-patches/2018-01/msg01605.html. Due to time pressures, I delayed those, but they are ready now. Here they are, bootstrapped and tested on powerpc64le-linux-gnu and powerpc64-linux-gnu. Is this okay for trunk? I

Re: [PATCH v2, rs6000] Use $ instead of . for PC

Forgot to mention, these have also been tested successfully as backports in gcc-7-branch. Okay to fix there as well? Thanks, Bill > On Jan 19, 2018, at 9:31 PM, Bill Schmidt wrote: > > Hi, > > Here's the same patch with corrected test cases. This has now passed

[PATCH v2, rs6000] Use $ instead of . for PC

Hi, Here's the same patch with corrected test cases. This has now passed bootstrap and testing on powerpc64-linux-gnu and powerpc64le-linux-gnu with no regressions. Is this okay for trunk? Hopefully tomorrow early I will have a separate patch also changing "setcr eq" to "setcr 2" to

Re: [PATCH, rs6000] Use $ instead of . for PC

> On Jan 19, 2018, at 7:53 PM, David Edelsohn wrote: > > On Fri, Jan 19, 2018 at 3:58 PM, Bill Schmidt > wrote: >> Hi, >> >> My recent patches to trunk and gcc-7-branch for avoiding speculation of >> indirect branches has a flaw, pointed out by

Re: [PATCH, rs6000] Use $ instead of . for PC

On Fri, Jan 19, 2018 at 08:53:52PM -0500, David Edelsohn wrote: > On Fri, Jan 19, 2018 at 3:58 PM, Bill Schmidt > wrote: > > Hi, > > > > My recent patches to trunk and gcc-7-branch for avoiding speculation of > > indirect branches has a flaw, pointed out by David.

Re: [C++ Patch] PR 83921 ("[7/8 Regression] GCC rejects constexpr initialization of empty aggregate")

Hi again, On 19/01/2018 23:55, Paolo Carlini wrote: ...Therefore It seems to me that a way to more cleanly solve the bug would be moving something like || !DECL_NONTRIVIALLY_INITIALIZED_P to the the above check in check_for_uninitialized_const_var, and therefore remove completely the

Re: [PATCH, rs6000] Use $ instead of . for PC

On Fri, Jan 19, 2018 at 3:58 PM, Bill Schmidt wrote: > Hi, > > My recent patches to trunk and gcc-7-branch for avoiding speculation of > indirect branches has a flaw, pointed out by David. Usage of "." to > represent the program counter is not portable across all

Re: Status of m32c target?

On 01/19/2018 10:14 AM, Jeff Law wrote: cc0 needs to die. That doesn't mean that any particular target needs to be dropped -- it just means that someone has to step forward to do the conversion. Unifying two parallel threads: might this be a good project for GSoC? -Sandra

[Bug fortran/80768] NULL pointer dereferenced in gfc_check_num_images at fortran/check.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80768 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 Status|NEW

[Bug fortran/80768] NULL pointer dereferenced in gfc_check_num_images at fortran/check.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80768 --- Comment #9 from kargl at gcc dot gnu.org --- Author: kargl Date: Fri Jan 19 23:51:18 2018 New Revision: 256908 URL: https://gcc.gnu.org/viewcvs?rev=256908=gcc=rev Log: 2018-01-19 Steven G. Kargl Backport of

[Bug fortran/80768] NULL pointer dereferenced in gfc_check_num_images at fortran/check.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80768 --- Comment #8 from kargl at gcc dot gnu.org --- Author: kargl Date: Fri Jan 19 23:37:29 2018 New Revision: 256907 URL: https://gcc.gnu.org/viewcvs?rev=256907=gcc=rev Log: 2018-01-19 Steven G. Kargl Backport of

Re: [PATCH, x86, libgcc] PR target/83917 Correct debug for -mcall-ms2sysv-xlogues stubs

On Fri, Jan 19, 2018 at 05:33:10PM -0600, Daniel Santos wrote: > When stepping through tail-call restore stubs the debugger has to assume > that rsp - 8 is the CFA, although it is not. This is because I did not > explicitly add any .cfi directives. This patch adds them to the > tail-call restore

[Committed] PR fortran/80768 -- testcase

Jakub fixed a typo in --- r250734 | jakub | 2017-07-31 02:32:02 -0700 (Mon, 31 Jul 2017) | 2 lines * check.c (gfc_check_num_images): Fix a pasto. but he seemed to be unaware of PR fortran/80768. I've converted to code

[Bug fortran/80768] NULL pointer dereferenced in gfc_check_num_images at fortran/check.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80768 --- Comment #7 from kargl at gcc dot gnu.org --- Author: kargl Date: Fri Jan 19 23:28:18 2018 New Revision: 256906 URL: https://gcc.gnu.org/viewcvs?rev=256906=gcc=rev Log: 2018-01-19 Steven G. Kargl PR

[PATCH, x86, libgcc] PR target/83917 Correct debug for -mcall-ms2sysv-xlogues stubs

When stepping through tail-call restore stubs the debugger has to assume that rsp - 8 is the CFA, although it is not. This is because I did not explicitly add any .cfi directives. This patch adds them to the tail-call restore stubs, but this is new territory for me, so I would appreciate

[Bug debug/83728] [8 regression] FAIL: gcc.dg/guality/pr68037-1.c

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

[Bug c++/83919] [8 regression] spurious -Wignored-qualifiers warning

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

[Bug c++/81167] [8 Regression] ICE on valid C++ code in deferred_printed_type, at cp/error.c:118

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

[Bug libstdc++/61458] std::aligned_storage is bigger than expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61458 Arthur O'Dwyer changed: What|Removed |Added CC||arthur.j.odwyer at gmail dot com ---

Re: [C++ Patch] PR 83921 ("[7/8 Regression] GCC rejects constexpr initialization of empty aggregate")

Hi, On 19/01/2018 23:28, Jason Merrill wrote: On Thu, Jan 18, 2018 at 5:53 PM, Paolo Carlini wrote: Hi, I'm finishing testing on x86_64-linux the below - which anyway seems very unlikely to cause regressions because we aren't really stress testing the relevant

[C++] Deprecate old for-scope handling

Jason, what do you think about deprecating the ARM-era for-scope handling that allows: void f () { for (int i = 0;;); i = 2; } we noisily accept that in c++98 mode with -fpermissive. It wasn't even well formed then. Implementing this has some unique requirements in the

Re: [PATCH, fortran] Support Fortran 2018 teams

I can confirm that the little change suggested by Steve passes the regtests (on x86_64-pc-linux-gnu) and the regular tests using OpenCoarrays. On Fri, Jan 19, 2018 at 10:33 AM, Steve Kargl wrote: > On Fri, Jan 19, 2018 at 09:18:14AM -0800, Damian Rouson wrote:

[Bug c++/83949] internal compiler error: Segmentation fault (only with -g)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83949 --- Comment #3 from Peter Foelsche --- also happens with pfoelsch@TXA-PFOELSCH-LT:/mnt/d/BSIMSOI$ g++-7 --version g++-7 (Ubuntu 7.2.0-1ubuntu1~16.04) 7.2.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source

[Bug c++/81167] [8 Regression] ICE on valid C++ code in deferred_printed_type, at cp/error.c:118

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81167 --- Comment #10 from Jakub Jelinek --- Author: jakub Date: Fri Jan 19 22:37:37 2018 New Revision: 256905 URL: https://gcc.gnu.org/viewcvs?rev=256905=gcc=rev Log: PR c++/81167 * call.c (joust): Use TREE_TYPE (source) if source is

[Bug debug/83728] [8 regression] FAIL: gcc.dg/guality/pr68037-1.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83728 --- Comment #7 from Jakub Jelinek --- Author: jakub Date: Fri Jan 19 22:36:04 2018 New Revision: 256904 URL: https://gcc.gnu.org/viewcvs?rev=256904=gcc=rev Log: PR debug/81570 PR debug/83728 * dwarf2cfi.c

[Bug debug/81570] create_pseudo_cfg assumes that INCOMING_FRAME_SP_OFFSET is a constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81570 --- Comment #7 from Jakub Jelinek --- Author: jakub Date: Fri Jan 19 22:36:04 2018 New Revision: 256904 URL: https://gcc.gnu.org/viewcvs?rev=256904=gcc=rev Log: PR debug/81570 PR debug/83728 * dwarf2cfi.c

[Bug c++/83919] [8 regression] spurious -Wignored-qualifiers warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83919 --- Comment #3 from Jakub Jelinek --- Author: jakub Date: Fri Jan 19 22:35:09 2018 New Revision: 256903 URL: https://gcc.gnu.org/viewcvs?rev=256903=gcc=rev Log: PR c++/83919 * typeck.c (convert_for_assignment): Suppress

Re: [PATCH, rs6000] Use $ instead of . for PC

> On Jan 19, 2018, at 3:58 PM, Segher Boessenkool > wrote: > > On Fri, Jan 19, 2018 at 10:20:23PM +0100, Andreas Schwab wrote: >> On Jan 19 2018, Bill Schmidt wrote: >> On Jan 19, 2018, at 3:09 PM, Jakub Jelinek

Re: [C++ Patch] PR 83921 ("[7/8 Regression] GCC rejects constexpr initialization of empty aggregate")

On Thu, Jan 18, 2018 at 5:53 PM, Paolo Carlini wrote: > Hi, > > I'm finishing testing on x86_64-linux the below - which anyway seems very > unlikely to cause regressions because we aren't really stress testing the > relevant checks in potential_constant_expression_1

Re: [C++ PATCH] Avoid spurious -Wignored-qualifiers warning on artificial C++17 P0138R2 cast (PR c++/83919)

OK. On Thu, Jan 18, 2018 at 6:17 PM, Jakub Jelinek wrote: > Hi! > > These casts for P0138R2 isn't something the user typed in their code, > so diagnosing -Wignored-qualifiers on these looks wrong. > -Wuseless-cast has been handled similarly in the past already. > >

[Bug c++/83949] internal compiler error: Segmentation fault (only with -g)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83949 --- Comment #2 from Peter Foelsche --- Created attachment 43193 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43193=edit *.ii compressed

Re: [PATCH] Fix unwind info in x86 interrupt functions (PR debug/83728)

On Thu, Jan 18, 2018 at 6:28 PM, Jakub Jelinek wrote: > Last summer i386 INCOMING_FRAME_SP_OFFSET macro has been changed, so that it > is one word for most of the functions (as previously always), but 2 words > for functions with interrupt attribute. > Unfortunately this breaks

patch to fix PR83147

The following patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83147 The patch was successfully boostrapped and tested on x86_64. There is no test for the patch because a test from the PR does not reproduce the bug anymore. Committed as rev. 256902. Index: ChangeLog

[Bug c++/83949] internal compiler error: Segmentation fault (only with -g)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83949 --- Comment #1 from Peter Foelsche --- Created attachment 43192 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43192=edit compiler stdout/stderr

Re: [C++ PATCH] Fix ICE in joust with -Wconversion (PR c++/81167)

On Thu, Jan 18, 2018 at 6:35 PM, Jakub Jelinek wrote: > Hi! > > As mentioned in the PR, we ICE on this testcase because > w->fn is a conversion operator, w->convs[0]->type is a reference > to a class type, but because that conversion is ck_ref_bind, > source_type looks through

[Bug c++/83949] New: internal compiler error: Segmentation fault (only with -g)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83949 Bug ID: 83949 Summary: internal compiler error: Segmentation fault (only with -g) Product: gcc Version: 5.3.0 Status: UNCONFIRMED Severity: normal

[Bug rtl-optimization/83147] LRA inheritance undo on multiple sets problem

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83147 --- Comment #4 from Vladimir Makarov --- Author: vmakarov Date: Fri Jan 19 22:16:30 2018 New Revision: 256902 URL: https://gcc.gnu.org/viewcvs?rev=256902=gcc=rev Log: 2018-01-19 Andreas Krebbel PR

RE: internal compiler error: Segmentation fault (all required info contained)

Note that crash only happens when using -g Peter -Original Message- From: gcc-bugs-ow...@gcc.gnu.org [mailto:gcc-bugs-ow...@gcc.gnu.org] On Behalf Of Foelsche, Peter Sent: Friday, January 19, 2018 16:06 To: gcc-bugs@gcc.gnu.org Subject: FW: internal compiler error: Segmentation fault

FW: internal compiler error: Segmentation fault (all required info contained)

I removed the compressed preprocessed file, as your email server does not accept an email of this size. I tried before to get an account at GCC bug tracker but was ignored. Peter From: Foelsche, Peter Sent: Friday, January 19, 2018 16:01 To: 'gcc-bugs@gcc.gnu.org'

[og7,nvptx] Backport CUDA 9 support from trunk.

I've committed this patch to openacc-gcc-7-branch which backports the recent CUDA 9 changes I applied to trunk here . OG7 already had an earlier version of this patch, but Tom requested some changes which went made their way into trunk.

Re: [PATCH, rs6000] Use $ instead of . for PC

On Fri, Jan 19, 2018 at 10:20:23PM +0100, Andreas Schwab wrote: > On Jan 19 2018, Bill Schmidt wrote: > > >> On Jan 19, 2018, at 3:09 PM, Jakub Jelinek wrote: > >> > >> On Fri, Jan 19, 2018 at 02:58:07PM -0600, Bill Schmidt wrote: > >>> ---

[PATCH] Fix tree-emutls ADDR_EXPR handling (PR middle-end/83945)

Hi! Before emutls lowering, expressions like _REF[(whatever)].a for static __thread e is considered gimple invariant (after all, for native TLS we do that too) and gimple invariants are shareable trees. lower_emutls* then has code to update the VAR_DECL in there with an SSA_NAME and if needed,

Re: [PATCH, rs6000] Testcase fix-ups for gimple-folding intrinsic tests.

Hi! On Fri, Jan 19, 2018 at 01:14:08PM -0600, Will Schmidt wrote: > Some testcase fix-ups affecting the gimple-folding tests, including: > - Add xxspltib as a valid instruction for vec-abs tests (power9). > - Fix up mismatched dg-require and dg-option values for the >

[Bug libfortran/83948] Thread safety issue writing to internal file - libgfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83948 --- Comment #1 from Bill Long --- The same code compiles and executes OK at 20 threads with other compilers. The size of the internal file is small (700 bytes).

[Bug libfortran/83948] New: Thread safety issue writing to internal file - libgfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83948 Bug ID: 83948 Summary: Thread safety issue writing to internal file - libgfortran Product: gcc Version: 7.2.0 Status: UNCONFIRMED Severity: normal

[PATCH] Fix branch probability computation in do_compare_rtx_and_jump (PR tree-optimization/83081)

Hi! This PR is about a certain test FAILing on arm, because it scans for "Invalid sum ..." message in the *.ira dump, but recent GCC versions have that message in there; not introduced by IRA though, but all the way from expansion. We are expanding: [local count: 1073741825]: _1 = *x_3(D);

[Bug middle-end/78809] Inline strcmp with small constant strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809 --- Comment #25 from Wilco --- (In reply to Qing Zhao from comment #24) > From the above, we can see: > even with n is as big as 20, inlined version is much faster than the > non-inlined version, both on aarch64 (no hardware string compare

[Bug c++/83947] New: ICE on invalid C++ code with auto: in tsubst_decl, at cp/pt.c:13046

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83947 Bug ID: 83947 Summary: ICE on invalid C++ code with auto: in tsubst_decl, at cp/pt.c:13046 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[PATCH] Fix UMOD rtx simplification (PR target/83930)

Hi! THis bug has been introduced 16.5 years ago. If simplify_binary_operation_1 is called with op1 (MEM) on which avoid_constant_pool_reference returns something simpler, for UMOD simplification we check that trueop1 is CONST_INT and power of 2, but then we use INTVAL of the op1 (MEM). Fixed by

Re: [PATCH, rs6000] Use $ instead of . for PC

On Jan 19 2018, Bill Schmidt wrote: >> On Jan 19, 2018, at 3:09 PM, Jakub Jelinek wrote: >> >> On Fri, Jan 19, 2018 at 02:58:07PM -0600, Bill Schmidt wrote: >>> --- gcc/testsuite/gcc.target/powerpc/safe-indirect-jump-2.c (revision >>> 256894) >>>

Re: Status of m32c target?

On Fri, Jan 19, 2018 at 07:58:02PM +0100, Eric Botcazou wrote: > > - cc0 does a good job and did always a good job in the past. In the > > years I contributed to avr, there hasn't been a single cc0 flaw (all the > > few, minor cc0-related issues were avr BE issues). cc0 does not do a good job at

Re: [PATCH, rs6000] Use $ instead of . for PC

> On Jan 19, 2018, at 3:09 PM, Jakub Jelinek wrote: > > On Fri, Jan 19, 2018 at 02:58:07PM -0600, Bill Schmidt wrote: >> --- gcc/testsuite/gcc.target/powerpc/safe-indirect-jump-2.c (revision >> 256894) >> +++ gcc/testsuite/gcc.target/powerpc/safe-indirect-jump-2.c (working

Re: [PATCH, rs6000] Use $ instead of . for PC

On Fri, Jan 19, 2018 at 02:58:07PM -0600, Bill Schmidt wrote: > --- gcc/testsuite/gcc.target/powerpc/safe-indirect-jump-2.c (revision > 256894) > +++ gcc/testsuite/gcc.target/powerpc/safe-indirect-jump-2.c (working copy) > @@ -30,4 +30,4 @@ int foo (int x) > > /* { dg-final {

[Bug target/83946] [7/8 Regression] Safe Indirect Jumps broken on AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83946 Bill Schmidt changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |wschmidt at gcc dot gnu.org ---

Re: [PATCH, rs6000] Use $ instead of . for PC

I see that David already proposed this same patch in PR83946. Sorry, I've gotten behind on my email. Two changes I need: The scan-assembly should have \$ rather than $ in it, and I should add PR83946 to the ChangeLog. Sorry for the noise. -- Bill Bill Schmidt, Ph.D. STSM, GCC Architect for

[PATCH, rs6000] Use $ instead of . for PC

Hi, My recent patches to trunk and gcc-7-branch for avoiding speculation of indirect branches has a flaw, pointed out by David. Usage of "." to represent the program counter is not portable across all POWER assemblers, particularly not being accepted on AIX. "$" is the universally accepted

Re: [PATCH v2, rs6000] Implement 32- and 64-bit BE handling for -mno-speculate-indirect-jumps

On Jan 19, 2018, at 12:32 PM, David Edelsohn wrote: > > This patch is incorrect for AIX. Which also means that the backport > to GCC 7 branch is incorrect for AIX and must be corrected before the > release. > > AIX assembler does not accept "." (period) as the current

Re: [PATCH v3, rs6000] Add -mspeculate-indirect-jumps option and implement non-speculating bctr / bctrl

On Fri, Jan 19, 2018 at 10:01:50AM -0700, Sandra Loosemore wrote: > > I see no documentation for the new option here :-( +;; -mno-speculate-indirect-jumps adds deliberate misprediction to indirect +;; branches via the CTR. +mspeculate-indirect-jumps +Target Undocumented

Re: [C++ PATCH] Speed up inplace_merge algorithm & fix inefficient logic(PR c++/83938)

This is a libstdc++ bug and patch, not the C++ front end. So I'm adding the libstdc++ list to CC. On Fri, Jan 19, 2018 at 3:02 AM, chang jc wrote: > Current std::inplace_merge() suffers from performance issue by inefficient > logic under limited memory, > > It leads to

Re: Small C++ tweak to fold_simple

On Fri, Jan 19, 2018 at 8:28 AM, Marek Polacek wrote: > fold_simple struck me as odd, certainly the NULL_TREE assignment is > unnecessary, so this patch simplifies it a bit. OK. > I've been confused about the commentary too, what is the difference between >

[Bug middle-end/78809] Inline strcmp with small constant strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809 --- Comment #24 from Qing Zhao --- From the above, we can see: even with n is as big as 20, inlined version is much faster than the non-inlined version, both on aarch64 (no hardware string compare insn provided) and X86 (hardware string

[Bug middle-end/78809] Inline strcmp with small constant strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809 --- Comment #23 from Qing Zhao --- I have an implementation for the part C of this task in my private space: part C: for strcmp (s1, s2), strncmp (s1, s2, n): if the result is NOT used to do simple equality test against zero, one of

[Bug target/83946] [7/8 Regression] Safe Indirect Jumps broken on AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83946 --- Comment #4 from David Edelsohn --- The rest of rs6000.md uses "$" unconditionally for the same purpose, although common parts of GCC uses ".".

[Bug target/83946] [7/8 Regression] Safe Indirect Jumps broken on AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83946 --- Comment #3 from Jakub Jelinek --- Does $ instead of . work on non-AIX though, and even if it does, isn't . preferrable? I.e. shouldn't the changes be conditional on AIX (or just AIX assembler, GAS should handle . on all targets)?

[Bug target/83946] [7/8 Regression] Safe Indirect Jumps broken on AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83946 --- Comment #2 from David Edelsohn --- Created attachment 43191 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43191=edit proposed patch

[PATCH, rs6000] Testcase fix-ups for gimple-folding intrinsic tests.

Hi, Some testcase fix-ups affecting the gimple-folding tests, including: - Add xxspltib as a valid instruction for vec-abs tests (power9). - Fix up mismatched dg-require and dg-option values for the fold-vec-shift-left-longlong tests (fixes/eliminates a test failure on p6). Sniff tested

[Bug target/83660] ICE with vec_extract inside expression statement

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83660 kelvin at gcc dot gnu.org changed: What|Removed |Added Assignee|kelvin at gcc dot gnu.org |unassigned at gcc dot

[Bug target/82303] Better PIE/PIC code generation for kernel code (x86_64 & arm64)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82303 --- Comment #10 from H.J. Lu --- (In reply to Thomas Garnier from comment #9) > I tested the change against a modified version of the proposed Linux x86_64 > PIE support. The changes removes all the PLT32 and GOT64 entry but I still > get

[Bug target/83946] [7/8 Regression] Safe Indirect Jumps broken on AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83946 David Edelsohn changed: What|Removed |Added Priority|P3 |P1 Status|UNCONFIRMED

[Bug target/83946] New: [7/8 Regression] Safe Indirect Jumps broken on AIX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83946 Bug ID: 83946 Summary: [7/8 Regression] Safe Indirect Jumps broken on AIX Product: gcc Version: 7.2.1 Status: UNCONFIRMED Severity: blocker Priority: P3

Re: Status of m32c target?

> Yes, I know that CCmode can represent condition code. But just the fact > that it can represent it doesn't make it superior or cc0 inferior or > bad. Having different representations for the same thing has also its > obvious upsides (think of different representations in maths or > physics),

[Bug target/82303] Better PIE/PIC code generation for kernel code (x86_64 & arm64)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82303 --- Comment #9 from Thomas Garnier --- I tested the change against a modified version of the proposed Linux x86_64 PIE support. The changes removes all the PLT32 and GOT64 entry but I still get R_X86_64_GOTPC64 & R_X86_64_GOTOFF64 relocations on

[Bug target/82303] Better PIE/PIC code generation for kernel code (x86_64 & arm64)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82303 Thomas Garnier changed: What|Removed |Added Attachment #43189|0 |1 is obsolete|

[Bug fortran/83901] [8 Regresion] ICE in fold_convert_loc, at fold-const.c:2402

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83901 Paul Thomas changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org ---

[Bug target/82303] Better PIE/PIC code generation for kernel code (x86_64 & arm64)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82303 --- Comment #7 from Thomas Garnier --- Created attachment 43189 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43189=edit testcase for mcmodel=large Build with: gcc -mcmodel=large -c -fstatic-pie ./test.c -o test Dump relocations on the

[Bug middle-end/83945] [7/8 Regression] internal compiler error: Segmentation fault with -O -fcode-hoisting

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83945 --- Comment #4 from Jakub Jelinek --- *** Bug 83944 has been marked as a duplicate of this bug. ***

[Bug middle-end/83945] [7/8 Regression] internal compiler error: Segmentation fault with -O -fcode-hoisting

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83945 --- Comment #5 from Jakub Jelinek --- *** Bug 83943 has been marked as a duplicate of this bug. ***

[Bug c/83943] internal compiler error: in get_constraint_for_ptr_offset, at tree-ssa-structalias.c:3155

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

[Bug c/83944] internal compiler error: Segmentation fault with -O -ftree-pre

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

[Bug middle-end/83945] [7/8 Regression] internal compiler error: Segmentation fault with -O -fcode-hoisting

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83945 Jakub Jelinek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

Re: [PATCH v2, rs6000] Implement 32- and 64-bit BE handling for -mno-speculate-indirect-jumps

This patch is incorrect for AIX. Which also means that the backport to GCC 7 branch is incorrect for AIX and must be corrected before the release. AIX assembler does not accept "." (period) as the current address. "b ." is incorrect. And testing for "b ." is incorrect. I am going to try

Re: [PATCH, rs6000] Add 128-bit support for vec_xl(), vec_xl_be(), vec_xst(), vec_xst_be() builtins.

On Fri, 2018-01-19 at 10:13 -0600, Segher Boessenkool wrote: > On Thu, Jan 18, 2018 at 04:51:47PM -0600, Segher Boessenkool wrote: > > > +(define_insn "vsx_ld_elemrev_v1ti" > > > +  [(set (match_operand:V1TI 0 "vsx_register_operand" "=wa") > > > +(vec_select:V1TI > > > +   

Re: [PATCH] Add gcc.dg/stack-check-16.c

On 01/19/2018 04:22 AM, Jakub Jelinek wrote: > Hi! > > This patch adds a new testcases, not exactly sure what is the exact > origin and what was the problem. The changes I've done are: > 1) macroize, so that the test is just a few lines rather than 160KB, >verified -fdump-tree-gimple printf

Re: [PATCH, rs6000] Add 128-bit support for vec_xl(), vec_xl_be(), vec_xst(), vec_xst_be() builtins.

On Fri, 2018-01-19 at 10:13 -0600, Segher Boessenkool wrote: > On Thu, Jan 18, 2018 at 04:51:47PM -0600, Segher Boessenkool wrote: > > > +(define_insn "vsx_ld_elemrev_v1ti" > > > +  [(set (match_operand:V1TI 0 "vsx_register_operand" "=wa") > > > +(vec_select:V1TI > > > +   

Re: [PATCH] rl78 anddi3 improvement

Jeff Law writes: > So I think you're ultimately far better off determining why GCC does not > generate efficient code for 64bit logicals on the rl78 target. In thinking about this more, one possible reason is that rl78 has an 8-bit WORD_MODE. Which means DImode operations are

Re: FW: [PATCH] rl78 umaxdi3 improvement

"Sebastian Perta" writes: > * config/rl78/rl78.md: New define_expand "umaxdi3". > * config/rl78/rl78.md: New define_expand "smaxdi3". > * config/rl78/rl78.md: New define_expand "smindi3". > * config/rl78/rl78.md: New define_expand "umindi3". >

Re: [PATCH] RL78 UNUSED note setting bug fix in rl78_note_reg_set

Sebastian Perta writes: > * config/rl78/rl78.c (rl78_note_reg_set): fixed dead reg check > for non-QImode registers This is OK. Thanks! Note: in the future; ChangeLog entries should be provided separate from the patch; they rarely apply cleanly anyway. > Index:

Re: [PATCH][ARM] Fix test fail with conflicting -mfloat-abi

On 16/01/18 10:31, Sudakshina Das wrote: Hi Christophe On 12/01/18 18:32, Christophe Lyon wrote: Le 12 janv. 2018 15:26, "Sudakshina Das" a écrit : Hi This patch fixes my earlier test case that fails for arm-none-eabi with explicit user option for -mfloat-abi which

[Bug target/83851] [8 regression] gcc.dg/vect/pr53185-2.c fails on armeb after r256634

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83851 rsandifo at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last

[Bug target/83888] [8 regression] new failures after r256639 on armhf

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83888 rsandifo at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last

  1   2   3   >