Re: [PING^3] Re: Updated autofdo bootstrap and testing patches

Andi Kleen writes: Ping^3! > Andi Kleen writes: > > Ping^2! > >> Andi Kleen writes: >> >> Ping! >> >>> Here's an updated version of the patchkit to enable autofdo bootstrap >>> and testing. It also fixes some autofdo issues. The

[PR71281] ICE on gcc trunk on knl, wsm, ivb and bdw targets

Hi, PR71281 happens when we use factored out negate stmt in other reassociations. Since we don't set the uid for this stmt, we hit the gcc_assert (in reassoc_stmt_dominates_stmt_p) which checks for uid being set. Attached patch fixes this. Regression tested on x86-64-linux-gnu with no new

Re: [PATCH][AArch64] Increase code alignment

On 06/03/16 17:22, Evandro Menezes wrote: On 06/03/16 05:51, Wilco Dijkstra wrote: It looks almost all AArch64 cores agree on alignment of 16 for function, and 8 for loops and branches, so we should change -mcpu=generic as well if there is no disagreement - feedback welcome. I'll see what

Re: RFC [1/2] divmod transform

On Mon, May 30, 2016 at 12:45 AM, Richard Biener wrote: > Joseph - do you know sth about why there's not a full set of divmod > libfuncs in libgcc? Because udivmoddi4 isn't a libfunc, it is a helper function for the div and mov libfuncs. Since we can compute the signed div

[PR tree-optimization/71316] Fix expected output in testcase after recent threading changes

As outlined in the BZ, this test was partially compromised by the recent threading changes. Those changes result in a jump thread being found during VRP1 rather than DOM2 (ie, earlier in the pipeline, which is good). The expected output needed tweaking for the logical-op-short-circuit

Re: [PR tree-optimization/71328] Fix off-by-one error in CFG/SSA updates for backward threading

On 06/03/2016 01:13 AM, Jakub Jelinek wrote: On Thu, Jun 02, 2016 at 11:24:49PM -0600, Jeff Law wrote: commit 96a568909e429b0f24d61c8a2f3dd3c183d720d7 Author: law Date: Fri Jun 3 05:20:16 2016 + PR tree-optimization/71328 *

Re: [PATCH][AArch64] Increase code alignment

On Fri, Jun 3, 2016 at 3:51 AM, Wilco Dijkstra wrote: > Increase loop alignment on Cortex cores to 8 and set function alignment to > 16. This makes things consistent across big.LITTLE cores, improves > performance of benchmarks with tight loops and reduces performance

Re: [PATCH][AArch64] Increase code alignment

On 06/03/16 05:51, Wilco Dijkstra wrote: It looks almost all AArch64 cores agree on alignment of 16 for function, and 8 for loops and branches, so we should change -mcpu=generic as well if there is no disagreement - feedback welcome. I'll see what sets of values Exynos M1 would be most

Re: [PATCH 3/3][AArch64] Emit division using the Newton series

Rebasing the patch... -- Evandro Menezes >From d791090aae6a29fa94d8fc10894ee1053b05bcc2 Mon Sep 17 00:00:00 2001 From: Evandro Menezes Date: Mon, 4 Apr 2016 14:02:24 -0500 Subject: [PATCH 3/3] [AArch64] Emit division using the Newton series 2016-04-04 Evandro Menezes

Re: [PATCH 1/3][AArch64] Add more choices for the reciprocal square root approximation

On 06/01/16 03:35, James Greenhalgh wrote: On Fri, May 27, 2016 at 05:57:23PM -0500, Evandro Menezes wrote: From 86d7690632d03ec85fd69bfaef8e89c0542518ad Mon Sep 17 00:00:00 2001 From: Evandro Menezes Date: Thu, 3 Mar 2016 18:13:46 -0600 Subject: [PATCH 1/3] [AArch64]

Re: [PATCH 2/3][AArch64] Emit square root using the Newton series

On 06/01/16 04:00, James Greenhalgh wrote: On Fri, May 27, 2016 at 05:57:26PM -0500, Evandro Menezes wrote: 2016-04-04 Evandro Menezes Wilco Dijkstra gcc/ * config/aarch64/aarch64-protos.h

