[v3 PATCH] PR 67844

Tested on Linux-PPC64. The problem is a tad tricky, since the bug triggered by the testcase is in a constructor that will not be used, but will cause endless meta-recursion via checking convertibility of an incomplete type that will cause further recursion. While there might be ways to fix that in

Re: [PATCH] SH FDPIC backend support

On Sun, Oct 04, 2015 at 02:10:42PM +0900, Oleg Endo wrote: > On Sat, 2015-10-03 at 18:34 -0400, Rich Felker wrote: > > > > > > I found and fixed the problem, but I have a new concern: calls to the > > > new shift instructions are using the following address forms: > > > > > > -mno-fdpic -fPIC: >

[PATCH 4/4] make more gimple_x_ptr accessors const correct

From: Trevor Saunders gcc/ChangeLog: 2015-10-04 Trevor Saunders * gimple.h (gimple_op_ptr): Require a non const gimple *. (gimple_assign_lhs_ptr): Likewise. (gimple_assign_rhs1_ptr): Likewise. (gimple_assign_rhs2_ptr): Likewise. (gimple_assign_rhs3_ptr

[PATCH 3/4] remove unused gasm accessors

From: Trevor Saunders gcc/ChangeLog: 2015-10-04 Trevor Saunders * gimple.h (gimple_asm_input_op_ptr): Remove. (gimple_asm_output_op_ptr): Likewise. --- gcc/gimple.h | 20 1 file changed, 20 deletions(-) diff --git a/gcc/gimple.h b/gcc/gimple.h index cfd

[PATCH 2/4] remove gimple_location_ptr ()

From: Trevor Saunders gcc/ChangeLog: 2015-10-04 Trevor Saunders * gimple.h (gimple_location_ptr): Remove. * tree-vrp.c (check_all_array_refs): Adjust. --- gcc/gimple.h | 9 - gcc/tree-vrp.c | 5 +++-- 2 files changed, 3 insertions(+), 11 deletions(-) diff --git a/

[PATCH 0/4] gimple accessor const correctness fixes

From: Trevor Saunders Hi, the first patch is just some cleanup I ran into along the way, but the rest of this series fixes const correctness for all of the gimple_x_ptr () functions. I was able to just remove a couple of them, but unfortunately most ar needed for either tree walking, or the use

[PATCH 1/4] make build_uses store tree * instead of tree

From: Trevor Saunders gcc/ChangeLog: 2015-10-04 Trevor Saunders * tree-ssa-operands.c (build_uses): store tree * instead of tree. (finalize_ssa_uses): Adjust. (append_use): Likewise. (verify_ssa_operands): Likewise. --- gcc/tree-ssa-operands.c | 30 ++

Re: [PATCH] x86 interrupt attribute

On Sun, Oct 4, 2015 at 2:07 PM, Uros Bizjak wrote: > On Sun, Oct 4, 2015 at 10:51 PM, H.J. Lu wrote: >> On Sun, Oct 4, 2015 at 1:00 PM, Uros Bizjak wrote: >>> On Sun, Oct 4, 2015 at 8:15 PM, H.J. Lu wrote: >>> > Looking a bit deeper into the code, it looks that we want to realign > the

Re: [gomp4.1] fix more scheduling inconsistencies and add verification routines

On 10/04/2015 10:26 AM, Aldy Hernandez wrote: However magically this happened before :), my attached changes to gomp_task_run_pre() will move this task to the end of the queue such that the WAITING tasks are first. FWIW, thinking about this some more, I suppose setting a task to GOMP_TASK_TIE

Re: [PATCH] x86 interrupt attribute

On Sun, Oct 4, 2015 at 10:51 PM, H.J. Lu wrote: > On Sun, Oct 4, 2015 at 1:00 PM, Uros Bizjak wrote: >> On Sun, Oct 4, 2015 at 8:15 PM, H.J. Lu wrote: >> Looking a bit deeper into the code, it looks that we want to realign the stack in the interrupt handler. Let's assume that interrupt

Re: [PATCH] x86 interrupt attribute

On Sun, Oct 4, 2015 at 1:00 PM, Uros Bizjak wrote: > On Sun, Oct 4, 2015 at 8:15 PM, H.J. Lu wrote: > >>> Looking a bit deeper into the code, it looks that we want to realign >>> the stack in the interrupt handler. Let's assume that interrupt >>> handler is calling some other function that saves

Re: [PATCH] x86 interrupt attribute

On Sun, Oct 4, 2015 at 8:15 PM, H.J. Lu wrote: >> Looking a bit deeper into the code, it looks that we want to realign >> the stack in the interrupt handler. Let's assume that interrupt >> handler is calling some other function that saves SSE vector regs to >> the stack. According to the x86 ABI,

