Re: [PATCH, GCC/ARM, ping] Remove ARMv8-M code for D17-D31

Committed (sorry for delay). Best regards, Thomas On 06/09/17 09:12, Kyrill Tkachov wrote: Hi Thomas, On 05/09/17 10:04, Thomas Preudhomme wrote: Ping? This is ok if a bootstrap and test run on arm-none-linux-gnueabihf shows no problems. Thanks, Kyrill Best regards, Thomas On

[committed] jit: handle equality of function pointer types

libgccjit was being overzealous when type-checking function pointers, requiring exact pointer equality of recording::function_type instances, defeating attempts by client code to work with function pointers as data. This patch removes the overzealous checking, and should allow function pointers

[committed] jit: document function pointers

This patch adds a new function-pointers.rst topic page to the libgccjit docs. Committed to trunk as r253257. gcc/jit/ChangeLog: * docs/topics/expressions.rst (Function calls): Add link to gcc_jit_context_new_function_ptr_type. (Function pointers): Convert to

[C++ PATCH] Stash bitfield width into DECL_BIT_FIELD_REPRESENTATIVE instead of DECL_INITIAL

Hi! On Wed, Sep 27, 2017 at 07:55:20AM -0700, Nathan Sidwell wrote: > 1) fix the parsing bug you found and move to (ab)using > DECL_BIT_FIELD_REPRESENTATIVE The following patch is the D_B_F_R part of the above. Bootstrapped/regtested on top of the patch I've just posted, ok for trunk?

Re: [PATCH] Enhance PHI processing in VN

David Edelsohn writes: > On Wed, Sep 27, 2017 at 6:58 PM, Richard Sandiford > wrote: >> David Edelsohn writes: >>> On Fri, Sep 15, 2017 at 2:53 AM, Richard Biener wrote: On Thu, 14 Sep 2017, David

Re: [PATCH][GRAPHITE] More TLC

On Wed, Sep 27, 2017 at 9:33 AM, Richard Biener wrote: > Looks like even when hacking the Fortran FE to produce nested > ARRAY_REFs we run into the same issue for > > (gdb) p debug_data_reference (dr) > #(Data Ref: > # bb: 17 > # stmt: >

Re: [PATCH, i386] Avoid 512-bit vector return constant for Intel AVX512 configuration

On Thu, Sep 28, 2017 at 4:05 PM, Shalnov, Sergey wrote: > Sorry. The patch is changed as you proposed. OK for mainline and committed. Thanks, Uros. > -Original Message- > From: Uros Bizjak [mailto:ubiz...@gmail.com] > Sent: Thursday, September 28, 2017 3:17 PM

[committed] Fix i386/pr82260-*.c testcases (PR target/82342)

Hi! When BMI2 is on, such as for -march=haswell defaulting gcc or when make check-gcc RUNTESTFLAGS='--target_board=unix\{-m64,-m64/-march=haswell\}' etc., these testcases emit sarx which is something the testcases didn't mean to test, they want to test what kind of insn is emitted to load the

Re: [PATCH][GRAPHITE] More TLC

On Wed, Sep 27, 2017 at 7:18 AM, Richard Biener wrote: > On Tue, 26 Sep 2017, Sebastian Pop wrote: > > > On Mon, Sep 25, 2017 at 8:12 AM, Richard Biener > wrote: > > > > > On Fri, 22 Sep 2017, Sebastian Pop wrote: > > > > > > > On Fri, Sep 22, 2017 at 8:03

[C++ PATCH] Fix attribute parsing for bitfields

On Wed, Sep 27, 2017 at 07:55:20AM -0700, Nathan Sidwell wrote: > Jakub, > > The following patch implements P0386R1 - NSDMIs for bit-fields. > > While working on that, I've discovered our parser mishandles attributes > > on bitfields, already C++11 says: > > identifier[opt]

Re: [PATCH] PR libstdc++/81469 deprecate std::uncaught_exception for C++17

Hi! On Wed, Sep 20, 2017 at 05:35:26PM +0100, Jonathan Wakely wrote: > C++17 deprecates uncaught_exception in favour of uncaught_exceptions, > so this adds the attribute. > > PR libstdc++/81469 > * libsupc++/exception (uncaught_exception): Deprecate for C++17. > *