[PATCH] Support x86-64 TLS code sequences without PLT

We can generate x86-64 TLS code sequences for general and local dynamic models without PLT, which uses indirect call via GOT: call *__tls_get_addr@GOTPCREL(%rip) instead of direct call: call __tls_get_addr[@PLT] Since direct call is 4-byte long and indirect call, is 5-byte long, the extra one

Re: RFC [1/2] divmod transform

On Mon, 30 May 2016, Richard Biener wrote: > Joseph - do you know sth about why there's not a full set of divmod > libfuncs in libgcc? I'm not familiar with the choice of divmod libfuncs. -- Joseph S. Myers jos...@codesourcery.com

Re: [PATCH][AArch64] Cleanup -mpc-relative-loads

On 06/03/16 07:56, Wilco Dijkstra wrote: This patch cleans up the -mpc-relative-loads option processing. Rename to avoid the "no*" name and confusing !no* expressions. Fix the option processing code to implement -mno-pc-relative-loads rather than ignore it. OK for commit? LGTM -- Evandro

Re: [PATCH][wwwdocs][AArch64] Mention -mcpu=qdf24xx support for GCC 6

On 06/02/16 09:54, Kyrill Tkachov wrote: The Qualcomm QDF24xx processor is now supported via the Shouldn't this read "The Qualcomm QDF24xx processors are now supported via the"? Not that I have a strong opinion about it, but, otherwise, OK. -- Evandro Menezes

Re: [PATCH] integer overflow checking builtins in constant expressions

