Re: [PATCH] Prevent LTO wrappers to process a recursive execution

On 04/25/2016 09:49 AM, Martin Liška wrote: Hello. To make LTO wrappers (gcc-nm, gcc-ar, gcc-ranlib) more smart, I would like to prevent execution of the same binary by these wrapper. For LTO testing I symlink ar (nm, ranlib) to these wrappers instead of hacking a build system to respect NM

Re: [PATCH v2] Allocate constant size dynamic stack space in the prologue

On 05/06/2016 03:44 AM, Dominik Vogt wrote: diff --git a/gcc/cfgexpand.c b/gcc/cfgexpand.c index 21f21c9..4d48afd 100644 --- a/gcc/cfgexpand.c +++ b/gcc/cfgexpand.c ... @@ -1099,8 +1101,10 @@ expand_stack_vars (bool (*pred) (size_t), struct stack_vars_data *data) /* If there were any,

Re: [PATCH v2] Allocate constant size dynamic stack space in the prologue

On 05/06/2016 03:37 AM, Dominik Vogt wrote: Updated version of the patch described below. Apart from fixing a bug and adding a test, the new logic is now used always, for all targets. The discussion of the original patch starts here: https://gcc.gnu.org/ml/gcc-patches/2015-11/msg03052.html

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

On 05/25/2016 07:32 AM, Dominik Vogt wrote: On Wed, May 25, 2016 at 02:30:54PM +0100, Dominik Vogt wrote: > On Tue, May 03, 2016 at 03:17:53PM +0100, Dominik Vogt wrote: > > Version two of the patch including a test case. > > > > On Mon, May 02, 2016 at 09:10:25AM -0600, Jeff Law wrote: > > >

[PATCH] Fix source locations of bad enum values (PR c/71610 and PR c/71613)

PR c/71613 identifies a problem where we fail to report this enum: enum { e1 = LLONG_MIN }; with -pedantic, due to LLONG_MIN being inside a system header. This patch updates the C and C++ frontends to use the location of the name as the primary location in the diagnostic, supplying the

Re: [PATCH, rs6000] Add minimum __float128 built-in support required for glibc

> On Jun 22, 2016, at 6:27 PM, Joseph Myers wrote: > > On Wed, 22 Jun 2016, Bill Schmidt wrote: > >> Hi Joseph, >> >> That's indeed preferable for the long term -- given how close we are to the >> cutoff for 6.2, though, I'm worried about adding any new dependencies

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

On Wed, Jun 22, 2016 at 05:29:59PM -0400, Michael Meissner wrote: > This code should fix the problem. It does not allow constants in the > arguments. Combine will create one of the vec_duplicate patterns with a > constant integer that will generate VSPLTIS or XXSPLTIB/etc. I also > tightened

Re: [PATCH, rs6000] Add minimum __float128 built-in support required for glibc

On Wed, 22 Jun 2016, Bill Schmidt wrote: > Hi Joseph, > > That's indeed preferable for the long term -- given how close we are to the > cutoff for 6.2, though, I'm worried about adding any new dependencies for > getting this upstream. I'd suggest that we go ahead with reviewing this > patch

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

On Tue, Jun 21, 2016 at 9:51 PM, H.J. Lu wrote: >> I have attached my version of the patch. It handles all your >> testcases, plus +1 case. Bootstrap is still running. >> >> Does the patch work for you? > > It works. Attached version of the patch was committed to mainline

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

> Fortran note: the float128_type_node used in the Fortran front end is > renamed to gfc_float128_type_node, since the semantics are different: > in particular, if long double has binary128 format, then the new > language-independent float128_type_node is a distinct type that also > has binary128

Re: [PATCH 1/3] Add gcc-auto-profile script

On Wed, Jun 22, 2016 at 11:34:05PM +0200, Bernhard Reutner-Fischer wrote: > >+for m in mod[:-1]: > >+print "model*:\ %s|\\" % m > >+print 'model*:\ %s) E="%s$FLAGS" ;;' % (mod[-1], event) > >+print '''*) > >+echo >&2 "Unknown CPU. Run contrib/gen_autofdo_event.py

Re: [PATCH 1/3] Add gcc-auto-profile script

On June 22, 2016 2:37:04 PM GMT+02:00, Andi Kleen wrote: >From: Andi Kleen > >Using autofdo is currently something difficult. It requires using the >model specific branches taken event, which differs on different CPUs. >The example shown in the manual

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

On Wed, Jun 22, 2016 at 09:22:22AM -0500, Segher Boessenkool wrote: > Don't give up so easily? ;-) > > The predicate should be tightened, the expander should use a new predicate > that allows all those other things. The hardest part is figuring a good > name for it ;-) This code should fix the

Re: [PING**2] [PATCH] Fix asm X constraint (PR inline-asm/59155)

On 06/22/16 21:51, Jeff Law wrote: > On 06/19/2016 07:25 AM, Bernd Edlinger wrote: >> Hi, >> >> ping... >> >> As this discussion did not make any progress, I just attached >> the latest version of my patch with the the changes that >> Vladimir proposed. >> >> Boot-strapped and reg-tested again on

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

Here is patch version 2, updated to apply without conflicts to current trunk (there was a conflict with r237714 moving cases over RID_* around) but with no other changes. (In particular, with no further changes to the PowerPC choice of mode - in this patch it matches what __float128 already

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

On 05/25/2016 07:30 AM, Dominik Vogt wrote: On Tue, May 03, 2016 at 03:17:53PM +0100, Dominik Vogt wrote: > Version two of the patch including a test case. > > On Mon, May 02, 2016 at 09:10:25AM -0600, Jeff Law wrote: > > On 04/29/2016 04:12 PM, Dominik Vogt wrote: > > >The attached patch

Re: [PATCH, rs6000] Add minimum __float128 built-in support required for glibc

Hi Joseph, That's indeed preferable for the long term -- given how close we are to the cutoff for 6.2, though, I'm worried about adding any new dependencies for getting this upstream. I'd suggest that we go ahead with reviewing this patch in the short term, and I'll be happy to work with you

Re: [PATCH, rs6000] Add minimum __float128 built-in support required for glibc

On Wed, 22 Jun 2016, Bill Schmidt wrote: > Bootstrapped and tested on powerpc64le-unknown-linux-gnu with no > regressions. All new tests pass except for the test for vspltish in > the infinity test; this relies on a patch in progress to fix things so we > generate that instead of an inferior

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

On 06/22/16 20:49, Jeff Law wrote: > On 06/21/2016 11:12 PM, Bernd Edlinger wrote: > >> >> What I wanted to say here, is that lra goes thru several iterations, >> changes something in the register allocation that has an impact on the >> frame layout, typically 4-5 times, and calls

Re: Fix for PR70926 in Libiberty Demangler (5)

On 05/26/2016 01:02 AM, Marcel Böhme wrote: 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

[PATCH, rs6000] Add minimum __float128 built-in support required for glibc

Hi, This patch implements built-ins to support __float128 on 64-bit PowerPC. This is a minimum set of built-ins required for use by glibc. The following six built-ins are supported: __builtin_absf128 __builtin_copysignf128 __builtin_huge_valf128 __builtin_inff128 __builtin_nanf128

Debug algorithms

Hi Here is eventually the so long promized patch to introduce Debug algos similarly to Debug containers. Why such an evolution: - More flexibility, debug algos can be used explicitely without activating Debug mode. - Performance: Debug algos can get rid of Debug layer on top of

Re: [PING**2] [PATCH] Fix asm X constraint (PR inline-asm/59155)

On 06/19/2016 07:25 AM, Bernd Edlinger wrote: Hi, ping... As this discussion did not make any progress, I just attached the latest version of my patch with the the changes that Vladimir proposed. Boot-strapped and reg-tested again on x86_64-linux-gnu. Is it OK for the trunk? Well, I don't

Re: [PATCH, rs6000] Scheduling update

Hi Pat, On Tue, Jun 21, 2016 at 12:45:26PM -0500, Pat Haugen wrote: > 2016-06-21 Pat Haugen > > * config/rs6000/power8.md (power8-fp): Include dfp type. > * config/rs6000/power6.md (power6-fp): Likewise. Please put the files in the changelog in some

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

On 06/21/2016 11:12 PM, Bernd Edlinger wrote: What I wanted to say here, is that lra goes thru several iterations, changes something in the register allocation that has an impact on the frame layout, typically 4-5 times, and calls INITIAL_ELIMINATION_OFFSET 3-4 times in a row, and in the

[PATCH, i386]: Simplify SYMBOL_REF handling in ix86_expand_move

Hello! This patch de-duplicates code involving SYMBOL_REF processing in ix86_expand_move. No functional changes. 2016-06-22 Uros Bizjak * config/i386/i386.c (ix86_expand_move): Simplify SYMBOL_REF handling. Bootstrapped and regression tested on x86_64-linux-gnu

Re: [PATCH 3/8] nvptx -muniform-simt

Ping. On Mon, 13 Jun 2016, Alexander Monakov wrote: > On Sun, 12 Jun 2016, Sandra Loosemore wrote: > > On 06/09/2016 10:53 AM, Alexander Monakov wrote: > > > +@item -muniform-simt > > > +@opindex muniform-simt > > > +Generate code that allows to keep all lanes in each warp active, even > > >

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

On 06/22/2016 01:20 AM, Bernd Edlinger wrote: On 06/21/16 23:29, Jeff Law wrote: How does this macro interact with INITIAL_FRAME_POINTER_OFFSET? That I forgot to mention: INITIAL_FRAME_POINTER_OFFSET is just a single call, so whenever it is called from lra/reload the frame layout is really

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

On Wed, Jun 15, 2016 at 11:01:05AM +0200, Richard Biener wrote: > And I don't understand the layout_type change either - it looks to me > it could just have used > > SET_TYPE_MODE (type, GET_MODE_COMPLEX_MODE (TYPE_MODE > (TREE_TYPE (type; > > and be done with it. To me that looks a lot

Re: [Patch, avr] Fix PR 71151

Senthil Kumar Selvaraj schrieb: Senthil Kumar Selvaraj writes: Georg-Johann Lay writes: Senthil Kumar Selvaraj schrieb: Hi, [set JUMP_TABLES_IN_TEXT_SECTION to 1] I added tests that use linker relaxation and discovered a relaxation bug in binutils 2.26 (and later) that messes up symbol

Re: [patch] preserve DECL_ORIGINAL_TYPE invariant in remap_decl

On 06/22/2016 03:12 AM, Eric Botcazou wrote: Hi, the invariant is that DECL_ORIGINAL_TYPE (t) != TREE_TYPE (t) as pointer value if t is a TYPE_DECL. It's enforced by the DWARF back-end: if (DECL_ORIGINAL_TYPE (decl)) { type = DECL_ORIGINAL_TYPE (decl); if

Re: [PATCH 3/3] Add make autoprofiledbootstrap

On Wed, Jun 22, 2016 at 11:51:17AM -0600, Jeff Law wrote: > On 06/22/2016 06:37 AM, Andi Kleen wrote: > >From: Andi Kleen > > > >Add support for profiledbootstrap with autofdo. Will be useful > >to get better testing coverage of autofdo. > > > >This requires Linux perf and

Re: [patch,testsuite,avr]: Support dg-require-effective-target avr_3byte_pc (and use it with PR71151 tests).

On 06/22/2016 11:44 AM, Georg-Johann Lay wrote: Jeff Law schrieb: On 06/22/2016 08:21 AM, Georg-Johann Lay wrote: Some tests for PR71151 assume that the target MCU has a 3-byte PC. The tests are failing because the simulator (avrtest) rejects to load the respective executables if .text

Re: [PATCH 1/3] Add gcc-auto-profile script

On 06/22/2016 11:44 AM, Andi Kleen wrote: 2016-06-22 Andi Kleen * config/i386/gcc-auto-profile: New file. contrib/: 2016-06-22 Andi Kleen * gen_autofdo_event.py: New file to regenerate gcc-auto-profile. This part

Re: [PATCH 3/3] Add make autoprofiledbootstrap

On 06/22/2016 06:37 AM, Andi Kleen wrote: From: Andi Kleen Add support for profiledbootstrap with autofdo. Will be useful to get better testing coverage of autofdo. This requires Linux perf and autofdo to be installed, only really for x86_64 linux on Intel so far. I

Re: [patch,testsuite,avr]: Support dg-require-effective-target avr_3byte_pc (and use it with PR71151 tests).

Jeff Law schrieb: On 06/22/2016 08:21 AM, Georg-Johann Lay wrote: Some tests for PR71151 assume that the target MCU has a 3-byte PC. The tests are failing because the simulator (avrtest) rejects to load the respective executables if .text exceeds 128KiB, e.g. for -mmcu=atmega128 which has only

Re: [PATCH 1/3] Add gcc-auto-profile script

> > 2016-06-22 Andi Kleen > > > > * config/i386/gcc-auto-profile: New file. > > > > contrib/: > > > > 2016-06-22 Andi Kleen > > > > * gen_autofdo_event.py: New file to regenerate > > gcc-auto-profile. > This part looks fine to me

Re: [PATCH, vec-tails 05/10] Check if loop can be masked

On 06/22/2016 10:09 AM, Ilya Enkovich wrote: Given the common structure & duplication I can't help but wonder if a single function should be used for widening/narrowing. Ultimately can't you swap mask_elems/req_elems and always go narrower to wider (using a different optab for the two

Re: [PATCH 2/3] Run profile feedback tests with autofdo

On 06/22/2016 06:37 AM, Andi Kleen wrote: From: Andi Kleen Extend the existing bprob and tree-prof tests to also run with autofdo. The test runtimes are really a bit too short for autofdo, but it's a reasonable sanity check. This only works natively for now. dejagnu

Re: [PATCH 1/3] Add gcc-auto-profile script

On 06/22/2016 06:37 AM, Andi Kleen wrote: From: Andi Kleen Using autofdo is currently something difficult. It requires using the model specific branches taken event, which differs on different CPUs. The example shown in the manual requires a special patched version of

Re: [PATCH, vec-tails 05/10] Check if loop can be masked

On 06/22/2016 09:03 AM, Ilya Enkovich wrote: 2016-06-16 9:26 GMT+03:00 Jeff Law : On 06/15/2016 05:22 AM, Richard Biener wrote: You look at TREE_TYPE of LOOP_VINFO_NITERS (loop_vinfo) - I don't think this is meaningful (if then only by accident). I think you should look at

Re: [patch,testsuite,avr]: Support dg-require-effective-target avr_3byte_pc (and use it with PR71151 tests).

On Jun 22, 2016, at 10:06 AM, Mike Stump wrote: > Please see target-utils.exp and ensure that the tools generate a stylized > message and then add support for that to target-utils.exp. Also, see return "::unsupported::memory full" in gcc-dg.exp, there is a copy there as

Re: [patch,testsuite,avr]: Support dg-require-effective-target avr_3byte_pc (and use it with PR71151 tests).

On Jun 22, 2016, at 7:21 AM, Georg-Johann Lay wrote: > > Some tests for PR71151 assume that the target MCU has a 3-byte PC. The tests > are failing because the simulator (avrtest) rejects to load the respective > executables if .text exceeds 128KiB, e.g. for -mmcu=atmega128

Re: [patch,testsuite,avr]: Support dg-require-effective-target avr_3byte_pc (and use it with PR71151 tests).

On 06/22/2016 08:21 AM, Georg-Johann Lay wrote: Some tests for PR71151 assume that the target MCU has a 3-byte PC. The tests are failing because the simulator (avrtest) rejects to load the respective executables if .text exceeds 128KiB, e.g. for -mmcu=atmega128 which has only flash of 128KiB

Re: [PATCH 1/7] SMS remove dependence on doloop: Use loop induction variable analysis in SMS pass

On 05/05/2016 12:01 AM, Shiva Chen wrote: Hi, SMS transformation would change the kernel loop iteration count. To do this, SMS pass will find the register contain loop count and generate the instructions to adjust loop count. Currently, SMS will try to find count_reg by recognizing doloop_end

Re: [PATCH] Change minimum of -predicted-iterations to 1 (PR71619)

On 06/22/2016 04:59 PM, Martin Liška wrote: > Hello. > > Following patch just changes minimum value to 1. I think having minimum to > zero > does not make any good sense. > > Running reg on x86_64-linux-gnu, ready after it finishes? > > Thanks, > Martin > As mentioned in PR48189, zero value

Re: [PATCH, vec-tails 05/10] Check if loop can be masked

2016-06-16 10:08 GMT+03:00 Jeff Law : > On 05/19/2016 01:42 PM, Ilya Enkovich wrote: >> >> Hi, >> >> This patch introduces analysis to determine if loop can be masked >> (compute LOOP_VINFO_CAN_BE_MASKED and LOOP_VINFO_REQUIRED_MASKS) >> and compute how much masking costs. >> >>

[ARM][testsuite] neon-testgen.ml removal

Hi, This is a new attempt at removing neon-testgen.ml and generated files. Compared to my previous version several months ago: - I have recently added testcases to make sure we do not lose coverage as described in https://gcc.gnu.org/ml/gcc-patches/2015-11/msg02922.html - I now also remove

[committed] libcpp: Tweak to missing #include source location

This patch tweaks the error message location for missing header files. Previously these read: test.c:1:17: fatal error: 404.h: No such file or directory #include "404.h" ^ compilation terminated. With this patch, the pertinent string is underlined: test.c:1:10: fatal error:

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

Hi Jeff, > I can buy that ;-) OK with a suitable ChangeLog entry. Thanks! Checked in with this changelog entry. Cheers Nick gcc/ChangeLog 2016-06-22 Nick Clifton * dwarf2out.c (scompare_loc_descriptor): Use SCALAR_INT_MODE_P() in place of

Re: [PATCH, vec-tails 05/10] Check if loop can be masked

2016-06-16 9:26 GMT+03:00 Jeff Law : > On 06/15/2016 05:22 AM, Richard Biener wrote: >> >> >> You look at TREE_TYPE of LOOP_VINFO_NITERS (loop_vinfo) - I don't think >> this is meaningful (if then only by accident). I think you should look at >> the >> control IV itself, possibly

[PATCH] Change minimum of -predicted-iterations to 1 (PR71619)

Hello. Following patch just changes minimum value to 1. I think having minimum to zero does not make any good sense. Running reg on x86_64-linux-gnu, ready after it finishes? Thanks, Martin >From c677c2bdc0f011dbda013dd396431b3afcbc2ae9 Mon Sep 17 00:00:00 2001 From: marxin

Re: [patch] Fix problematic debug info for parameters at -O0

> Do you really need the memset in there to reproduce it? > Wouldn't asm volatile ("" : : "r" ([0]) : "memory"); > or something similar be enough? Or if you need to clear something, > clear much smaller part of the array? Probably only the 128 first bytes, will change that. -- Eric Botcazou

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

On Tue, Jun 21, 2016 at 06:46:57PM -0500, Bill Schmidt wrote: > >> When I did this, I ran into a problem with an existing test case. We end > >> up matching the *vsx_splat_v4si_internal pattern instead of falling back > >> to the altivec_vspltisw pattern. The constraints don't match for

[patch,testsuite,avr]: Support dg-require-effective-target avr_3byte_pc (and use it with PR71151 tests).

Some tests for PR71151 assume that the target MCU has a 3-byte PC. The tests are failing because the simulator (avrtest) rejects to load the respective executables if .text exceeds 128KiB, e.g. for -mmcu=atmega128 which has only flash of 128KiB and only a 2-byte PC. Hence the tests have to

Re: [PATCH, vec-tails 04/10] Add masking cost

On 16 Jun 00:16, Jeff Law wrote: > On 05/19/2016 01:40 PM, Ilya Enkovich wrote: > >Hi, > > > >This patch extends vectorizer cost model to include masking cost by > >adding new cost model locations and new target hook to compute > >masking cost. > > > >Thanks, > >Ilya > >-- > >gcc/ > > >

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

On 21 Jun 2016 21:10, Jeff Law wrote: > 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 ?

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

2016-06-21 23:57 GMT+03:00 Jeff Law : > 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

Re: [PATCH] Implement -fdiagnostics-parseable-fixits

On Jun 21, 2016, at 8:25 PM, David Malcolm wrote: > I implemented tests using both -fself-test and DejaGnu. > For the DejaGnu test coverage, I attempted to implement detection of the > output strings via existing directives, but after several hours of > failing, I instead

Re: [Patch AArch64] Use default_elf_asm_named_section instead of special cased hook

* config/aarch64/aarch64-protos.h (aarch64_elf_asm_named_section): Remove declaration. diff --git a/gcc/config/aarch64/aarch64-protos.h b/gcc/config/aarch64/aarch64-protos.h index e8c2ac8..3cdd69b 100644 --- a/gcc/config/aarch64/aarch64-protos.h +++

Re: [patch] Fix problematic debug info for parameters at -O0

On Wed, Jun 22, 2016 at 03:16:20PM +0200, Eric Botcazou wrote: > /* { dg-do run } */ > /* { dg-options "-g" } */ > /* { dg-skip-if "" { *-*-* } { "*" } { "-O0" } } */ > > typedef __UINTPTR_TYPE__ uintptr_t; > > typedef struct { uintptr_t pa; uintptr_t pb; } fatp_t > __attribute__ ((aligned (2

Re: [patch] Fix problematic debug info for parameters at -O0

> The testcase doesn't necessarily need to FAIL without the patch on x86, it > is fine if it fails on some PowerPC* or Visium. Here's what I have installed on mainline and 6 branch (not sure it's worth fixing on the aging 5 branch). The test fails on PowerPC/Linux: (gdb) b param-5.c:26

[PATCH 1/3] Add gcc-auto-profile script

From: Andi Kleen Using autofdo is currently something difficult. It requires using the model specific branches taken event, which differs on different CPUs. The example shown in the manual requires a special patched version of perf that is non standard, and also will likely

[PATCH 2/3] Run profile feedback tests with autofdo

From: Andi Kleen Extend the existing bprob and tree-prof tests to also run with autofdo. The test runtimes are really a bit too short for autofdo, but it's a reasonable sanity check. This only works natively for now. dejagnu doesn't seem to support a wrapper for unix

Re: [PATCH][AArch64][2/2] (Re)Implement vcopy_lane intrinsics

On 7 June 2016 at 17:56, Kyrill Tkachov wrote: > Ok for trunk? > > Thanks, > Kyrill > > 2016-06-07 Kyrylo Tkachov > James Greenhalgh > > * config/aarch64/arm_neon.h (vcopyq_lane_f32,

[Ada] Crash on config pragma Component_Alignment

Pragma Component_Alignment was not implemented properly and caused a crash when used in a configuration file due to how it was applied via the scope table. This patch correctly identifies this case and uses a global variable Configuration_Component_Alignment to capture the value set during

[Ada] Analysis of pragmas containing integer expressions not verified properly

If a string is used as an argument instead of an integer, Check_Arg_Is_OK_Static_Expression with Any_Integer will falsely verify causing the compiler to halt compilation when the caller acts on the assumption that it was verified. This patch creates checks so that Any_Integer works properly and

[Ada] Spurious error on derived type with unknown discriminants and predicate

This patch fixes a spurious error on an instantiation of an unbounded container, when the element type is a private type with unknown discriminants, derived from an array subtype with a predicate aspect. The following must ocmpile quietly: gcc -c gpr2-attribute.adb --- package GPR2 is

[Ada] Independent tasks and the Fall_Back_Handler

This patch fixes a bug in which if a Fall_Back_Handler is installed for the environment task, independent tasks will call it. The following test should run quietly: with Ada.Text_IO; package body Debug is protected body Dbg is procedure Termination (Cause : in

Re: [PATCH][AArch64][1/2] Add support INS (element) instruction to copy lanes between vectors

Ping. Richard, Marcus, do you have any feedback on this? https://gcc.gnu.org/ml/gcc-patches/2016-06/msg00502.html Thanks, Kyrill On 14/06/16 10:36, James Greenhalgh wrote: On Tue, Jun 07, 2016 at 05:56:47PM +0100, Kyrill Tkachov wrote: Hi all, This patch addresses an deficiency we have in

Re: [PATCH][AArch64][2/2] (Re)Implement vcopy_lane intrinsics

Ping. Richard, Marcus, do you have any feedback on this? https://gcc.gnu.org/ml/gcc-patches/2016-06/msg00503.html Thanks, Kyrill On 14/06/16 10:38, James Greenhalgh wrote: On Tue, Jun 07, 2016 at 05:56:51PM +0100, Kyrill Tkachov wrote: Hi all, This is the second part of James's patch from:

[Ada] Improve and unify warning machinery for address clauses

This change moves the rest of the warning machinery for address clauses to Validate_Address_Clauses, ensuring that all the variants are issued from it. This affects only absolute address clauses in practice, i.e. address clauses of the form for I'Address use To_Address (16#_#) and variants

[Ada] New implementation of Ada.Containers.Unbounded_Priority_Queues

This patch uses O(lg N) algorithms for Unbounded_Priority_Queues. No expected change in behavior; no test available. Tested on x86_64-pc-linux-gnu, committed on trunk 2016-06-22 Bob Duff * a-cuprqu.ads, a-cuprqu.adb: Completely rewrite this package. Use

[Ada] Crash on illegal expression in context with predicate

This patch fixes a compiler abort on a return statement for a function whose type is a derived type with a dynamic predicate, when the return expression has the parent type. Compiling gpr2-attribute.adb must yield: gpr2-attribute.adb:8:14: expected type "Qualified_Name" defined at

[Ada] New debug switch -gnatd.o

This patch causes -gnatd.o to choose a more conservative elaboration order. The following test should compile and run quietly. gnatmake -q -f -gnatd.o -g -O0 elab_indirect_2-main -bargs -p -ws with Elab_Indirect; with Elab_Indirect.Child; package body Elab_Indirect_2 is procedure P is

[Ada] Spurious error with predicate on type derived from unconstrained array

This patch fixes a spurious error on the compilation of a subprogram whose formal parameter is derived from an unconstrained array type with a dynamic predicate aspect. The following must compile quietly: gcc -c gpr2-attribute.adb gcc -c -gnata gpr2-attribute.adb --- package GPR2 is

[PATCH][ARM] Add support for some ARMv8-A cores to driver-arm.c

Hi all, This patch adds entries to the arm_cpu_table in driver-arm.c to enable it to perform native CPU detection on some aarch32 ARMv8-A systems. The cores added are Cortex-A32, Cortex-A35, Cortex-A53, Cortex-A57, Cortex-A72, Cortex-A73. Bootstrapped and tested on arm-none-linux-gnueabihf.

Re: [patch] Fix problematic debug info for parameters at -O0

> The testcase doesn't necessarily need to FAIL without the patch on x86, it > is fine if it fails on some PowerPC* or Visium. Well, the value of a guality test that isn't exercised on x86 is close to 0, but I can try on PowerPC indeed. -- Eric Botcazou

Re: [patch] Fix problematic debug info for parameters at -O0

On Wed, Jun 22, 2016 at 11:21:44AM +0200, Eric Botcazou wrote: > > Ok, even for branches I think, but would be nice to have a corresponding > > guality testcase (perhaps just for -O0 with dg-skip-if) which fails without > > this patch and succeeds with it. > > Thanks. The failure mode is that

Re: [patch] Fix problematic debug info for parameters at -O0

> Ok, even for branches I think, but would be nice to have a corresponding > guality testcase (perhaps just for -O0 with dg-skip-if) which fails without > this patch and succeeds with it. Thanks. The failure mode is that the offset from VIRTUAL_STACK_VARS_REGNUM is too large so, on RISC

Re: Unreviewed patches

Hi Jeff, > 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

[patch] preserve DECL_ORIGINAL_TYPE invariant in remap_decl

Hi, the invariant is that DECL_ORIGINAL_TYPE (t) != TREE_TYPE (t) as pointer value if t is a TYPE_DECL. It's enforced by the DWARF back-end: if (DECL_ORIGINAL_TYPE (decl)) { type = DECL_ORIGINAL_TYPE (decl); if (type == error_mark_node) return;

Re: [patch] Fix problematic debug info for parameters at -O0

On Wed, Jun 22, 2016 at 10:52:32AM +0200, Eric Botcazou wrote: > the fix for PR middle-end/61268: > https://gcc.gnu.org/viewcvs/gcc?view=revision=213002 > changed validize_mem to modify its argument in-place, which in turns means > that emit_move_insn can do it too. That's a little surprising,

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

On Tue, Jun 21, 2016 at 04:26:03PM -0600, Jeff Law wrote: > 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

[patch] Fix problematic debug info for parameters at -O0

Hi, the fix for PR middle-end/61268: https://gcc.gnu.org/viewcvs/gcc?view=revision=213002 changed validize_mem to modify its argument in-place, which in turns means that emit_move_insn can do it too. That's a little surprising, but I guess not really problematic in the end, except when the

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

On Wed, Jun 22, 2016 at 09:12:25AM +0100, Kyrill Tkachov wrote: > Hi James, > > On 21/06/16 17:38, James Greenhalgh wrote: > >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

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

Hi James, On 21/06/16 17:38, James Greenhalgh wrote: 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

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

On 06/21/16 23:29, Jeff Law wrote: > > How does this macro interact with INITIAL_FRAME_POINTER_OFFSET? That I forgot to mention: INITIAL_FRAME_POINTER_OFFSET is just a single call, so whenever it is called from lra/reload the frame layout is really expected to change, and so it does not make a

Re: [patch, avr,wwwdocs] PR 58655

On Tuesday 21 June 2016 09:39 PM, Georg-Johann Lay wrote: 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,

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

The whole idea of this patch is to disable those things in newlib, but they must synchronize this file with GCC. So if merging this into trunk will be all they need, then I have no need to merge this into release branches. 2016-06-21 22:08 GMT+02:00 Jeff Law : > On 06/15/2016

Re: [PATCH] Fix ICE with invalid use of flags output operand

Hello! > this fixes an ICE that happens when an asm statement tries to print > the flags output operand. > gcc: > 2016-06-11 Bernd Edlinger > > * config/i386/i386.c (print_reg): Emit an error message on attempt to > print FLAGS_REG. > > testsuite: > 2016-06-11

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

On Tue, Jun 21, 2016 at 08:55:15PM -0600, Jeff Law wrote: > user_defined_section_attribute was introduced as part of the hot/cold > partitioning changes. > > https://gcc.gnu.org/ml/gcc-patches/2004-07/msg01545.html > > > What's supposed to happen is hot/cold partitioning is supposed to be