[Bug fortran/71592] Add some facilities for compile-time check

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71592 --- Comment #4 from Jakub Jelinek --- (In reply to 鍾 from comment #2) > (In reply to Jakub Jelinek from comment #1) > > You can't use such static_assert this way in C++, unless the function is > > constexpr, nor in C (always), so guess you are

Re: [PATCH] Add a new target hook to compute the frame layout

On 06/21/16 23:29, Jeff Law wrote: > On 06/16/2016 08:47 AM, Bernd Edlinger wrote: >> Hi! >> >> >> By the design of the target hook INITIAL_ELIMINATION_OFFSET >> it is necessary to call this function several times with >> different register combinations. >> Most targets use a cached data structure

[Bug fortran/71592] Add some facilities for compile-time check

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71592 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c++/71616] New: ICE on valid C++ code at -O1 and above on x86_64-linux-gnu: in binds_to_current_def_p, at symtab.c:2232

with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto --prefix=/usr/local/gcc-trunk --disable-bootstrap Thread model: posix gcc version 7.0.0 20160621 (experimental) [trunk revision 237650] (GCC) $ $ g++-trunk -O0 -c small.cpp $ g++-6.1 -O1 -c small.cpp $ $ g++-trunk -O1 -c small.cpp

[Bug fortran/71592] Add some facilities for compile-time check

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71592 --- Comment #2 from 鍾 --- (In reply to Jakub Jelinek from comment #1) > You can't use such static_assert this way in C++, unless the function is > constexpr, nor in C (always), so guess you are proposing something > completely different (like,

[Bug target/71615] wrong float point result with {-Ofast, -march=native, and valgrind}

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71615 Andrew Pinski changed: What|Removed |Added Target||x86_64-pc-linux-gnu

Re: C, C++: Fix PR 69733 (bad location for ignored qualifiers warning)

On 05/04/2016 09:17 AM, Bernd Schmidt wrote: On 04/25/2016 10:18 PM, Joseph Myers wrote: On Fri, 22 Apr 2016, Bernd Schmidt wrote: +/* Returns the smallest location != UNKNOWN_LOCATION in LOCATIONS, + considering only those c_declspec_words found in LIST, which + must be terminated by

[Bug fortran/71615] New: wrong float point result with {-Ofast, -march=native, and valgrind}

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71615 Bug ID: 71615 Summary: wrong float point result with {-Ofast, -march=native, and valgrind} Product: gcc Version: 5.3.1 Status: UNCONFIRMED Severity: major

Re: [PR66726] Fix regression caused by Factor conversion out of COND_EXPR

On 06/01/2016 04:46 AM, kugan wrote: Hi All, Factoring out CONVERT_EXPR introduced a regression for (PR66726). I had to revert my previous patch due to some regressions. This is a much simplified version compared to the one I reverted. There is a test-case (pr46309.c) in the test-suite which

Re: [PATCH PING] boehm-gc: check for execinfo.h directly

On 06/21/2016 06:59 PM, Mike Frysinger wrote: On 21 Jun 2016 15:46, Jeff Law wrote: If accepted into upstream Boehm-GC, then this is obviously acceptable in GCC's copy. so changes can be pushed directly if it's already in upstream ? my original goal is already fixed in upstream, but it's not

Re: [PATCH] Print column numbers in inclusion trace consistently.

On 06/03/2016 05:24 AM, Marcin Baczyński wrote: 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

Re: Unreviewed patches

On 06/06/2016 02:16 AM, Rainer Orth wrote: The following patches have remained unreviewed for a week: [gotools, libcc1] Update copyright dates https://gcc.gnu.org/ml/gcc-patches/2016-05/msg02307.html Everything bug the gotools changes are OK. THe master bits for gotools is

[PATCH] Implement -fdiagnostics-parseable-fixits

Both GCC and Clang can emit "fix-it" hints for a diagnostic, giving a suggestion about how to fix the issue. Clang has an option -fdiagnostics-parseable-fixits, which emits a machine-readable version of the fixits, for use by IDEs. (The only IDE I know of that supports this format is Xcode [1];

Re: [PATCH 2/2] gcc: Update comment in bb-reorder.c

On 06/10/2016 10:56 AM, Andrew Burgess wrote: * gcc/bb-reorder.c (pass_partition_blocks::gate): Update comment. Thanks. Installed. jeff

Re: [PATCH 1/2] gcc: Remove unneeded global flag.

On 06/10/2016 10:56 AM, Andrew Burgess wrote: The global flag `user_defined_section_attribute' is set while parsing C code when the section attribute is encountered. The flag is set when anything has the section attribute applied to it, functions or data. The only place this global was used

[Bug middle-end/71614] ppc __gcc_qmul is mis-optimized not to be commutative

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71614 --- Comment #5 from Andrew Pinski --- The other thing to note is: https://gcc.gnu.org/ml/gcc-patches/2014-01/msg00157.html

[Bug middle-end/71614] ppc __gcc_qmul is mis-optimized not to be commutative

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71614 --- Comment #4 from Andrew Pinski --- The fix would then put a barrier to force GCC not to do contracting. Something like: v = a*d; w = b*c; asm("":"+f"(v)); asm("":"+f"(w)); tau += v + w; /* Add in other second-order terms. */