On 06/03/2016 09:32 AM, Jakub Jelinek wrote: On Fri, Jun 03, 2016 at 09:29:48AM -0600, Martin Sebor wrote: + { + tree type = TREE_TYPE (TREE_TYPE (t)); + tree vflow = arith_overflowed_p (opcode, type, arg0, arg1) + ? integer_one_node :

Re: [C++ Patch] PR 70202 ("ICE on invalid code in build_simple_base_path, at cp/class.c:579")

OK. Jason

Re: [patch, fortran] PR52393 I/O: "READ format" statement with parenthesized default-char-expr

On Wed, Jun 1, 2016 at 9:28 AM, Jerry DeLisle wrote: > On 06/01/2016 12:25 AM, FX wrote: >>> 2016-05-30 Jerry DeLisle >>> >>> PR fortran/52393 >>> * io.c (match_io): For READ, try to match a default character >>> expression. If

Re: [PATCH][2/3] Vectorize inductions that are live after the loop

On June 3, 2016 7:45:24 PM GMT+02:00, Jakub Jelinek wrote: >On Thu, Jun 02, 2016 at 05:11:15PM +0100, Alan Hayward wrote: >> * gcc.dg/vect/vect-live-1.c: New test. >> * gcc.dg/vect/vect-live-2.c: New test. >> * gcc.dg/vect/vect-live-5.c: New test. >> *

[PATCH] Selftest framework (v7)

On Fri, 2016-06-03 at 01:21 +0200, Bernd Schmidt wrote: > On 06/02/2016 11:06 PM, David Malcolm wrote: > > gcc/ChangeLog: > > * Makefile.in (OBJS): Add function-tests.o, > > hash-map-tests.o, hash-set-tests.o, rtl-tests.o, > > selftest-run-tests.o. > > (OBJS-libcommon): Add

Re: [PATCH, rs6000] Fix ICE for vec_ld and vec_st of array when compiled with g++

You’re right, I don’t need the -O0. I’d like to leave the dg-skip-if in place because I’m worried about older processors not defining altivec, etc. Thanks! Bill > On Jun 3, 2016, at 1:17 PM, Segher Boessenkool > wrote: > > On Fri, Jun 03, 2016 at 11:41:26AM

Re: [PATCH, rs6000] Fix ICE for vec_ld and vec_st of array when compiled with g++

On Fri, Jun 03, 2016 at 11:41:26AM -0500, Bill Schmidt wrote: > When changing vec_ld and vec_st to be expanded during parsing, I > missed a subtle case that happens only for C++. If the base address > argument has an array type, this doesn’t get converted to a pointer. > For our purposes, we need

Re: [PATCH][2/3] Vectorize inductions that are live after the loop

On Thu, Jun 02, 2016 at 05:11:15PM +0100, Alan Hayward wrote: > * gcc.dg/vect/vect-live-1.c: New test. > * gcc.dg/vect/vect-live-2.c: New test. > * gcc.dg/vect/vect-live-5.c: New test. > * gcc.dg/vect/vect-live-slp-1.c: New test. > * gcc.dg/vect/vect-live-slp-2.c: New

[PATCH] Fix SLP wrong-code with VECTOR_BOOLEAN_TYPE_P (PR tree-optimization/71259)

On Tue, Jan 12, 2016 at 05:21:37PM +0300, Ilya Enkovich wrote: > > --- gcc/tree-vect-slp.c.jj 2016-01-08 21:45:57.0 +0100 > > +++ gcc/tree-vect-slp.c 2016-01-11 12:07:19.633366712 +0100 > > @@ -2999,12 +2999,9 @@ vect_get_constant_vectors (tree op, slp_ > > gimple

[C++ PATCH] Avoid exponential compile time in cp_fold_function (PR c++/70847, PR c++/71330, PR c++/71393)

Hi! As mentioned in these PRs, if there are many nested SAVE_EXPRs or TARGET_EXPRs and many of those appear two or more times in the tree, cp_fold_function has huge compile time requirements. Even when each cp_fold should use a cache and once something has been folded, will return the same tree

Fix predictor hitrate reporting

Hi, the hack to report predictor hitrates by re-running branch prediction has a quirk because the loop niter code feeds the "loop iterations guessed" predictor by the feedback data, so it is incorrectly reported as predicting many loops. This patch avoids that by using the data only when profile

Re: [Patch, avr] Fix PR 71151

Senthil Kumar Selvaraj schrieb: Hi, This patch fixes PR 71151 by eliminating the TARGET_ASM_FUNCTION_RODATA_SECTION hook and setting JUMP_TABLES_IN_TEXT_SECTION to 1. As described in the bugzilla entry, this hook assumed it will get called only for jumptable rodata for functions.

[PATCH, rs6000] Fix ICE for vec_ld and vec_st of array when compiled with g++

Hi, When changing vec_ld and vec_st to be expanded during parsing, I missed a subtle case that happens only for C++. If the base address argument has an array type, this doesn’t get converted to a pointer. For our purposes, we need the pointer, and it’s safe to make that conversion, so this

Re: [PATCH] integer overflow checking builtins in constant expressions

On 06/03/2016 09:23 AM, Jakub Jelinek wrote: On Fri, Jun 03, 2016 at 09:07:09AM -0600, Martin Sebor wrote: I'm not sure I understand your concern but at this point I would prefer to keep things as they are. I like that the functionality My concern is that if you declare that NULL is valid

[PATCH] Fix check_GNU_style.sh for BSD / Mac OS X

check_GNU_style.sh fails to detect lines >80 chars on BSD / Mac OS X systems. This is becuase paste is being called with an empty delimiter list. Instead \0 should be used. Tested on Ubuntu 14.04 and OS X 10.9.5 contrib/ * check_GNU_style.sh: Fix paste args for BSD Alan diff --git

Re: [PATCH] integer overflow checking builtins in constant expressions

On Fri, Jun 03, 2016 at 09:29:48AM -0600, Martin Sebor wrote: > >>+ { > >>+ tree type = TREE_TYPE (TREE_TYPE (t)); > >>+ tree vflow = arith_overflowed_p (opcode, type, arg0, arg1) > >>+ ? integer_one_node : integer_zero_node; > > > >This looks incorrect, the return type

Re: [PATCH v2] gcov: Runtime configurable destination output

"H.J. Lu" writes: > On Mon, May 23, 2016 at 11:16 AM, Aaron Conole wrote: >> Nathan Sidwell writes: >> >>> On 05/19/16 14:40, Aaron Conole wrote: Nathan Sidwell writes: >>> >> +FILE *__gcov_error_file = NULL;

Re: [PATCH] integer overflow checking builtins in constant expressions

+ { + tree type = TREE_TYPE (TREE_TYPE (t)); + tree vflow = arith_overflowed_p (opcode, type, arg0, arg1) + ? integer_one_node : integer_zero_node; This looks incorrect, the return type is TREE_TYPE (t), some complex integer type, therefore vflow needs

C PATCH to improve location for abstract declarators (PR c/71362)

This fixes an imprecise location info with abstract declarators. The problem was that when we build_id_declarator, the default location was input_location and we never attempted to use a more precise location. This patch does it. Bootstrapped/regtested on x86_64-linux, ok for trunk? 2016-06-03

Re: [PATCH] integer overflow checking builtins in constant expressions

On Fri, Jun 03, 2016 at 09:07:09AM -0600, Martin Sebor wrote: > I'm not sure I understand your concern but at this point I would > prefer to keep things as they are. I like that the functionality My concern is that if you declare that NULL is valid third argument for e.g. __builtin_add_overflow,

Re: [PATCH] integer overflow checking builtins in constant expressions

On 06/02/2016 01:34 AM, Jakub Jelinek wrote: On Thu, Jun 02, 2016 at 09:23:16AM +0200, Jakub Jelinek wrote: Also, perhaps just a documentation thing, it would be good to clarify the NULL last argument. From the POV of generating efficient code, I think we should say something that the last

Re: [PATCH v2] gcov: Runtime configurable destination output

On Mon, May 23, 2016 at 11:16 AM, Aaron Conole wrote: > Nathan Sidwell writes: > >> On 05/19/16 14:40, Aaron Conole wrote: >>> Nathan Sidwell writes: >> > +FILE *__gcov_error_file = NULL; Unless I'm missing something, isn't this

Re: [PING] [PR other/70945] Handle function_glibc_finite_math in offloading

On Fri, Jun 03, 2016 at 04:44:15PM +0200, Thomas Schwinge wrote: > Hi! > > Ping. I think it would be better to just add this support to newlib. Or are they opposed to that for whatever reason? Jakub

[PING] [PR other/70945] Handle function_glibc_finite_math in offloading

Hi! Ping. On Sat, 21 May 2016 17:59:17 +0200, I wrote: > As discussed in "Offloading: compatibility > of target and offloading toolchains", there are situations where we have > to do more work to ensure compatibility between target and offloading > toolchains. > >

[Patch, avr] Fix PR 71151

Hi, This patch fixes PR 71151 by eliminating the TARGET_ASM_FUNCTION_RODATA_SECTION hook and setting JUMP_TABLES_IN_TEXT_SECTION to 1. As described in the bugzilla entry, this hook assumed it will get called only for jumptable rodata for functions. This was true until 6.1, when a

Fix continue prediction for C++

Hi, as noticed by Richard, genericize_continue_stmt doesn't really add the prediction statement becuase it has no side effects, so we don't do any continue prediction for C++. Bootstrapped/regtested x86_64-linux, comitted. Honza * g++.dg/tree-ssa/pred-1.C: New testcase *

[PATCH] Backport PowerPC complex __float128 compiler support to GCC 6.x

These patches were installed on the trunk on May 2nd, with a fix from Alan Modra on May 11th. Unless I here objections in the next few days, I will commit these changes to the GCC 6.x branch. These changes will allow people to use complex __float128 types (via an attribute) on the PowerPC.

[PATCH][AArch64] Cleanup -mpc-relative-loads

This patch cleans up the -mpc-relative-loads option processing. Rename to avoid the "no*" name and confusing !no* expressions. Fix the option processing code to implement -mno-pc-relative-loads rather than ignore it. OK for commit? ChangeLog: 2016-06-03 Wilco Dijkstra

[PATCH] rs6000: Remove the ancient mfcr peepholes

These peepholes replace two mfcr;mask sequences by one mfcr;mask;mask sequence. On modern cpus, the original mfcr's were actually mfocrf, but the new insn is an actual heavy-weight mfcr. This is very bad for performance. The comment says there is a three cycle delay between two consecutive mfcr

Re: [PATCH] Do not instrument string cst w/ unknown decl size (PR, sanitizer/71378)

On 06/03/2016 01:00 PM, Jakub Jelinek wrote: > I think the STRING_CST with non-constant size is already a bug, so this > patch looks to me just like a workaround for a bug that is somewhere else. Ah, thanks for clarification, it looked weird to me. I've just reclassified the PR, btw. clang++

[PATCH] Print column numbers in inclusion trace consistently.

Hi, the patch below fixes PR/42014. Although the fix itself seems easy enough, I have a problem with the test. Is there a way to match the output before the "warning:" line? dg-{begin,end}-multiline-output doesn't do the job, or at least I don't know how to convince it. Bootstrapped on x86_64

Re: Remove duplicated GOMP SIMD LANE code

On Thu, Jun 2, 2016 at 6:03 PM, Alan Hayward wrote: > The IFN_GOMP_SIMD_LANE code in vectorizable_call is essentially a > duplicate of > the code in vectorizable_live_operation. They both replace all uses > outside the > loop with the constant VF - 1. > > Note that my patch

Re: [PATCH][3/3] No need to vectorize simple only-live stmts

On Thu, Jun 2, 2016 at 6:14 PM, Alan Hayward wrote: > >>Statements which are live but not relevant need marking to ensure they are >>vectorized. >> >>Live statements which are simple and all uses of them are invariant do not >>need >>to be vectorized. >> >>This patch adds a

Re: [PATCH][2/3] Vectorize inductions that are live after the loop

On Thu, Jun 2, 2016 at 6:11 PM, Alan Hayward wrote: > > > On 01/06/2016 10:51, "Richard Biener" wrote: > >>On Wed, Jun 1, 2016 at 10:46 AM, Alan Hayward >>wrote: >>> >>> >>> On 30/05/2016 14:22, "Richard Biener"

Re: [PATCH] Do not instrument string cst w/ unknown decl size (PR, sanitizer/71378)

On Fri, Jun 03, 2016 at 12:53:06PM +0200, Martin Liška wrote: > As seen in the issue, we try to instrument a global variable that contains a > string > constant. Following patch does not instrument in the size is variable (VLA). > > Patch survives regression tests and bootstraps on x86_64-linux.

Re: [PATCH][1/3] Add loop_vinfo to vect_get_vec_def_for_operand

On Thu, Jun 2, 2016 at 6:04 PM, Alan Hayward wrote: > >> This patch simply adds loop_vinfo as an extra argument to >> vect_get_vec_def_for_operand and only generates a stmt_vinfo if required. >> This is a required cleanup for patch [2/3]. >> Tested on x86 and aarch64. >> >>

[PATCH] Do not instrument string cst w/ unknown decl size (PR, sanitizer/71378)

Hi! As seen in the issue, we try to instrument a global variable that contains a string constant. Following patch does not instrument in the size is variable (VLA). Patch survives regression tests and bootstraps on x86_64-linux. It's questionable whether the same situation can also happen in

[PATCH][AArch64] Increase code alignment

Increase loop alignment on Cortex cores to 8 and set function alignment to 16. This makes things consistent across big.LITTLE cores, improves performance of benchmarks with tight loops and reduces performance variations due to small changes in code layout. It looks almost all AArch64 cores

Re: [RFC: Patch 1/6] New target hook: rtx_branch_cost

On Thu, Jun 2, 2016 at 6:53 PM, James Greenhalgh wrote: > > Hi, > > This patch introduces a new target hook, to be used like BRANCH_COST but > with a guaranteed unit of measurement. We want this to break away from > the current ambiguous uses of BRANCH_COST. > >

Re: [PATCH, rs6000] Fix PR70957 (skip vsx-elemrev-[24].c tests for a downlevel assembler)

On Thu, Jun 02, 2016 at 03:50:21PM -0500, Bill Schmidt wrote: > The only way I know to make the test predictable is to use a run-time test to > check whether > P9 vector instructions will execute. Thus this solution. I’ve verified we > no longer have test > failures on machines with a

Re: [PATCH] Warn about return with a void expression with -Wreturn-type.

2016-06-03 11:36 GMT+02:00 Bernd Schmidt : > On 06/02/2016 12:03 PM, Marcin Baczyński wrote: >> >> 2016-06-02 4:51 GMT+02:00 Martin Sebor : >>> >>> As a disclaimer, someone else endowed with those special powers >>> will need to approve your final patch. If

Re: [PATCH] Warn about return with a void expression with -Wreturn-type.

On 06/02/2016 12:03 PM, Marcin Baczyński wrote: 2016-06-02 4:51 GMT+02:00 Martin Sebor : As a disclaimer, someone else endowed with those special powers will need to approve your final patch. If you don't get a timely approval please ping the patch weekly. *

Re: [RFC: Patch 0/6] Rewrite the noce-ifcvt cost models

On 06/02/2016 06:53 PM, James Greenhalgh wrote: As I iterated through versions of this patch set, I realised that all we really wanted for ifcvt was a way to estimate the cost of a branch in units that were comparable to the cost of instructions. The trouble with BRANCH_COST wasn't that it was

Re: [AArch64 1/2] Refactor aarch64_operands_ok_for_ldpstp, aarch64_operands_adjust_ok_for_ldpstp

On 17/05/16 10:22, James Greenhalgh wrote: Hi, These two functions are very similar and suffer from code duplication. With a little bit of work we can reduce the strain on the reader by refactoring the functions. Essentially, we're going to remove the explicit references to reg_1, reg_2,

Re: [PATCH][combine] PR middle-end/71074 Check that const_op is >= 0 before potentially shifting in simplify_comparison

On 06/03/2016 10:35 AM, Kyrill Tkachov wrote: Here is the patch with the changes discussed. Bootstrapped and tested on arm-none-linux-gnueabihf, aarch64-none-linux-gnu and x86_64-linux. Is this ok? I think so, but since this is one of those situations where I'm essentially approving my own

[Patch AArch64] Refactor and clean up some of the sched_fusion handling

Hi, I had a little trouble understanding the sched_fusion code, so I refactored it and added some comments. I think this is a bit easier to read, but I'm equally happy dropping the patch. Bootstrapped on aarch64-none-linux-gnu. OK? Thanks, James --- 2016-06-03 James Greenhalgh

Re: [Patch AArch64 2/2] Some more cleanup of ldp/stp generation

*ping* https://gcc.gnu.org/ml/gcc-patches/2016-05/msg01192.html Thanks, James On Tue, May 17, 2016 at 10:22:31AM +0100, James Greenhalgh wrote: > > This is another refactoring patch to clean up more of the ldp/stp handling > code and avoid duplicating quite as much code. > > Much like the

Re: [AArch64 1/2] Refactor aarch64_operands_ok_for_ldpstp, aarch64_operands_adjust_ok_for_ldpstp

*ping* https://gcc.gnu.org/ml/gcc-patches/2016-05/msg01193.html Thanks, James On Tue, May 17, 2016 at 10:22:30AM +0100, James Greenhalgh wrote: > > Hi, > > These two functions are very similar and suffer from code duplication. > With a little bit of work we can reduce the strain on the reader

[C++ Patch] PR 70202 ("ICE on invalid code in build_simple_base_path, at cp/class.c:579")

Hi, in this error recovery issue, after a sensible error message about duplicate base type and a redundant one about an incomplete type (the type with the erroneous base type) we finally crash much later in build_simple_base_path. Yesterday I noticed that elsewhere we don't check the return

[PATCH][ARM][obvious] Fix typos in *thumb1_mulsi3 comment

Hi all, This patch just fixes a couple of typos (s/can fails/can fail/, s/with the Thumb/on Thumb/) and makes the commenting style consistent on this pattern in thumb1.md Tested on arm-none-eabi. Committing as obvious. Thanks, Kyrill 2016-06-03 Kyrylo Tkachov

[Committed] Adding myself to MAINTAINERS

Index: MAINTAINERS === --- MAINTAINERS (revision 237053) +++ MAINTAINERS (working copy) @@ -493,6 +493,7 @@ Ziga Mahkovec David Malcolm

[AArch64] Give some new costs for Cortex-A57 floating-point operations

Hi, This patch rebases the floating-point cost table for Cortex-A57 to be relative to the cost of a floating-point move. This in response to this feedback from Richard Sandiford [2] on Ramana's patch to calls.c [1] from 2014: I think this is really a bug in the backend. The backend is

Re: [PATCH][combine] PR middle-end/71074 Check that const_op is >= 0 before potentially shifting in simplify_comparison

On 13/05/16 14:26, Bernd Schmidt wrote: On 05/13/2016 03:22 PM, Kyrill Tkachov wrote: /* We only want to handle integral modes. This catches VOIDmode, CCmode, and the floating-point modes. An exception is that we @@ -11649,7 +11649,8 @@ simplify_comparison (enum rtx_code code,

[PATCH][ARM] Fix gcc.target/arm/builtin-bswap16-1.c

Hi all, The test gcc.target/arm/builtin-bswap16-1.c refuses to compile when testing a toolchain configured with --with-mode=thumb --with-float=hard and an architecture that supports Thumb2. This is because the test explicitly sets the -march option to armv6 and we get an error complaining

[PATCH][wwwdocs][obvious] Fix typo in -finline-matmul-limit

Committed as obvious. Thanks, Kyrill Index: htdocs/gcc-6/changes.html === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v retrieving revision 1.82 diff -U 3 -r1.82 changes.html --- htdocs/gcc-6/changes.html 31 May 2016

Re: [PATCH v1] Support for SPARC M7 and VIS 4.0

> This patch adds support for -mcpu=niagara7, corresponding to the SPARC > M7 CPU as documented in the Oracle SPARC Architecture 2015 and the M7 > Processor Supplement. The patch also includes intrinsics support for > all the VIS 4.0 instructions. > > This patch has been tested in

Re: move increase_alignment from simple to regular ipa pass

> > fsection-anchors > > > > Common Report Var(flag_section_anchors) > > > > Access data in the same section from shared anchor points. > > > > Funny. I see the

Re: move increase_alignment from simple to regular ipa pass

On Thu, 2 Jun 2016, Jan Hubicka wrote: > > On Thu, 2 Jun 2016, David Edelsohn wrote: > > > > > > Richard Biener wrote: > > > > > > >> "This would mean the pass should get its own non-Optimization flag > > > >> initialized by targets where section anchors are usually used" > > > >> IIUC

Re: [PATCH] Fix cgraph edge redirection with non-POD lhs (PR middle-end/71387)

On Thu, 2 Jun 2016, Jakub Jelinek wrote: > Hi! > > Apparently my r236430 change (trunk) and r236431 (6.x) broke the following > testcase. In the later similar change to gimple-fold.c in r236506 > I've added code to tweak gimple_call_fntype if we have newly one of the > void something (void)

Re: [PATCH, OpenACC] Make reduction arguments addressable

On Fri, Jun 03, 2016 at 03:13:40PM +0800, Chung-Lin Tang wrote: > On 2016/6/2 10:00 PM, Jakub Jelinek wrote: > > Wouldn't it be better to pass either a bool openacc_async flag, or > > whole clauses, down to gfc_trans_omp_reduction_list and handle it there > > instead of walking the list after the

Re: [PATCH, OpenACC] Make reduction arguments addressable

On 2016/6/2 10:00 PM, Jakub Jelinek wrote: > Wouldn't it be better to pass either a bool openacc_async flag, or > whole clauses, down to gfc_trans_omp_reduction_list and handle it there > instead of walking the list after the fact? You mean this style? (patch attached) Tested again with no

Re: [PR tree-optimization/71328] Fix off-by-one error in CFG/SSA updates for backward threading

On Thu, Jun 02, 2016 at 11:24:49PM -0600, Jeff Law wrote: > commit 96a568909e429b0f24d61c8a2f3dd3c183d720d7 > Author: law > Date: Fri Jun 3 05:20:16 2016 + > > PR tree-optimization/71328 > * tree-ssa-threadupdate.c

Re: [PATCH] integer overflow checking builtins in constant expressions

Hi! On Thu, Jun 02, 2016 at 06:28:21PM -0600, Martin Sebor wrote: First of all, can you please respond to the mail I've sent about NULL argument issues (and proposal for __builtin_*_overflow_p)? This patch as well as the nonnull attribute patch then depends on that decision... > + { > +