Re: [PATCH] x86 interrupt attribute

On Sun, Oct 4, 2015 at 3:29 AM, Uros Bizjak wrote: > On Sun, Oct 4, 2015 at 7:23 AM, Yulia Koval wrote: >> Hi, >> >> Here is the last version of the patch. Regtested/bootstraped for >> Linux/i686 and Linux/x86_64. >> >> Date: Fri, 4 Sep 2015 08:53:23 -0700 >> Subject: [PATCH] Implement x86 interr

[gomp4.1] fix more scheduling inconsistencies and add verification routines

Jakub, this is the inconsistency you pointed out while we were analyzing the scheduling circular lists. The problem in gomp_task_run_pre() is that, upon setting an upcoming running task to TIED, we may leave either the sibling or taskgroup queues in an indeterminate state. We may have upcomin

[PATCH, i386]: Add a testcase for PR67447 (AKA 67756), insn does not satisfy its constraints

This PR was fixed by [1]. This patch adds the testcase from PR that failed on x86 target for the same reason. 2015-10-04 Uros Bizjak PR rtl-optimization/67447 * gcc.target/i386/pr67447.c: New test. Tested on x86_64-linux-gnu {,-m32} and committed to mainline SVN. [1] https://gcc.gnu

Re: [PING][PR67476] Add param parloops-schedule

On 22/09/15 12:58, Bernd Schmidt wrote: On 09/22/2015 09:19 AM, Tom de Vries wrote: These two patches: - https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00938.html - https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00940.html add a param parloop-schedule=. The problem I have when trying to review t

[RFC PATCH, i386]: Allow -mincoming-stack-boundary=3 for x86_64

Hello! As shown in PR 66697 [1] and WineHQ bug [2], an application can misalign incoming stack to less than ABI mandated 16 bytes. While it is possible to use -mincoming-stack-boundary=2 (= 4 bytes) for 32 bit targets to emit stack realignment code, this option is artificially limited to 4 (= 16

[PATCH, i386]: Tighten check for GP register in pro/epilogue register save/restore functions

Hello! Attached patch tightens the check for general purpose register in prologue and epilogue register save/restore functions. These functions handle GP regs exclusively. 2015-10-04 Uros Bizjak * config/i386/i386.c (ix86_nsaved_regs): Use GENERAL_REGNO_P to check for general register

Re: [PATCH, i386, AVX-512] Update extract_even_odd w/ AVX-512BW insns.

On Sat, Oct 3, 2015 at 12:49 PM, Dominique d'Humières wrote: > Kirill, > > The new tests fail on x86_64-apple-darwin14: > > FAIL: gcc.target/i386/vect-pack-trunc-1.c (test for excess errors) > UNRESOLVED: gcc.target/i386/vect-pack-trunc-1.c compilation failed to produce > executable > FAIL: gcc.t

[fortran, committed] Remove dead code

Hello, I found an unused variable when working on pr67758. Committed as revision 228458. Mikael Index: ChangeLog === --- ChangeLog (révision 228457) +++ ChangeLog (révision 228458) @@ -1,5 +1,9 @@ 2015-10-04 Mikael Morin +

[Patch, fortran, 5] Bakport Andre's r222477 deep copy fix for PR67818

Hello, my recent PR67721 patch [1] introduced a regression [2] on the 5 branch. [1] https://gcc.gnu.org/ml/gcc-patches/2015-09/msg02048.html [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67818 The patch [1] introduces more deep copies, but deep copies have been somewhat broken, until Andre f

Re: [wwwdocs] Buildstat update for 4.9

On Sun, 13 Sep 2015, Tom G. Christensen wrote: > Latest results for 4.9.x Thanks, applied. Sorry for the delay - recovering from a harddrive failure. Gerald

Re: [Patch] [x86_64] znver1 enablement

On Sun, Oct 4, 2015 at 8:46 AM, Kumar, Venkataramanan wrote: > GCC bootstrap completed with and without -march=znver1. > Ok for trunk after completing gcc regression tests ? > > ChangeLog: > * config.gcc (i[34567]86-*-linux* | ...): Add znver1. > (case ${target})

Re: [PATCH] x86 interrupt attribute

On Sun, Oct 4, 2015 at 7:23 AM, Yulia Koval wrote: > Hi, > > Here is the last version of the patch. Regtested/bootstraped for > Linux/i686 and Linux/x86_64. > > Date: Fri, 4 Sep 2015 08:53:23 -0700 > Subject: [PATCH] Implement x86 interrupt attribute > > The interrupt and exception handlers are ca