[Bug middle-end/71614] ppc __gcc_qmul is mis-optimized not to be commutative

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71614 --- Comment #3 from Tim Shen --- (In reply to Andrew Pinski from comment #2) > Two things, try -fno-strict-aliasing first. > Since your main violates C aliasing rules. > Second thing to try is -ffp-contract=off as I am suspecting: > v = a*d; >

[Bug middle-end/71614] ppc __gcc_qmul is mis-optimized not to be commutative

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71614 --- Comment #2 from Andrew Pinski --- Two things, try -fno-strict-aliasing first. Since your main violates C aliasing rules. Second thing to try is -ffp-contract=off as I am suspecting: v = a*d; w = b*c; tau += v + w; /* Add in other

[Bug middle-end/71614] ppc __gcc_qmul is mis-optimized not to be commutative

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71614 --- Comment #1 from Tim Shen --- > Suppose the attached file is a.c s/a\.c/b.c

[Bug middle-end/71614] New: ppc __gcc_qmul is mis-optimized not to be commutative

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71614 Bug ID: 71614 Summary: ppc __gcc_qmul is mis-optimized not to be commutative Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3

Re: [PATCH PING] boehm-gc: check for execinfo.h directly

On 21 Jun 2016 15:46, Jeff Law wrote: > On 06/13/2016 11:40 AM, Mike Frysinger wrote: > > The current header depends on glibc version checks to determine whether > > execinfo.h exists which breaks uClibc. Instead, add an explicit configure > > check for it. > > > > 2015-08-29 Mike Frysinger

Re: [PATCH, rs6000] Prefer vspltisw/h over xxspltib+instruction when available

> On Jun 21, 2016, at 5:34 PM, Segher Boessenkool > wrote: > > On Tue, Jun 21, 2016 at 03:14:51PM -0500, Bill Schmidt wrote: >> I discovered recently that, with -mcpu=power9, an attempt to generate a >> vspltish instruction resulted instead in an xxspltib followed

[Bug fortran/71580] Internal compiler error associated with type bound defined assignment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71580 Ian Harvey changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug fortran/70864] internal compiler error: in gfc_get_symbol_decl, at fortran/trans-decl.c:1403

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70864 Ian Harvey changed: What|Removed |Added CC||ian_harvey at bigpond dot com --- Comment

[Bug target/54412] Request for 32-byte stack alignment with -mavx on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412 Joseph Coffland changed: What|Removed |Added CC||gcc at joe dot coffland.com ---

Re: [7/7] Add negative and zero strides to vect_memory_access_type

On 06/15/2016 02:53 AM, Richard Sandiford wrote: This patch uses the vect_memory_access_type from patch 6 to represent the effect of a negative contiguous stride or a zero stride. The latter is valid only for loads. Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install? Thanks,

gcc-5-20160621 is now available

Snapshot gcc-5-20160621 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/5-20160621/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 5 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5

Re: [6/7] Explicitly classify vector loads and stores

On 06/15/2016 02:52 AM, Richard Sandiford wrote: This is the main patch in the series. It adds a new enum and routines for classifying a vector load or store implementation. Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install? Thanks, Richard gcc/ * tree-vectorizer.h

Re: [PATCH, rs6000] Prefer vspltisw/h over xxspltib+instruction when available

On Tue, Jun 21, 2016 at 03:14:51PM -0500, Bill Schmidt wrote: > I discovered recently that, with -mcpu=power9, an attempt to generate a > vspltish instruction resulted instead in an xxspltib followed by a vupkhsb. > This is semantically correct but the extra instruction is not optimal. I >

