Re: Dominance related breakage, was Re: [PATCH] PR71275 ira.c bb_loop_depth

On 05/26/2016 10:14 PM, Alan Modra wrote: On Thu, May 26, 2016 at 10:12:14AM -0400, Vladimir Makarov wrote: On 05/26/2016 07:02 AM, Alan Modra wrote: This fixes lack of bb_loop_depth info in some of the early parts of ira, which has been the case for quite some time. All active branches

Re: [PATCH], PR 71294, Fix -O3 -fstack-protector bug on PowerPC power8

On Thu, May 26, 2016 at 09:50:18PM -0400, Michael Meissner wrote: > It might be argued that this is a reload bug (since it runs on LRA), but > sometimes it is simpler to place a simpler work around in the machine > dependent > code. If the maintainers decide that it should be fixed in reload

Dominance related breakage, was Re: [PATCH] PR71275 ira.c bb_loop_depth

On Thu, May 26, 2016 at 10:12:14AM -0400, Vladimir Makarov wrote: > On 05/26/2016 07:02 AM, Alan Modra wrote: > >This fixes lack of bb_loop_depth info in some of the early parts of > >ira, which has been the case for quite some time. All active branches > >return 0 from bb_loop_depth() in

[PATCH], PR 71294, Fix -O3 -fstack-protector bug on PowerPC power8

It might be argued that this is a reload bug (since it runs on LRA), but sometimes it is simpler to place a simpler work around in the machine dependent code. If the maintainers decide that it should be fixed in reload instead of via this patch, that is fine. PR 71294 involves vectorization

Re: [Patch] Disable text mode translation in ada for Cygwin

On 5/26/2016 21:55, Arnaud Charlet wrote: >> Text mode translation should not be done for Cygwin, especially since it >> does not >> support unicode setmode calls. This also fixes ada builds for Cygwin. >> >> OK for trunk? > > OK, thanks. > Can someone please commit this? I don't have SVN write

Re: [PATCH], Add PowerPC ISA 3.0 min/max support

On Thu, May 26, 2016 at 03:59:43PM -0500, Segher Boessenkool wrote: > On Thu, May 26, 2016 at 01:04:59PM -0400, Michael Meissner wrote: > > * config/rs6000/rs6000.md (SFDF2): New iterator to allow doing > > conditional moves there the comparison type is different from move > > type. >

Re: Add option for whether ceil etc. can raise "inexact", adjust x86 conditions

On Thu, 26 May 2016, Jan Hubicka wrote: > > > +ffp-int-builtin-inexact > > > +Common Report Var(flag_fp_int_builtin_inexact) Optimization > > > +Allow built-in functions ceil, floor, round, trunc to raise \"inexact\" > > > exceptions. > > When adding new codegen option which affects the

Re: [PATCH], Add PowerPC ISA 3.0 min/max support

On Thu, May 26, 2016 at 01:04:59PM -0400, Michael Meissner wrote: > * config/rs6000/rs6000.md (SFDF2): New iterator to allow doing > conditional moves there the comparison type is different from move > type. s/there/where/ ? > Don't forget to delete this line ;-) > +/*

Re: [PATCH] Improve *vec_concatv2si_sse4_1

On Thu, May 26, 2016 at 07:39:01PM +0200, Uros Bizjak wrote: > On Thu, May 26, 2016 at 7:05 PM, Jakub Jelinek wrote: > > Hi! > > > > This patch adds an avx512dq alternative (EVEX vpinsrd requires that) and > > enables EVEX vmovd and vpunpckldq. > > > > Bootstrapped/regtested on

[committed] Warn about OpenMP schedule clause chunk size when proven not positive