Re: [PATCH] Fix fortran/81509

On Thu, Sep 28, 2017 at 10:46:06AM +0100, Paul Richard Thomas wrote: > > I'll take your word for it on the F2008 contraints. Given that the > patch is very good - OK for trunk. > The text for IAND from F2008 is Arguments. I shall be of type integer or a boz-literal-constant. J shall be

[patch, libfortran] Fix thead sanitizer issue with libgfortran

Hello world, the attached patch fixes the problem reported in PR 66756: When opeing a file, the main lock for all units was acquired, the unit lock was acquired, and then the main lock was released and re-aquired. To the thread sanitizer, this is a lock-order inversion. One option would have

[C PATCH] Fix flags on compound literal VAR_DECLs (PR c/82340)

Hi! As the testcase shows, while build_compound_literal had some code to set up TREE_READONLY flag on compound literal VAR_DECLs, it didn't handle volatile nor restrict quals. Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2017-09-28 Jakub Jelinek

[PATCH, i386]: Do not check index when encoding %esp as %rsp to avoid 0x67 prefix

As mentioned in the PR, SP_REG can not be encoded as index. 2017-09-28 Uros Bizjak * config/i386/i386.c (ix86_print_operand_address_as): Do not check index when encoding %esp as %rsp to avoid 0x67 prefix. Bootstrapped and regression tested on x86_64-linux-gnu

Re: [PATCH][GRAPHITE] More TLC

Hi skimo, On Tue, Sep 26, 2017 at 10:15 AM, Sven Verdoolaege < sven.verdoola...@gmail.com> wrote: > On Tue, Sep 26, 2017 at 09:19:50AM -0500, Sebastian Pop wrote: > > Sven, is there already a function that computes the sum of all > > strides in a proximity map? Maybe you have code that does > >

[C++ PATCH] Let make check-c++-all test also c++2a

Hi! On Wed, Sep 27, 2017 at 07:55:20AM -0700, Nathan Sidwell wrote: > I'm sorry for my tardiness. It think the patch would be better broken > apart: > 1) fix the parsing bug you found and move to (ab)using > DECL_BIT_FIELD_REPRESENTATIVE > > 2) the new c++2a feature > > Is that

Re: [PATCH][GRAPHITE] More TLC

On Wed, Sep 27, 2017 at 8:04 AM, Richard Biener wrote: > > Another thing I notice is that we don't handle the multi-dimensional > accesses the fortran frontend produces: > > (gdb) p debug_data_reference (dr) > #(Data Ref: > # bb: 18 > # stmt: _43 = *a_141(D)[_42]; > # ref:

C++ PATCH for c++/56973 (DR 696), lambda capture of const variables

The G++ lambda implementation previously implemented an early tentative resolution of DR 696, whereby mentions of an outer constant variable would immediately decay to the constant value of that variable. But the final resolution specified that we should capture or not depending on how the

Re: [PATCH][GRAPHITE] Simplify SCOP detection

On Wed, Sep 27, 2017 at 2:21 AM, Richard Biener wrote: > On Tue, 26 Sep 2017, Sebastian Pop wrote: > >> On Tue, Sep 26, 2017 at 7:03 AM, Richard Biener wrote: >> >> > >> > The following is the result of me trying to understand SCOP detection >> > and the

Re: Make tests less istreambuf_iterator implementation dependent

On 28/09/2017 14:12, Jonathan Wakely wrote: On 27/09/17 22:16 +0200, François Dumont wrote: Hi     I just committed attached patch as trivial.     Those tests were highly istreambuf_iterator implementation, it is the result of the call to money_get<>::get which is pointing immediately

Re: Make tests less istreambuf_iterator implementation dependent

On 28/09/17 21:59 +0200, François Dumont wrote: On 28/09/2017 14:12, Jonathan Wakely wrote: On 27/09/17 22:16 +0200, François Dumont wrote: Hi     I just committed attached patch as trivial.     Those tests were highly istreambuf_iterator implementation, it is the result of the call to

Re: 0002-Part-2.-Document-finstrument-control-flow-and-notrack attribute

