David Malcolm a écrit:
> This patch adds a test plugin that recurses down an expression tree,
> printing diagnostics showing the ranges of each node in the tree.
>
> It corresponds to:
> [PATCH 15/22] Add plugin to recursively dump the source-ranges in a tree
> https://gcc.gnu.org/ml/gcc-pa
Hi Marcus,
Thanks for the review and comments.
>> OK and can you back port to 5 ?
Please find attached the backported patch on gcc-5-branch.
Regression tested on AArch64 without any issues.
2015-09-28 Andrew Pinski
ChangeLog
* config/aarch64/aarch64.md (prefetch):
Chan
-Original Message-
From: Bin.Cheng [mailto:amker.ch...@gmail.com]
Sent: Monday, September 28, 2015 7:05 AM
To: Ajit Kumar Agarwal
Cc: Segher Boessenkool; GCC Patches; Vinod Kathail; Shail Aditya Gupta;
Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: [Patch,optimization]: Optimized ch
On Sun, Sep 27, 2015 at 11:13 PM, Ajit Kumar Agarwal
wrote:
>
>
> -Original Message-
> From: Segher Boessenkool [mailto:seg...@kernel.crashing.org]
> Sent: Sunday, September 27, 2015 7:49 PM
> To: Ajit Kumar Agarwal
> Cc: GCC Patches; Vinod Kathail; Shail Aditya Gupta; Vidhumouli Hunsigida
From: hiraditya
Redesign Graphite scop detection for faster compiler time and detecting more
SCoPs.
Existing algorithm for SCoP detection in graphite was based on dominator tree
where a tree (CFG) traversal was required for analyzing an SESE. The tree
traversal is linear in the number of basic
On 09/27/2015 01:57 PM, Hans-Peter Nilsson wrote:
On Wed, 9 Sep 2015, Mike Stump wrote:
On Sep 8, 2015, at 9:41 PM, David Miller wrote:
+#define TARGET_LRA_P hook_bool_void_true
Are we at the point there this should be the default, and old
ports should just define to false, if they really n
On Wed, 9 Sep 2015, Mike Stump wrote:
> On Sep 8, 2015, at 9:41 PM, David Miller wrote:
> > +#define TARGET_LRA_P hook_bool_void_true
>
> Are we at the point there this should be the default, and old
> ports should just define to false, if they really need to?
I think no. For one, we don't have
On September 27, 2015 5:13:59 PM GMT+02:00, Ajit Kumar Agarwal
wrote:
>
>
>-Original Message-
>From: Segher Boessenkool [mailto:seg...@kernel.crashing.org]
>Sent: Sunday, September 27, 2015 7:49 PM
>To: Ajit Kumar Agarwal
>Cc: GCC Patches; Vinod Kathail; Shail Aditya Gupta; Vidhumouli
>H
On September 26, 2015 9:10:13 AM GMT+02:00, "Bin.Cheng"
wrote:
>On Sat, Sep 26, 2015 at 12:51 PM, Ajit Kumar Agarwal
> wrote:
>> SPEC CPU 2000 benchmarks are run and there is following impact on the
>performance
>> and code size.
>>
>> ratio with the optimization vs ratio without optimization fo
Hello!
Now that PR 57195 (Mode attributes with specific mode iterator can not
be used as mode iterators in *.md files) [1] is fixed, we can merge
*vec_extract_zext patterns.
2015-09-27 Uros Bizjak
* config/i386/predicates.md (register_sse4nonimm_operand): New
predicate.
* config/i
Hi!
> > OK for trunk?
Ok.
Jakub
> Hi!
> Ping.
OK for the Fortran part, though I suspect you need Jakub to approve it as well.
FX
-Original Message-
From: Segher Boessenkool [mailto:seg...@kernel.crashing.org]
Sent: Sunday, September 27, 2015 7:49 PM
To: Ajit Kumar Agarwal
Cc: GCC Patches; Vinod Kathail; Shail Aditya Gupta; Vidhumouli Hunsigida;
Nagaraju Mekala
Subject: Re: [Patch,optimization]: Optimized changes
Hi!
Ping.
On Fri, 14 Aug 2015 17:53:52 +0200, I wrote:
> On Fri, 14 Aug 2015 12:56:00 +0200, I wrote:
> > (Can a Fortran person please comment on this: as it's nontrivial to write
> > to stderr, let's just write to stdout followed by a flush, which does
> > have the same ordering effect -- OK?)
>
On Sat, Sep 26, 2015 at 04:51:20AM +, Ajit Kumar Agarwal wrote:
> SPEC CPU 2000 benchmarks are run and there is following impact on the
> performance
> and code size.
>
> ratio with the optimization vs ratio without optimization for INT benchmarks
> (3807.632 vs 3804.661)
>
> ratio with the
On Wed, 2015-09-23 at 21:04 +0900, Oleg Endo wrote:
> Hi,
>
> The attached patch fixes PR 67391. Some additional reg overlapping were
> added to the addsi3 patterns while making LRA on SH work, but not all of
> them seem to be good. Removing them, seems to be working just fine.
> Tested on sh-el
On 26/09/15 22:49 +0200, Florian Weimer wrote:
On 09/26/2015 09:52 PM, Jonathan Wakely wrote:
Would changes like this be suitable for _FORTIFY_SOURCE?
diff --git a/libstdc++-v3/include/std/mutex b/libstdc++-v3/include/std/mutex
index 5e5ced1..074bf26 100644
--- a/libstdc++-v3/include/std/mut
17 matches
Mail list logo