Re: [PATCH] Drop excess size used for run time allocated stack variables.

On 06/21/2016 03:35 AM, Dominik Vogt wrote: What do we do now with the two patches? At the moment, the functional patch depends on the changes in the cleanup patch, so it cannot be applied on its own. Options: (with the requested cleanup in the functional patch) 1) Apply both patches as

Re: [PATCH] Fix bootstrap on hppa*-*-hpux*

On 05/20/2016 12:09 PM, John David Anglin wrote: On 2016-05-18 2:20 AM, Jakub Jelinek wrote: On Tue, May 17, 2016 at 08:31:00PM -0400, John David Anglin wrote: >r235550 introduced the use of long long, and the macros LLONG_MIN and LLONG_MAX. These macros >are not defined by default and we

[Bug target/70123] [5 Regression] Miscompilation of cfitsio testcase on s390x-linux starting with r222144

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70123 --- Comment #11 from Jeffrey A. Law --- Certainly OK by me to backport to gcc-5. So go for it Bernd when you're back from PTO.

Re: [PATCH] Improve TBAA with unions

On 05/24/2016 03:14 AM, Richard Biener wrote: On Wed, 18 May 2016, Richard Biener wrote: The following adjusts get_alias_set beahvior when applied to union accesses to use the union alias-set rather than alias-set zero. This is in line with behavior from the alias oracle which (bogously)

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

On 05/26/2016 10:16 AM, Nick Clifton wrote: 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

Re: [PATCH PR68030/PR69710][RFC]Introduce a simple local CSE interface and use it in vectorizer