On 09/27/2017 06:27 AM, Tsimbalist, Igor V wrote: > > > 0002-Add-documentation-for-fcf-protection-option-and-nocf.patch > > > From bc896670fef5eb7324c0e0134747696f3ed66553 Mon Sep 17 00:00:00 2001 > From: Igor Tsimbalist > Date: Sun, 17 Sep 2017 14:57:29 +0300 >

Re: [PATCH] PR libstdc++/81469 deprecate std::uncaught_exception for C++17

On 09/28/2017 11:52 AM, Jakub Jelinek wrote: Hi! On Wed, Sep 20, 2017 at 05:35:26PM +0100, Jonathan Wakely wrote: C++17 deprecates uncaught_exception in favour of uncaught_exceptions, so this adds the attribute. PR libstdc++/81469 * libsupc++/exception (uncaught_exception):

Re: 0001-Part-1.-Add-generic-part-for-Intel-CET-enabling

On 09/19/2017 07:39 AM, Tsimbalist, Igor V wrote: > Here is an updated patch (version #2). The main differences are: > > - Change attribute and option names; > - Add additional parameter to gimple_build_call_from_tree by adding a type > parameter and > use it 'nocf_check' attribute

Re: 0005-Part-5.-Add-x86-CET-documentation

On 09/27/2017 11:01 AM, Joseph Myers wrote: > On Wed, 27 Sep 2017, Florian Weimer wrote: > >> This is part of the ABI GCC implements, so it has to be documented somewhere, >> and not just as part of the GCC source code. >> >> CET is not properly described in the ABI supplement and I don't think

[PATCH], Add PowerPC ISA 3.0 IEEE 128-bit floating point round to odd built-in functions

This patch addss built-in functions on PowerPC ISA 3.0 (power9) that allow the user to access the round to odd IEEE 128-bit floating point instructions. I have checked it on a little endian power8 system doing a bootstrap and make check. There were no regressions in the testsuite. I verified

Re: 0003-Part-3.-Add-tests-for-finstrument-control-flow-and-notrack attribute

On 09/19/2017 07:58 AM, Tsimbalist, Igor V wrote: > Here is an updated patch (version #2). Mainly attribute and option names > were changed. > The test for ICF will be introduced in x86 specific tests (patch 0006-Part-6) > as the implementation > checks if the CF instrumentation is on to adjust

Re: [C++ PATCH] Stash bitfield width into DECL_BIT_FIELD_REPRESENTATIVE instead of DECL_INITIAL

On 09/28/2017 11:49 AM, Jakub Jelinek wrote: The following patch is the D_B_F_R part of the above. Bootstrapped/regtested on top of the patch I've just posted, ok for trunk? Looks good, a couple of nits. I think the bits out of the cp FE are sufficiently obvious given the cp changes. c/

Re: 0005-Part-5.-Add-x86-CET-documentation

On 09/27/2017 09:17 AM, Tsimbalist, Igor V wrote: >> > > 0005-Add-x86-CET-documentation.patch > > > From dda22b06a3a5bde9b0dc57585d878db520769510 Mon Sep 17 00:00:00 2001 > From: Igor Tsimbalist > Date: Tue, 4 Jul 2017 13:55:03 +0300 > Subject: [PATCH 5/6] Add x86

Re: [C++ PATCH] Fix attribute parsing for bitfields

On 09/28/2017 11:47 AM, Jakub Jelinek wrote: I don't see the first half of 1) related to second half thereof, the DECL_BIT_FIELD_REPRESENTATIVE is unrelated to the parsing bug, and a needed precondition of 2). That's very conscientious of you. As I said on IRC, I hope

Re: [C++ PATCH] Let make check-c++-all test also c++2a

On 09/28/2017 11:50 AM, Jakub Jelinek wrote: Hi! Here is the third patch, which enables testing c++2a in make check-c++-all. Regtested and regtested with make check-c++-all on x86_64-linux and i686-linux, ok for trunk? yup, thanks. -- Nathan Sidwell

Re: [PATCH][GRAPHITE] Remove another small quadraticness

On Wed, Sep 27, 2017 at 6:48 AM, Richard Biener wrote: > > Turns out loop_nest recorded in scop-info isn't really necessary as > we can simply process parameters in loop bounds during the gather_bbs > walk where we encounter each loop (identified by its header) once. > > This

Re: [PATCH][GRAPHITE] Speedup SCOP detection some more, add region handling to domwalk

On Wed, Sep 27, 2017 at 6:07 AM, Richard Biener wrote: > /* Maximal number of array references in a scop. */ > DEFPARAM (PARAM_GRAPHITE_MAX_ARRAYS_PER_SCOP, "graphite-max-arrays-per-scop", "maximum number of arrays per scop.", 100, 0, 0) Let's

Re: [PATCH][GRAPHITE] Allow --param graphite-max-arrays-per-scop=0

On Wed, Sep 27, 2017 at 6:51 AM, Richard Biener wrote: > > The following is to allow making --param graphite-max-arrays-per-scop > unbounded. That's a little tricky because the bound is used when > computing "alias-sets" for scalar constraints. There's an easy way > out

Re: [PATCH][GRAPHITE] Make --param loop-block-tile-size=0 disable tiling

On Wed, Sep 27, 2017 at 7:20 AM, Richard Biener wrote: > > Currently ISL aborts on this special value and for debugging (and > tuning?) it's nice to avoid all the clutter introduced by tiling. > > Committed as obvious. > > Richard. > > 2017-09-27 Richard Biener

Re: [PATCH][GRAPHITE] Speedup SCOP detection some more, add region handling to domwalk

On Wed, Sep 27, 2017 at 6:07 AM, Richard Biener wrote: > > This removes another quadraticness from SCOP detection, gather_bbs > domwalk. This is done by enhancing domwalk to handle SEME regions > via a special return value from before_dom_children. > > With this I'm now

Re: [C PATCH] Fix flags on compound literal VAR_DECLs (PR c/82340)

On Thu, 28 Sep 2017, Jakub Jelinek wrote: > Hi! > > As the testcase shows, while build_compound_literal had some code to set up > TREE_READONLY flag on compound literal VAR_DECLs, it didn't handle volatile > nor restrict quals. > > Fixed thusly, bootstrapped/regtested on x86_64-linux and

libbacktrace patch committed: Support compressed debug sections

This patch to libbacktrace adds support for compressed debug sections. Rather than require all users of libbacktrace to link against -lz, I wrote new code in libbacktrace to inflate a zlib stream. Because the code does not have to be as flexible as zlib, and because it is only used to uncompress

Re: [PATCH] Asm memory constraints

On Mon, Aug 21, 2017 at 10:29:30AM +0930, Alan Modra wrote: > Fixed in this revised patch. The only controversial aspect now should > be whether those array casts ought to be officially blessed. I've > checked that "=m" (*(T (*)[]) ptr), "=m" (*(T (*)[n]) ptr), and > "=m" (*(T (*)[10]) ptr), all

Re: 0005-Part-5.-Add-x86-CET-documentation

On 09/27/2017 09:17 AM, Tsimbalist, Igor V wrote: Updated version #3. diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index e52a1ea..accba40 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -5655,6 +5655,14 @@ compiled with the @option{-fcf-protection=branch} option. The

Re: 0002-Part-2.-Document-finstrument-control-flow-and-notrack attribute

On 09/27/2017 06:27 AM, Tsimbalist, Igor V wrote: Updated version #4. [snip] @@ -11348,6 +11349,31 @@ is used to link a program, the GCC driver automatically links against @file{libmpxwrappers}. See also @option{-static-libmpxwrappers}. Enabled by default. +@item

[PATCH, rs6000] Follow-on fix for PR target/80210: ICE in extract_insn

This patch fixes two new issues exposed (but not caused) by the original test case added for PR80210 as well as a modified version of that test case. The first problem is that the test case pr80210.c ICEs on 32-bit compiles that do not pass either an explicit or implicit -mcpu=... option. I did

[openacc, testsuite, committed] Fix libgomp.oacc-c-c++-common/loop-g-{1,2}.c for non-nvidia devices

Hi, this patch makes the test-cases libgomp.oacc-c-c++-common/loop-g-{1,2}.c work for non-nvidia devices. For nvidia devices, a vector_length of 32 is required for the test to pass. For devices with a non-32 forced vector_length, this test-case will fail the test for excess errors due to:

[PATCH 5/5] New target check: vect_can_peel

gcc/ChangeLog: 2017-09-28 Andreas Krebbel * doc/sourcebuild.texi: Document vect_can_peel. gcc/testsuite/ChangeLog: 2017-09-28 Andreas Krebbel * g++.dg/vect/slp-pr56812.cc: xfail for targets which don't want

Re: [PATCH 4/5] New target check: vect_nopeel - v2

On 09/26/2017 06:49 PM, Richard Sandiford wrote: > Andreas Krebbel writes: ... > Sorry for the bikeshedding, but how about having a positive test > like vect_can_peel instead? ! vect_no... can be hard to read in > complex conditions. (There's already that problem

Re: [libgomp, testsuite] Remove superfluous -fopenmp from libgomp testcases

On 09/28/2017 10:37 AM, Thomas Schwinge wrote: Hi Tom! On Thu, 28 Sep 2017 09:41:15 +0200, Tom de Vries wrote: On 11/07/2013 09:11 AM, Jakub Jelinek wrote: On Wed, Nov 06, 2013 at 08:42:16PM +0100, tho...@codesourcery.com wrote: From: Thomas Schwinge

[PATCH 4/5] New target check for double<->int conversions

gcc/ChangeLog: 2017-09-28 Andreas Krebbel * doc/sourcebuild.texi: Document vect_intdouble_cvt and vect_doubleint_cvt. gcc/testsuite/ChangeLog: 2017-09-28 Andreas Krebbel * gcc.dg/vect/pr66251.c: Replace

[PATCH 3/5] New target check: vect_long_mult

We don't have a 64 bit vector integer multiply on z. Add a specific check for that. gcc/ChangeLog: 2017-09-28 Andreas Krebbel * doc/sourcebuild.texi: Document vect_long_mult. gcc/testsuite/ChangeLog: 2017-09-28 Andreas Krebbel

Re: [PATCH 4/5] New target check: vect_nopeel - v2

On 09/27/2017 07:30 PM, Sandra Loosemore wrote: > On 09/27/2017 03:05 AM, Rainer Orth wrote: >> Hi Andreas, >> >>> On 09/27/2017 10:10 AM, Rainer Orth wrote: Hi Andreas, > On 09/26/2017 02:26 PM, Rainer Orth wrote: >> Hi Andreas, >> >>> diff --git

Re: [PATCH] libstdc++: istreambuf_iterator keep attached streambuf

On Thu, 28 Sep 2017 11:34:25 +0100 Jonathan Wakely wrote: > On 23/09/17 09:54 +0300, Petr Ovtchenkov wrote: > >istreambuf_iterator should not forget about attached > >streambuf when it reach EOF. > > > >Checks in debug mode has no infuence more on character > >extraction in

Re: Make tests less istreambuf_iterator implementation dependent

On 27/09/17 22:16 +0200, François Dumont wrote: Hi     I just committed attached patch as trivial.     Those tests were highly istreambuf_iterator implementation, it is the result of the call to money_get<>::get which is pointing immediately beyond the last character recognized to quote

Avoid assembler warnings from AArch64 constructor/destructor priorities

Many GCC tests fail for AArch64 with current binutils because of assembler warnings of the form "Warning: ignoring incorrect section type for .init_array.00100". The same issue was fixed for ARM in r247015 by using SECTION_NOTYPE when creating those sections; this patch applies the same fix to

Re: [PATCH] libstdc++: istreambuf_iterator keep attached streambuf

On 23/09/17 09:54 +0300, Petr Ovtchenkov wrote: istreambuf_iterator should not forget about attached streambuf when it reach EOF. Checks in debug mode has no infuence more on character extraction in istreambuf_iterator increment operators. In this aspect behaviour in debug and non-debug mode is

Re: correct attribute ifunc C++ type safety (PR 82301)

On 09/25/2017 02:03 AM, Martin Sebor wrote: > +a @option{-Wincompatible-pointer-types} warning for mismatches. To suppress > +a warning for the necessary cast from a pointer to the implementation member > +function to the type of the corresponding non-member function use the >

Re: [PATCH] Fix fortran/81509

Hi Steve, I'll take your word for it on the F2008 contraints. Given that the patch is very good - OK for trunk. Thanks Paul On 27 September 2017 at 20:36, Steve Kargl wrote: > The attached patch fixes PR fortran/81509. > > In short, F2008 now allows

Re: [PATCH][mingw] Enable colorized diagnostics

On 2017/9/28 7:37, JonY wrote: Does it make sense to use a global lock in mingw_ansi_fputs? I was thinking about a named Mutex object. Named Mutexes (as well as Events and Semaphores) can be shared across processes, but there are other considerations: 1. The name of the Mutex should base

Re: [Patch][aarch64] Use IFUNCs to enable LSE instructions in libatomic on aarch64

On 31/08/17 18:24, Steve Ellcey wrote: > On Tue, 2017-08-29 at 12:25 +0100, Szabolcs Nagy wrote: >> > >> > in glibc the hwcap is not used, because it has accesses to >> > cached dispatch info, but in libatomic using the hwcap >> > argument is the right way. > Here is an updated version of the

Re: [PATCH] streambuf_iterator: avoid debug-dependent behaviour

On 28/09/17 11:50 +0100, Jonathan Wakely wrote: On 21/09/17 07:46 +0200, François Dumont wrote: Gentle reminder, ok to commit ? No. Could you and Petr please come to an agreement about what is actually wrong with the current implementation, and agree on a solution? Currently you're both just

[PATCH 0/5] vect testsuite adjustments for S/390 - v2

Changes to last version: - vect_mult_long renamed to vect_long_mult (since there is already vect_int_mult ...) - vect_no_peel changed to vect_can_peel as suggested by Richard - another two target checks added: vect_intdouble_cvt and vect_doubleint_cvt - documentation for the new target checks

[PATCH 1/5] Enable vect_float with S/390 VXE and adjust testcases

The target supports routines provide vect_double and vect_float but these do not appear to be used consequently in the vect testcases. With z13 we only have support for vector double but with z14 also for vector float. This patch adds vect_float to the testcases using the float data type and make

[PATCH 2/5] Testcases using dg-options require at least -mzarch.

Testcases which override the vect default options using dg-options need at least -mzarch on S/390 32 bit. gcc/testsuite/ChangeLog: 2017-09-28 Andreas Krebbel * gfortran.dg/vect/fast-math-mgrid-resid.f: Use -mzarch on S/390. *

Re: [PATCH] streambuf_iterator: avoid debug-dependent behaviour

On 21/09/17 07:46 +0200, François Dumont wrote: Gentle reminder, ok to commit ? No. Could you and Petr please come to an agreement about what is actually wrong with the current implementation, and agree on a solution? Currently you're both just proposing patches that do different things,

Re: [ARM,testsuite] Some tests require arm_neon_hw

On 28/09/17 14:09, Christophe Lyon wrote: > Hi, > > I've noticed that a few dg-run arm tests require Neon to execute, but > do not ensure that. They only check that the compiler options are > support. This small patch fixes that by adding arm_neon_hw > effective-target. > > This makes the tests

Re: Enable ifunc attribute by default for SPARC GNU/Linux

> Similar to other architectures with IFUNC binutils/glibc support, this > patch enables the ifunc attribute for SPARC GNU/Linux. This is needed > for building glibc with the current checks on IFUNC resolver types > (and use of the attribute in glibc rather than manually created IFUNCs > is

Re: [PATCH] libstdc++: istreambuf_iterator keep attached streambuf

On 28/09/17 15:06 +0300, Petr Ovtchenkov wrote: On Thu, 28 Sep 2017 11:34:25 +0100 Jonathan Wakely wrote: On 23/09/17 09:54 +0300, Petr Ovtchenkov wrote: >istreambuf_iterator should not forget about attached >streambuf when it reach EOF. > >Checks in debug mode has no

Re: Avoid assembler warnings from AArch64 constructor/destructor priorities

On 28/09/17 13:31, Joseph Myers wrote: > Many GCC tests fail for AArch64 with current binutils because of > assembler warnings of the form "Warning: ignoring incorrect section > type for .init_array.00100". The same issue was fixed for ARM in > r247015 by using SECTION_NOTYPE when creating those

[PATCH, i386] Avoid 512-bit vector return constant for Intel AVX512 configuration

Hi, GCC uses full 512-bit register to return the constant from the function. The patch avoid 512-bit register usage if "-mprefer-avx256" option used. 2017-09-28 Sergey Shalnov gcc/ * config/i386/i386.md(*movsf_internal, *movdf_internal): Return

Re: [PATCH, i386] Avoid 512-bit vector return constant for Intel AVX512 configuration

On Thu, Sep 28, 2017 at 3:08 PM, Shalnov, Sergey wrote: > Hi, > GCC uses full 512-bit register to return the constant from the function. > The patch avoid 512-bit register usage if "-mprefer-avx256" option used. > > 2017-09-28 Sergey Shalnov

[RFA gfortran] PR 25071: dummy argument larger than actual argument

Hi all, In the PR there was some consensus to turn the warnings into errors. This is what the patch does: the warnings are kept with -std=legacy, errors are emitted otherwise. I am sure it may exist a better solution, but I did not find it. While regtesting I have found several regressions

[ARM,testsuite] Some tests require arm_neon_hw

Hi, I've noticed that a few dg-run arm tests require Neon to execute, but do not ensure that. They only check that the compiler options are support. This small patch fixes that by adding arm_neon_hw effective-target. This makes the tests unsupported on the related configurations (eg cortex-m3 ,

RE: [PATCH, i386] Avoid 512-bit vector return constant for Intel AVX512 configuration

Sorry. The patch is changed as you proposed. -Original Message- From: Uros Bizjak [mailto:ubiz...@gmail.com] Sent: Thursday, September 28, 2017 3:17 PM To: Shalnov, Sergey Cc: gcc-patches@gcc.gnu.org; kirill.yuk...@gmail.com; Senkevich, Andrew

Re: correct attribute ifunc C++ type safety (PR 82301)

On 09/24/2017 06:03 PM, Martin Sebor wrote: r253041 enhanced type checking for alias and ifunc attributes to detect declarations of incompatible aliases, or ifunc resolvers that return pointers to functions of an incompatible type.  More extensive testing exposed a bug in the implementation of

Re: [PATCH] For -Os change movabsq $(imm32 << shift), %rX[xip] to movl $imm2, %eX[xip]; shl $shift, %rX[xip] (PR target/82339)

On Wed, Sep 27, 2017 at 3:36 PM, Jakub Jelinek wrote: > Hi! > > Doing a movl + shlq by constant seems to be 1 byte shorter > than movabsq, so this patch attempts to use the former form > unless flags is live. > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for

[libgomp, testsuite] Remove superfluous -fopenmp from libgomp testcases

[ was: Re: [gomp4 2/9] libgomp: Prepare for testcases without -fopenmp. ] On 11/07/2013 09:11 AM, Jakub Jelinek wrote: On Wed, Nov 06, 2013 at 08:42:16PM +0100, tho...@codesourcery.com wrote: From: Thomas Schwinge libgomp/ * testsuite/lib/libgomp.exp

Re: [libgomp, testsuite] Remove superfluous -fopenmp from libgomp testcases

Hi Tom! On Thu, 28 Sep 2017 09:41:15 +0200, Tom de Vries wrote: > On 11/07/2013 09:11 AM, Jakub Jelinek wrote: > > On Wed, Nov 06, 2013 at 08:42:16PM +0100, tho...@codesourcery.com wrote: > >> From: Thomas Schwinge > >> > >>libgomp/ > >>*

Re: [libgomp, testsuite] Remove superfluous -fopenmp from libgomp testcases

On Thu, Sep 28, 2017 at 09:41:15AM +0200, Tom de Vries wrote: > [ was: Re: [gomp4 2/9] libgomp: Prepare for testcases without -fopenmp. ] > > On 11/07/2013 09:11 AM, Jakub Jelinek wrote: > > On Wed, Nov 06, 2013 at 08:42:16PM +0100, tho...@codesourcery.com wrote: > > > From: Thomas Schwinge

Re: [PATCH][AArch64] Add BIC-imm and ORR-imm SIMD pattern

On 27/09/17 18:57, Sudi Das wrote: > > > Hi James > > I have made the requested changes to the patch. > > > 2017-09-27 Sudakshina Das > > * config/aarch64/aarch64-protos.h (enum simd_immediate_check): New > check type > for aarch64_simd_valid_immediate. >