Hi! While porting doacross-1.c testcase to Fortran, I've discovered that I've used there schedule(static, 0), which is invalid (I've meant schedule(static) instead). This patch adds warning for this for all FEs. Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.

Further refinement to -Wswitch-unreachable

Martin complained that -Wswitch-unreachable wouldn't warn on try-blocks, either compiler-generated or user-written. This patch, which looks into GIMPLE_TRY's body, seems to DTRT for both. Bootstrapped/regtested on x86_64-linux, ok for trunk? 2016-05-26 Marek Polacek

Re: Add option for whether ceil etc. can raise "inexact", adjust x86 conditions

> > +ffp-int-builtin-inexact > > +Common Report Var(flag_fp_int_builtin_inexact) Optimization > > +Allow built-in functions ceil, floor, round, trunc to raise \"inexact\" > > exceptions. When adding new codegen option which affects the correctness, it is also necessary to update

Re: tuple move constructor

On 26/05/16 19:49 +0200, Marc Glisse wrote: On Thu, 26 May 2016, Jonathan Wakely wrote: On 25/05/16 14:54 +0100, Jonathan Wakely wrote: On 23/05/16 20:39 +0200, Marc Glisse wrote: Ping (re-attaching, I just added a one-line comment before the tag class as asked by Ville) This is OK for

Re: tuple move constructor

On Thu, 26 May 2016, Jonathan Wakely wrote: On 25/05/16 14:54 +0100, Jonathan Wakely wrote: On 23/05/16 20:39 +0200, Marc Glisse wrote: Ping (re-attaching, I just added a one-line comment before the tag class as asked by Ville) This is OK for trunk - thanks. On second thoughts - does

Re: [PATCH] Improve *vec_concatv2si_sse4_1

On Thu, May 26, 2016 at 7:05 PM, Jakub Jelinek wrote: > Hi! > > This patch adds an avx512dq alternative (EVEX vpinsrd requires that) and > enables EVEX vmovd and vpunpckldq. > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? > > 2016-05-26 Jakub Jelinek

[PATCH, i386]: Use if_then_else or cond RTXes to calculate attribute value

Hello! Some of these strings went out of control. Use if_then_else or cond RTXes to make things readable and maintainable again. No functional changes. 2016-05-26 Uros Bizjak * config/i386/i386.md (*movqi_internal) : Use if_then_else or cond RTXes to calculate

Re: C PATCH for comptypes handling of TYPE_REF_CAN_ALIAS_ALL

On Thu, 26 May 2016, Marek Polacek wrote: > The C++ FE has been changed, as a part of c++/50800, in such a way that it no > longer considers types differentiating only in TYPE_REF_CAN_ALIAS_ALL > incompatible. But the C FE still rejects the following testcase, so this > patch > makes the C FE

Re: [PTX] more tests annotations

Hello, On Thu, 26 May 2016, Nathan Sidwell wrote: > Applied the attached to markup some more tests that PTX either crashes on or > doesn't apply strict IEEE semantics to. In one case it's about debug info > that we don't emit. > Index: gcc.dg/torture/c99-contract-1.c >

Re: [PATCH 1/3] Encapsulate comp_cost within a class with methods.

On 05/19/2016 01:24 PM, Bin.Cheng wrote: > On Thu, May 19, 2016 at 11:23 AM, Martin Liška wrote: >> On 05/16/2016 03:55 PM, Martin Liška wrote: >>> On 05/16/2016 12:13 PM, Bin.Cheng wrote: Hi Martin, Could you please rebase this patch and the profiling one against

Re: [PTX] malloc/realloc/free

Hello, On Thu, 26 May 2016, Nathan Sidwell wrote: > This patch removes the malloc/realloc/free wrappers from libgcc. I've > implemented them completely in C and put them in the ptx newlib port -- > where one expects such functions. It appears that the new Newlib code doesn't free 'p' on

[PATCH v4] gcov: Runtime configurable destination output

The previous gcov behavior was to always output errors on the stderr channel. This is fine for most uses, but some programs will require stderr to be untouched by libgcov for certain tests. This change allows configuring the gcov output via an environment variable which will be used to open the

Re: [PATCH][1/3][ARM] Keep ctz expressions together until after reload

On Thu, 26 May 2016, Kyrill Tkachov wrote: > the early RTL optimisers. This better expresses the semantics of the > operation as a whole, since the RBIT operation is represented as an > UNSPEC anyway and so will not see the benefits of combine, This doesn't affect your patch, but I think it

[PATCH] Improve *vec_concatv4si

Hi! Both vpunpcklqdq and vmovhps are available with XMM EVEX args in AVX512VL. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2016-05-26 Jakub Jelinek * config/i386/sse.md (*vec_concatv4si): Use v=v,v instead of x=x,x and v=v,m instead

[PATCH] Improve *vec_concatv2si_sse4_1

Hi! This patch adds an avx512dq alternative (EVEX vpinsrd requires that) and enables EVEX vmovd and vpunpckldq. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2016-05-26 Jakub Jelinek * config/i386/sse.md (*vec_concatv2si_sse4_1): Add avx512dq

Re: [PATCH], Add PowerPC ISA 3.0 min/max support

On Mon, May 09, 2016 at 09:31:43AM -0500, Segher Boessenkool wrote: > On Thu, May 05, 2016 at 03:18:39PM -0400, Michael Meissner wrote: > > At the present time, the code does not support comparisons involving >= and > > <= > > unless the -ffast-math option is used. I hope eventually to support >

Re: RFA: Generate normal DWARF DW_LOC descriptors for non integer mode pointers

Hi Jeff, >>> I may be missing something, but isn't it the transition to an FP >>> relative address rather than a SP relative address that's the problem >>> here? >> >> Yes, I believe so. >> >>> Where does that happen? I think that it happens in dwarf2out.c:based_loc_descr() which detects the

Re: tuple move constructor

On 25/05/16 14:54 +0100, Jonathan Wakely wrote: On 23/05/16 20:39 +0200, Marc Glisse wrote: Ping (re-attaching, I just added a one-line comment before the tag class as asked by Ville) This is OK for trunk - thanks. On second thoughts - does this change the passing conventions for

Re: Add option for whether ceil etc. can raise "inexact", adjust x86 conditions

On Thu, May 26, 2016 at 1:46 AM, Joseph Myers wrote: > In ISO C99/C11, the ceil, floor, round and trunc functions may or may > not raise the "inexact" exception for noninteger arguments. Under TS > 18661-1:2014, the C bindings for IEEE 754-2008, these functions are >

Re: Fix ivopts estimates for internal functions

On May 26, 2016 4:39:02 PM GMT+02:00, Richard Sandiford wrote: >tree-ssa-loop-ivopts.c:loop_body_includes_call was treating internal >calls such as IFN_SQRT as clobbering all caller-saved registers, which >I don't think is appropriate for any current internal function.

Re: [v3 PATCH] PR libstdc++/66338

On 26/05/16 01:07 +0300, Ville Voutilainen wrote: On 25 May 2016 at 16:55, Jonathan Wakely wrote: On 24/05/16 19:49 +0300, Ville Voutilainen wrote: On 24 May 2016 at 19:35, Ville Voutilainen wrote: Slight tweak. The avoidance of

Re: [patch] libstdc++/69703 ignore endianness in codecvt_utf8

On 26/05/16 14:02 +0200, Christophe Lyon wrote: I've seen you've backported the main patch to the gcc-6 branch, you forgot to add the follow-up "Add dg-require-filesystem-ts directive to test". And likewise for the gcc-5 branch. Both fixed now, sorry about that, again.

[PING] Re: Updated autofdo bootstrap and testing patches

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 last patch is more a > workaround > (to make autofdo bootstrap not ICE), but may need a better fix. > > The main

[PTX] more tests annotations

Applied the attached to markup some more tests that PTX either crashes on or doesn't apply strict IEEE semantics to. In one case it's about debug info that we don't emit. nathan 2016-05-26 Nathan Sidwell * gcc.dg/20060410.c: Xfail on ptx. *

[PATCH 1/3] config-list.mk: add KNOWN_BROKEN

When using config-list.mk to build all configurations, it's useful to filter out the configurations that are known to be broken. This patch does so, adding a KNOWN_BROKEN variable. contrib/ChangeLog: * config-list.mk (LIST): Rename to... (FULL_LIST): ...this.

Re: [PTX] crt0

On 05/26/16 10:36, Nathan Sidwell wrote: Ib. PTX appears to accept '.extern .weak ...', but that has the same semantics as '.extern ...', which IMHO is a bug. '.extern .weak' doesn't mean anything special. Working on a GCC patch to stop us emitting it. Pah, I'd misremembered what we

[PATCH 3/3] config-list.mk: add OPT-enable-obsolete to 4 targets

r233165 marked three deprecated rtems targets as obsolete. r233887 marked mep-elf as obsolete. Update config-list.mk to add OPT-enable-obsolete to these 4 targets. contrib/ChangeLog: * config-list.mk (FULL_LIST): Add OPT-enable-obsolete to avr-rtems, h8300-rtems, m32r-rtems,

[PATCH 2/3] config-list.mk: add GCC_SRC_DIR

config-list.mk currently requires the pwd to be in a sibling directory of the source tree. However, building using config-list.mk can consume over 400GB of disk space in this build directory (e.g. my machine successfully built cc1 for 206 configurations last night, consuming 442GB of space).

Fix ivopts estimates for internal functions

tree-ssa-loop-ivopts.c:loop_body_includes_call was treating internal calls such as IFN_SQRT as clobbering all caller-saved registers, which I don't think is appropriate for any current internal function. Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install? Thanks, Richard gcc/

Re: [PTX] crt0

On 05/25/16 11:49, Alexander Monakov wrote: On Wed, 25 May 2016, Nathan Sidwell wrote: With today's trunk and newlib, if I run unresolved symbol __exitval_ptr Is should work now, just pushed a patch to newlib. PTX appears to accept '.extern .weak ...', but that has the same semantics as

Remove word_mode hack for split bitfields

This patch is effectively reverting a change from 1994. The reason I think it's a hack is that store_bit_field_1 is creating a subreg reference to one word of a field even though it has already proven that the field spills into the following word. We then rely on the special SUBREG handling in

[PTX] malloc/realloc/free

This patch removes the malloc/realloc/free wrappers from libgcc. I've implemented them completely in C and put them in the ptx newlib port -- where one expects such functions. applied to trunk. nathan 2016-05-26 Nathan Sidwell * config/nvptx/free.asm: Delete. *

C PATCH for comptypes handling of TYPE_REF_CAN_ALIAS_ALL

The C++ FE has been changed, as a part of c++/50800, in such a way that it no longer considers types differentiating only in TYPE_REF_CAN_ALIAS_ALL incompatible. But the C FE still rejects the following testcase, so this patch makes the C FE follow suit. After all, the may_alias attribute is not

Re: [PATCH] PR71275 ira.c bb_loop_depth

On 05/26/2016 07:02 AM, Alan Modra wrote: This fixes lack of bb_loop_depth info in some of the early parts of ira, which has been the case for quite some time. All active branches return 0 from bb_loop_depth() in update_equiv_regs, but whether that actually causes mis-optimization anywhere but

Re: [AArch64][2/4] PR63596, honor tree-stdarg analysis result to improve VAARG codegen

On Fri, May 06, 2016 at 04:00:28PM +0100, Jiong Wang wrote: > This patch fixes PR63596. > > There is no need to push/pop all arguments registers. We only need to > push and pop those registers used. These use info is calculated by a > dedicated vaarg optimization tree pass "tree-stdarg", the

Re: Fix for PR70909 in Libiberty Demangler (4)

It seems like in cases of malformed input we should return the input again rather than produce garbage like "K". Maybe catch this sort of situation in d_lookup_template_parameter? Jason On Mon, May 2, 2016 at 11:21 AM, Marcel Böhme wrote: > Hi, > > This fixes several

Re: [Patch] Disable text mode translation in ada for Cygwin

> Text mode translation should not be done for Cygwin, especially since it > does not > support unicode setmode calls. This also fixes ada builds for Cygwin. > > OK for trunk? OK, thanks. > gcc/ada/ChangeLog: > * sysdep.c (__gnat_set_binary_mode, __gnat_set_text_mode, >

Re: C PATCH to add -Wswitch-unreachable (PR c/49859)

On Thu, May 26, 2016 at 3:06 AM, Marek Polacek wrote: > On Wed, May 25, 2016 at 03:21:00PM -0600, Martin Sebor wrote: >> I see. Thanks for clarifying that. No warning on a declaration >> alone makes sense in the case above but it has the unfortunate >> effect of suppressing

[PATCH, libstdc++/testsuite] 29_atomics/atomic/65913.cc: require atomic-builtins rather than specific target

[Sorry for the large recipient list, I wasn't sure who of C++ and x86 maintainers should approve this] Hi, 29_atomics/atomic/65913.cc test in libstdc++ is a runtime test that only rely on atomic and gnu++11 support. Therefore I propose to require atomic-builtins instead of an x86 (32 or 64

Re: [PATCH] Help PR70729, shuffle LIM and PRE

On 18 May 2016 at 12:55, Richard Biener wrote: > > The following patch moves LIM before PRE to allow it to cleanup CSE > (and copyprop) opportunities LIM exposes. It also moves the DCE done > in loop before the loop pipeline as otherwise it is no longer executed >

[Patch] Disable text mode translation in ada for Cygwin

Text mode translation should not be done for Cygwin, especially since it does not support unicode setmode calls. This also fixes ada builds for Cygwin. OK for trunk? gcc/ada/ChangeLog: * sysdep.c (__gnat_set_binary_mode, __gnat_set_text_mode, __gnat_set_mode): Disable text mode

Re: [patch] libstdc++/69703 ignore endianness in codecvt_utf8

On 26 May 2016 at 13:58, Christophe Lyon wrote: > On 5 May 2016 at 12:12, Jonathan Wakely wrote: >> On 04/05/16 17:19 +0100, Andre Vieira (lists) wrote: >>> >>> On 20/04/16 18:40, Jonathan Wakely wrote: On 19/04/16 19:07 +0100, Jonathan

Re: [patch] libstdc++/69703 ignore endianness in codecvt_utf8

On 5 May 2016 at 12:12, Jonathan Wakely wrote: > On 04/05/16 17:19 +0100, Andre Vieira (lists) wrote: >> >> On 20/04/16 18:40, Jonathan Wakely wrote: >>> >>> On 19/04/16 19:07 +0100, Jonathan Wakely wrote: This was reported as a bug in the Filesystem library, but

Re: [PATCH][AArch64] Adjust SIMD integer preference

James Greenhalgh wrote: > I really don't like [1][2][3] this technique of attempting to work around > register allocator issues using the disparaging mechanisms. I don't see the issue as it is a standard mechanism to describe higher cost to the register allocator. On the other had the use of '*'

Re: [AArch64][1/4] Enable tree-stdarg pass for AArch64 by defining counter fields

On Fri, May 06, 2016 at 04:00:13PM +0100, Jiong Wang wrote: > This patch initialize va_list_gpr_counter_field and > va_list_fpr_counter_field properly for AArch64 backend that tree-stdarg > pass will be enabled. > > The "required register" analysis is largely target independent, but the > user

[PATCH] PR71275 ira.c bb_loop_depth

This fixes lack of bb_loop_depth info in some of the early parts of ira, which has been the case for quite some time. All active branches return 0 from bb_loop_depth() in update_equiv_regs, but whether that actually causes mis-optimization anywhere but trunk is yet to be determined. I played a

Re: [PATCH][AArch64] Adjust SIMD integer preference

On Fri, Apr 22, 2016 at 03:35:42PM +, Wilco Dijkstra wrote: > SIMD operations like combine prefer to have their operands in FP registers, > so increase the cost of integer registers slightly to avoid unnecessary > int<->FP moves. This improves register allocation of scalar SIMD operations. I

Re: [PATCH][AArch64] Tie operand 1 to operand 0 in AESMC pattern when AES/AESMC fusion is enabled

On Fri, May 20, 2016 at 11:04:32AM +0100, Kyrill Tkachov wrote: > Hi all, > > The recent -frename-registers change exposed a deficiency in the way we fuse > AESE/AESMC instruction pairs in aarch64. > > Basically we want to enforce: > AESE Vn, _ > AESMC Vn, Vn > > to enable the fusion,

[PATCH][3/3][RTL ifcvt] PR middle-end/37780: Conditional expression with __builtin_clz() should be optimized out

Hi all, In this PR we want to optimise: int foo (int i) { return (i == 0) ? N : __builtin_clz (i); } on targets where CLZ is defined at zero to the constant 'N'. This is determined at the RTL level through the CLZ_DEFINED_VALUE_AT_ZERO macro. The obvious place to implement this would be in

[PATCH][2/3][AArch64] Keep CTZ components together until after reload

Hi all, In a similar rationale to patch 1/3 this patch changes the AArch64 backend to keep the CTZ expression as a single RTX until after reload when it is split into an RBIT and a CLZ instruction. This enables CTZ-specific optimisations in the pre-reload RTL optimisers. Bootstrapped and

[PATCH][1/3][ARM] Keep ctz expressions together until after reload

Hi all, On arm we don't have a dedicated instruction that corresponds to a CTZ rtx but we synthesise it with an RBIT instruction followed by a CLZ. This is currently done at expand time. However, I'd like to push that step until after reload and keep the CTZ rtx as a single whole in the early

Re: [PATCH/AARCH64/ILP32] Fix unwinding (libgcc)

On Wed, Apr 27, 2016 at 02:13:21PM -0700, Andrew Pinski wrote: > Hi, > AARCH64 ILP32 is like x32 where UNITS_PER_WORD > sizeof(void*) so we > need to define REG_VALUE_IN_UNWIND_CONTEXT for ILP32. This fixes > unwinding through the signal handler. This is independent of the ABI > which Linux

Re: [PR71252][PR71269] Fix trunk errors due to stmt_to_insert

Hi Jakub, On 26 May 2016 at 18:18, Jakub Jelinek wrote: > On Thu, May 26, 2016 at 02:17:56PM +1000, Kugan Vivekanandarajah wrote: >> --- a/gcc/tree-ssa-reassoc.c >> +++ b/gcc/tree-ssa-reassoc.c >> @@ -3767,8 +3767,10 @@ swap_ops_for_binary_stmt (vec ops, >>

[committed] Add PR71280 testcase

Hi! I came up with a simple C testcase for a PR, which apparently Martin fixed yesterday in PR71239. Thus, I've just committed following testcase as obvious and will close the PR. 2016-05-26 Jakub Jelinek PR tree-optimization/71280 * gcc.dg/pr71280.c: New

Re: [PATCH][ARM] PR target/71056: Don't use vectorized builtins when NEON is not available

Hi Ramana, On 19/05/16 14:36, Ramana Radhakrishnan wrote: On 11/05/16 15:32, Kyrill Tkachov wrote: Hi all, In this PR a NEON builtin is introduced during SLP vectorisation even when NEON is not available because arm_builtin_vectorized_function is missing an appropriate check in the BSWAP

Re: [PATCH][AArch64] Improve aarch64_case_values_threshold setting

On Mon, May 16, 2016 at 11:38:04AM +0100, Wilco Dijkstra wrote: > GCC expands switch statements in a very simplistic way and tries to use a > table > expansion even when it is a bad idea for performance or codesize. > GCC typically emits extremely sparse tables that contain mostly default >

Re: [AArch64, 2/4] Extend vector mutiply by element to all supported modes

On Wed, May 18, 2016 at 02:13:53PM +0100, Jiong Wang wrote: > Thanks for reporting this. > > Yes, reproduced. I should force those res* local variable into > memory so they can be in the same order as the expected result > which is kept in memory. > > The following patch fix this. > >

Re: [PATCH, testsuite] Skip tail call tests on Thumb-1 targets

On 26/05/16 09:24, Thomas Preudhomme wrote: On Wednesday 25 May 2016 11:38:44 Mike Stump wrote: On May 25, 2016, at 10:20 AM, Thomas Preudhomme wrote: 2016-05-24 Thomas Preud'homme * gcc.dg/plugin/plugin.exp: skip tail

[AArch64, testsuite] Fix vmul_elem_1.c on big-endian

On 18/05/16 14:13, Jiong Wang wrote: On 18/05/16 09:17, Christophe Lyon wrote: gcc/ 2016-05-17 Jiong Wang * config/aarch64/aarch64-simd.md (*aarch64_mul3_elt_to_128df): Extend to all supported modes. Rename to...

Re: [PATCH] Improve vcvtps2ph

On 23 May 19:21, Jakub Jelinek wrote: > Hi! > > These insns are available in AVX512VL, so we can just use v instead of x. > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? OK. -- Thanks, K

Re: [PATCH] Improve *ssse3_palignr_perm

On 23 May 19:17, Jakub Jelinek wrote: > Hi! > > This pattern is used to improve __builtin_shuffle in some cases; > VPALIGNR is AVX512BW & AVX512VL. > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? OK. -- Thanks, K

Re: [PATCH] Improve *avx_vperm_broadcast_*

Hi Jakub, On 23 May 19:15, Jakub Jelinek wrote: > Hi! > > The vbroadcastss and vpermilps insns are already in AVX512F & AVX512VL, > so can be used with v instead of x, the splitter case where we for AVX > emit vpermilps plus vpermf128 is more problematic, because the latter > insn isn't available

Re: [PATCH, testsuite] Skip tail call tests on Thumb-1 targets

On Wednesday 25 May 2016 11:38:44 Mike Stump wrote: > On May 25, 2016, at 10:20 AM, Thomas Preudhomme wrote: > > 2016-05-24 Thomas Preud'homme > > > >* gcc.dg/plugin/plugin.exp: skip tail call tests for Thumb-1. > > > > Is

Re: [PR71252][PR71269] Fix trunk errors due to stmt_to_insert

On Thu, May 26, 2016 at 02:17:56PM +1000, Kugan Vivekanandarajah wrote: > --- a/gcc/tree-ssa-reassoc.c > +++ b/gcc/tree-ssa-reassoc.c > @@ -3767,8 +3767,10 @@ swap_ops_for_binary_stmt (vec ops, >operand_entry temp = *oe3; >oe3->op = oe1->op; >oe3->rank = oe1->rank; > +

Re: C PATCH to add -Wswitch-unreachable (PR c/49859)

On Wed, May 25, 2016 at 03:21:00PM -0600, Martin Sebor wrote: > I see. Thanks for clarifying that. No warning on a declaration > alone makes sense in the case above but it has the unfortunate > effect of suppressing the warning when the declaration is followed > by a statement, such as in: > >

Re: Fix for PR70909 in Libiberty Demangler (4)

Hi, This patch is pending a careful review. Best regards, - Marcel > On 2 May 2016, at 11:21 PM, Marcel Böhme wrote: > > Hi, > > This fixes several stack overflows due to infinite recursion in d_print_comp > (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909). > >

Re: Fix for PR70926 in Libiberty Demangler (5)

Hi: Pending review. Best - Marcel > On 3 May 2016, at 10:40 PM, Marcel Böhme wrote: > > Hi, > > This fixes four access violations > (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70926). > > Two of these first read the value of a length variable len from the mangled