On 06/06/2016 05:23 AM, Bin.Cheng wrote: Hi Jeff, What's your opinion on this (and how to extend it to a region based interface)? I will update this patch for further review if you are okay. I've never pondered how to revamp DOM into a regional interface (though I have pondered how to revamp

Re: [PATCH PR68030/PR69710][RFC]Introduce a simple local CSE interface and use it in vectorizer

On 05/27/2016 05:56 AM, Richard Biener wrote: On Fri, May 27, 2016 at 1:11 PM, Bin.Cheng wrote: On Fri, May 27, 2016 at 11:45 AM, Richard Biener wrote: On Wed, May 25, 2016 at 1:22 PM, Bin Cheng wrote: Hi, As analyzed in

Re: [PATCH PING] boehm-gc: check for execinfo.h directly

On 06/13/2016 11:40 AM, Mike Frysinger wrote: The current header depends on glibc version checks to determine whether execinfo.h exists which breaks uClibc. Instead, add an explicit configure check for it. 2015-08-29 Mike Frysinger * configure.ac: Call

[Bug c/71613] Useful warnings silenced when macros from system headers are used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613 --- Comment #2 from joseph at codesourcery dot com --- Really we need to review warnings and work out in each case what's right for macros from system headers. If the issue is about the macro's contents, the warnings should be avoided; if it

Re: [PATCH 4/4] C FE: suggest corrections for misspelled identifiers and type names

On 06/14/2016 09:15 AM, David Malcolm wrote: This patch introduces a new lookup_name_fuzzy function to the C frontend and uses it to provides suggestions for various error messages that may be due to misspellings, and also for the warnings in implicit_decl_warning. This latter part may be

[Ada] clean up handling of DECL_ORIGINAL_TYPE in gigi

More specifically the ??? comment: /* ??? Copy and original type are not supposed to be variant but we really need a variant for the placeholder machinery to work. */ if (TYPE_IS_FAT_POINTER_P (t)) tt = build_variant_type_copy (t); else

Re: [PATCH] Reject boolean/enum types in last arg of __builtin_*_overflow_p (take 2)

On 06/15/2016 05:47 AM, Jakub Jelinek wrote: On Tue, Jun 14, 2016 at 11:13:28AM -0600, Martin Sebor wrote: Here is an untested patch for that. Except that the middle-end considers conversions between BOOLEAN_TYPE and single bit unsigned type as useless, so in theory this can't work well, and

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

On June 21, 2016 5:50:26 PM GMT+02:00, James Greenhalgh wrote: > >On Fri, Jun 03, 2016 at 12:39:42PM +0200, Richard Biener wrote: >> On Thu, Jun 2, 2016 at 6:53 PM, James Greenhalgh >> wrote: >> > >> > Hi, >> > >> > This patch introduces a new

Re: [PATCH] Add a new target hook to compute the frame layout

On 06/16/2016 08:47 AM, Bernd Edlinger wrote: Hi! By the design of the target hook INITIAL_ELIMINATION_OFFSET it is necessary to call this function several times with different register combinations. Most targets use a cached data structure that describes the exact frame layout of the current

Re: Implement C _FloatN, _FloatNx types [version 2]

On Tue, 21 Jun 2016, Michael Meissner wrote: > While from one perspective, it would have been cleaner if the PowerPC > had separate internal types for IBM extended double and IEEE 128-bit floating > point. But the way the compiler has been implemented is that TFmode is which > ever type is the

[Bug c/71613] Useful warnings silenced when macros from system headers are used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613 Manuel López-Ibáñez changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

Re: [PATCH, PR middle-end/71488] Fix vectorization of comparison of booleans

On 06/16/2016 05:06 AM, Ilya Enkovich wrote: Hi, This patch fixes incorrect comparison vectorization for booleans. The problem is that regular comparison which works for scalars doesn't work for vectors due to different binary representation. Also this never works for scalar masks. This patch

[Bug c/71610] Improve location for "warning: ISO C restricts enumerator values to range of ‘int’ [-Wpedantic]"?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71610 Manuel López-Ibáñez changed: What|Removed |Added Keywords||easyhack

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

On Tue, 21 Jun 2016, Michael Meissner wrote: > > I'm now working on support for TS 18661-3 _FloatN / _FloatNx type names > > (keywords), constant suffixes and addiitions. That will > > address, for C, the need to use modes for complex float128 (bug 32187) by > > allowing the standard

[Bug c/71567] Incorrect loop optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71567 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org ---

Re: Implement C _FloatN, _FloatNx types [version 2]

On Tue, Jun 21, 2016 at 05:41:36PM +, Joseph Myers wrote: > [Changes in version 2 of the patch: > > * PowerPC always uses KFmode for _Float128 and _Float64x when those > types are supported, not TFmode. While from one perspective, it would have been cleaner if the PowerPC had separate

[Bug c/71597] Confusing error for incompatible enums, wrong previous declaration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71597 Manuel López-Ibáñez changed: What|Removed |Added Keywords||diagnostic

[Bug c/71603] pragma diagnostic pop fails to restore warning level

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71603 Manuel López-Ibáñez changed: What|Removed |Added Keywords||diagnostic, easyhack

[PATCH, rs6000] Prefer vspltisw/h over xxspltib+instruction when available

Hi, I discovered recently that, with -mcpu=power9, an attempt to generate a vspltish instruction resulted instead in an xxspltib followed by a vupkhsb. This is semantically correct but the extra instruction is not optimal. I found that there was some logic in xxspltib_constant_p to do

[Bug tree-optimization/71609] [7 regression] test case gfortran.dg/vect/vect-8.f90 fails starting with r237549

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71609 Bill Seurer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: [PATCH 2/3] Add support for arm*-*-phoenix* targets.

On 06/15/2016 08:22 AM, Kuba Sejdak wrote: Is it ok for trunk? If possible, If possible, please merge it also to GCC-6 and GCC-5 branches. 2016-06-15 Jakub Sejdak * config.gcc: Add support for arm*-*-phoenix* targets. * config/arm/t-phoenix: New. *

Re: [PATCH 3/3] Add support for arm*-*-phoenix* targets in libgcc.

On 06/15/2016 08:22 AM, Kuba Sejdak wrote: Is it ok for trunk? If possible, If possible, please merge it also to GCC-6 and GCC-5 branches. 2016-06-15 Jakub Sejdak * config.host: Add suport for arm*-*-phoenix* targets. OK for the trunk. jeff

Re: [PATCH 1/3] Disable libgcj and libgloss for Phoenix-RTOS targets.

On 06/15/2016 08:22 AM, Kuba Sejdak wrote: This patch disables libgcj and libgloss in main configure.ac for new OS port - Phoenix-RTOS. Those libs are unnecessary to build GCC or newlib for arm-phoenix. Is it ok for trunk? If possible, If possible, please merge it also to GCC-6 and GCC-5

[Bug fortran/71068] [5/6/7 Regression] ICE in check_data_variable(): Bad expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71068 Tobias Burnus changed: What|Removed |Added Status|NEW |RESOLVED CC|

Re: [PATCH], Simplify setup of complex types

On 06/21/2016 07:48 AM, Michael Meissner wrote: When I submitted the back port to allow complex __float128 to be created on the PowerPC to the GCC 6.2 branch, Richard Biener suggested a simpler way to set the complex type: https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01114.html This patch

Re: [PATCH] x86-64: Load external function address via GOT slot

On Tue, Jun 21, 2016 at 11:22 AM, Uros Bizjak wrote: > On Tue, Jun 21, 2016 at 2:40 PM, H.J. Lu wrote: >> On Mon, Jun 20, 2016 at 12:46 PM, Richard Sandiford >> wrote: >>> Uros Bizjak writes: On Mon,

Re: Deprecating basic asm in a function - What now?

On Tue, Jun 21, 2016 at 06:29:45PM +, Bernd Edlinger wrote: > I do not like the idea to deprecate the basic asm at all, I must admit, > but I think if we added a warning, that just contains a positive information, > like > "warning: basic asm semantic has been changed to implicitly clobber

[Bug fortran/71612] [Coarray] Wrongly rejects coindexed variables in READ

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71612 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/71612] [Coarray] Wrongly rejects coindexed variables in READ

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71612 --- Comment #1 from Tobias Burnus --- Something like the following is needed; the first part should be fine (untested) and be sufficient for compiling the code, but the FIXME is required to get it actually working ... diff --git

[Bug c/71613] New: Useful warnings silenced when macros from system headers are used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613 Bug ID: 71613 Summary: Useful warnings silenced when macros from system headers are used Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

[Bug sanitizer/71611] New: UBSan shows type '' for enums based on long

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71611 Bug ID: 71611 Summary: UBSan shows type '' for enums based on long Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [PATCH] Giant concepts patch

I've pushed my work-in-progress integration branch to jason/concepts-rewrite. Jason On Mon, Jun 20, 2016 at 4:28 PM, Jason Merrill wrote: > On Fri, Mar 25, 2016 at 1:33 AM, Andrew Sutton > wrote: >> I'll just leave this here... >> >> This patch

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

On Thu, Jun 16, 2016 at 10:06:48PM +, Joseph Myers wrote: > On Wed, 15 Jun 2016, Michael Meissner wrote: > > > Note, I do feel the front ends should be modified to allow __complex > > __float128 > > directly rather than having to use an attribute to force the complex type > > (and > > to

[Bug c/71610] New: Improve location for "warning: ISO C restricts enumerator values to range of ‘int’ [-Wpedantic]"?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71610 Bug ID: 71610 Summary: Improve location for "warning: ISO C restricts enumerator values to range of ‘int’ [-Wpedantic]"? Product: gcc Version: 7.0 Status: UNCONFIRMED

[Bug fortran/71068] [5/6/7 Regression] ICE in check_data_variable(): Bad expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71068 --- Comment #4 from Tobias Burnus --- Author: burnus Date: Tue Jun 21 18:36:25 2016 New Revision: 237656 URL: https://gcc.gnu.org/viewcvs?rev=237656=gcc=rev Log: 2016-06-20 Tobias Burnus PR fortran/71068 *

Re: Deprecating basic asm in a function - What now?

On 21/06/2016 17:53, Andrew Haley wrote: > On 21/06/16 17:43, Jeff Law wrote: > > I think there's enough resistance to deprecating basic asms within a > > function that we should probably punt that idea. > > > > I do think we should look to stomp out our own uses of basic asms > > within

Re: [PATCH] x86-64: Load external function address via GOT slot

On Tue, Jun 21, 2016 at 2:40 PM, H.J. Lu wrote: > On Mon, Jun 20, 2016 at 12:46 PM, Richard Sandiford > wrote: >> Uros Bizjak writes: >>> On Mon, Jun 20, 2016 at 9:19 PM, H.J. Lu wrote: On Mon, Jun

Re: [Patch, Fortran] PR71068 - fix ICE on invalid with coindexed DATA

Dear Paul, Paul Richard Thomas wrote: Thanks for the patch Thanks also from my side. PS Why, in principle, can data objects not have co-indices? I think there is no really fundamental reason, but it doesn't make really sense. DATA is an explicit initialization, similar to "integer :: i

C++ PATCH for concept checking in non-dependent expressions

Concept code also needs some updates to accommodate my GCC 7 fix for 10200. First, and not limited to concepts, we need to treat a member template as dependent if its signature depends on template parameters of its enclosing class (which, more importantly, are template parameters of the scope

[Bug target/71103] avr-gcc crashes with unrecognizable insn error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71103 Georg-Johann Lay changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

Re: [Patch, Fortran] PR71068 - fix ICE on invalid with coindexed DATA

Dear Tobias, "Beauty is in the eye of the beholder!" It works, it's good :-) OK for trunk Thanks for the patch Paul PS Why, in principle, can data objects not have co-indices? On 21 June 2016 at 16:15, Tobias Burnus wrote: > Dear all, > > the problem comes

[PATCH, rs6000] Scheduling update

This patch adds instruction scheduling support for the Power9 processor. Bootstrap/regression tested on powerpc64/powerpc64le with no new failures. Ok for trunk? Ok for backport to GCC 6 branch after successful bootstrap/regtest there? -Pat 2016-06-21 Pat Haugen

Implement C _FloatN, _FloatNx types [version 2]

[Changes in version 2 of the patch: * PowerPC always uses KFmode for _Float128 and _Float64x when those types are supported, not TFmode. * More thorough checking for back ends using too-low precision values for modes, to avoid that causing too-low precision values for types. * Patch

Re: [Fortran, Patch] First patch for coarray FAILED IMAGES (TS 18508)

* PING * 2016-06-06 15:05 GMT-06:00 Alessandro Fanfarillo : > Dear all, > > please find in attachment the first patch (of n) for the FAILED IMAGES > capability defined in the coarray TS 18508. > The patch adds support for three new intrinsic functions defined in > the TS

Re: Deprecating basic asm in a function - What now?

On 21/06/16 17:43, Jeff Law wrote: > I think there's enough resistance to deprecating basic asms within a > function that we should probably punt that idea. > > I do think we should look to stomp out our own uses of basic asms > within functions just from a long term maintenance standpoint. > >

Re: RFC: pass to warn on questionable uses of alloca().

On 06/21/2016 10:00 AM, Jakub Jelinek wrote: On Tue, Jun 21, 2016 at 09:57:59AM -0600, Jeff Law wrote: Would a new attribute to annotate async-signal safe functions help? I envision that the attribute on a function definition would turn off the alloca/VLA to malloc transformation, and could

[Bug middle-end/66867] Suboptimal code generation for atomic_compare_exchange

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66867 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #7

Re: Deprecating basic asm in a function - What now?

On 06/21/2016 10:33 AM, Andrew Haley wrote: Hi, On 21/06/16 13:08, Michael Matz wrote: On Tue, 21 Jun 2016, Andrew Haley wrote: As said in the various threads about basic asms, all correctness problems can be solved by making GCC more conservative in handling them (or better said: not

[Committed][testsuite] Ensure vrnd* tests run on ARMv8 cores

The recently added gcc.target/aarch64/advsimd-intrinsics/vrnd*.c tests cause failures due to accidentally running on non-ARMv8 hardware - the target check arm_v8_neon_ok is correct for compilation tests but should be arm_v8_neon_hw for execution tests. Fix this and also change arm_v8_neon_hw to

Re: [PATCH][AArch64] Add initial support for Cortex-A73

On Tue, Jun 21, 2016 at 04:55:43PM +0100, Kyrill Tkachov wrote: > Hi all, > > This is a rebase of https://gcc.gnu.org/ml/gcc-patches/2016-06/msg00403.html > on top of Evandro's changes. > Also, to elaborate on the original posting, the initial tuning structure is > based on the Cortex-A57 one but

[Committed][testsuite] Fix tree-ssa/attr-hotcold-2.c failures

Fix tree-ssa/attr-hotcold-2.c failures now that the test runs. GCC dumps the blocks 3 times so update count to 3 and the test passes. ChangeLog: 2016-06-21  Wilco Dijkstra      gcc/testsuite/     * gcc.dg/tree-ssa/attr-hotcold-2.c (scan-tree-dump-times):     Set to 3 so test

Re: Deprecating basic asm in a function - What now?

Hi, On 21/06/16 13:08, Michael Matz wrote: > On Tue, 21 Jun 2016, Andrew Haley wrote: > >>> As said in the various threads about basic asms, all correctness >>> problems can be solved by making GCC more conservative in handling >>> them (or better said: not making it less conservative). >> >>

[Bug tree-optimization/71609] [7 regression] test case gfortran.dg/vect/vect-8.f90 fails starting with r237549

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71609 --- Comment #1 from amker at gcc dot gnu.org --- Should be fixed by https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01501.html ? Thanks, bin

Re: [patch, avr,wwwdocs] PR 58655

Pitchumani Sivanupandi schrieb: Attached patches add documentation for -mfract-convert-truncate option and add that info to release notes (gcc-4.9 changes). If OK, could someone commit please? I do not have commit access. Regards, Pitchumani gcc/ChangeLog 2016-06-21 Pitchumani Sivanupandi

[PATCH] [OBVIOUS] s/imposisble/impossible in predict.c

Hello. I've just installed patch that does $SUBJECT. Thanks, Martin >From 8302396974053dd00cd5eaff594dddf2f1ccf80b Mon Sep 17 00:00:00 2001 From: marxin Date: Tue, 21 Jun 2016 18:05:50 +0200 Subject: [PATCH] s/imposisble/impossible in predict.c gcc/ChangeLog: 2016-06-21

Re: RFC: pass to warn on questionable uses of alloca().

On Tue, Jun 21, 2016 at 09:57:59AM -0600, Jeff Law wrote: > >Would a new attribute to annotate async-signal safe functions > >help? I envision that the attribute on a function definition > >would turn off the alloca/VLA to malloc transformation, and > >could also diagnose calls to other function

[RFC: Patch 4/6 v2] Modify cost model for noce_cmove_arith

Hi, This patch clears up the cost model for noce_try_cmove_arith. We lose the "??? FIXME: Magic number 5" comment, and gain a more realistic cost model for if-converting memory accesses. This is the patch that has the chance to cause the largest behavioural changes for most targets - the

[Bug tree-optimization/71609] New: [7 regression] test case gfortran.dg/vect/vect-8.f90 fails starting with r237549

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71609 Bug ID: 71609 Summary: [7 regression] test case gfortran.dg/vect/vect-8.f90 fails starting with r237549 Product: gcc Version: 7.0 Status: UNCONFIRMED Severity:

Re: RFC: pass to warn on questionable uses of alloca().

On 06/21/2016 09:51 AM, Martin Sebor wrote: On 06/20/2016 03:41 PM, Jeff Law wrote: On 06/20/2016 08:56 AM, Joseph Myers wrote: On Sat, 18 Jun 2016, Martin Sebor wrote: the function regardless of the value of its argument). At the same time, it seems that an even more reliable solution than

[RFC: Patch 2/6 v2] Factor out the comparisons against magic numbers in ifcvt

Hi, This patch pulls the comparisons between if_info->branch_cost and a magic number representing an instruction count to a common function. While I'm doing it, I've documented the instructions that the magic numbers relate to, and updated them where they were inconsistent. If our measure of

Re: [PATCH][AArch64] Add initial support for Cortex-A73

Hi all, This is a rebase of https://gcc.gnu.org/ml/gcc-patches/2016-06/msg00403.html on top of Evandro's changes. Also, to elaborate on the original posting, the initial tuning structure is based on the Cortex-A57 one but with the issue rate set to 2, FMA steering turned off and ADRP+LDR fusion

[RFC: Patch 6/6 v2] Remove second cost model from noce_try_store_flag_mask

Hi, This transformation tries two cost models, one estimating the number of insns to use, one estimating the RTX cost of the transformed sequence. This is inconsistent with the other cost models used in ifcvt.c and unneccesary - eliminate the second cost model. Thanks, James --- 2016-06-21

[RFC: Patch 5/6 v2] Improve the cost model for multiple-sets

Hi, This patch is rewrites the cost model for bb_ok_for_noce_multiple_sets to use the max_seq_cost heuristic added in earlier patch revisions. As with the previous patch, I've used the new parameters to ensure that the testsuite is still testing the functionality rather than relying on the

Re: RFC: pass to warn on questionable uses of alloca().

On 06/20/2016 03:41 PM, Jeff Law wrote: On 06/20/2016 08:56 AM, Joseph Myers wrote: On Sat, 18 Jun 2016, Martin Sebor wrote: the function regardless of the value of its argument). At the same time, it seems that an even more reliable solution than pointing out potentially unsafe calls to the

[RFC: Patch 3/6 v2] Remove if_info->branch_cost

Hi, This patch removes what is left of branch_cost uses, moving them to use the new hook and tagging each left over spot with a TODO to revisit them. All these uses are in rtx costs units, so we don't have more work to do at this point. Bootstrapped as part of the patch series on aarch64 and

  1   2   >