Hi Community,
We are 1 week away from midterm evaluations of students' work. Mentors, please
start looking closely into your student's progress and draft up evaluation
notes.
Midterm evaluations are very important in GSoC. Students who fail this
evaluation are immediately kicked out of the p
On Mon, 2014-06-16 at 14:42 -0400, Vladimir Makarov wrote:
> On 2014-06-16, 2:25 PM, Aaron Sawdey wrote:
> > On Mon, 2014-06-16 at 14:14 +, Ajit Kumar Agarwal wrote:
> >> Hello All:
> >>
> >> I have worked on the Open64 compiler where the Register Pressure Guided
> >> Unroll and Jam gave a goo
On 2014-06-16, 2:25 PM, Aaron Sawdey wrote:
On Mon, 2014-06-16 at 14:14 +, Ajit Kumar Agarwal wrote:
Hello All:
I have worked on the Open64 compiler where the Register Pressure Guided Unroll
and Jam gave a good amount of performance improvement for the C and C++ Spec
Benchmark and also F
On 2014-06-16, 10:14 AM, Ajit Kumar Agarwal wrote:
Hello All:
I have worked on the Open64 compiler where the Register Pressure Guided Unroll
and Jam gave a good amount of performance improvement for the C and C++ Spec
Benchmark and also Fortran benchmarks.
The Unroll and Jam increases the re
On Mon, 2014-06-16 at 14:14 +, Ajit Kumar Agarwal wrote:
> Hello All:
>
> I have worked on the Open64 compiler where the Register Pressure Guided
> Unroll and Jam gave a good amount of performance improvement for the C and
> C++ Spec Benchmark and also Fortran benchmarks.
>
> The Unroll a
On June 16, 2014 6:39:58 PM CEST, Ajit Kumar Agarwal
wrote:
>
>
>-Original Message-
>From: Richard Biener [mailto:richard.guent...@gmail.com]
>Sent: Monday, June 16, 2014 7:55 PM
>To: Ajit Kumar Agarwal
>Cc: gcc@gcc.gnu.org; Vladimir Makarov; Michael Eager; Vinod Kathail;
>Shail Aditya G
-Original Message-
From: Richard Biener [mailto:richard.guent...@gmail.com]
Sent: Monday, June 16, 2014 7:55 PM
To: Ajit Kumar Agarwal
Cc: gcc@gcc.gnu.org; Vladimir Makarov; Michael Eager; Vinod Kathail; Shail
Aditya Gupta; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: Register Pre
On Mon, Jun 16, 2014 at 12:52:10PM +0200, Andreas Schwab wrote:
> Dan Carpenter writes:
> > Adding "--param allow-store-data-races=0" to the GCC options for the
> > kernel breaks C=1 because Sparse isn't expecting a GCC option with that
> > format.
> Please try --param=allow-store-data-races=0 i
On Mon, Jun 16, 2014 at 4:14 PM, Ajit Kumar Agarwal
wrote:
> Hello All:
>
> I have worked on the Open64 compiler where the Register Pressure Guided
> Unroll and Jam gave a good amount of performance improvement for the C and
> C++ Spec Benchmark and also Fortran benchmarks.
>
> The Unroll and J
Hi,
On Mon, 16 Jun 2014, Richard Biener wrote:
> For
>
> (match_and_simplify
> (MINUS_EXPR @2 (PLUS_EXPR@2 @0 @1))
> @1)
Btw, this just triggered my eye. So with lumping the predicate to the
capture without special separator syntax, it means that there's a
difference between "minus_expr
Hello All:
I have worked on the Open64 compiler where the Register Pressure Guided Unroll
and Jam gave a good amount of performance improvement for the C and C++ Spec
Benchmark and also Fortran benchmarks.
The Unroll and Jam increases the register pressure in the Unrolled Loop leading
to inc
Hello All:
There has been work done for load rematerialization. Instead of Store and Load
of variables they kept in registers for the Live range. Till now we are doing
the rematerialization of scalar loads.
Is it feasible to have rematerialization for the vector Loads? This will be
helpful
On Mon, 16 Jun 2014, Andreas Schwab wrote:
> > Adding "--param allow-store-data-races=0" to the GCC options for the
> > kernel breaks C=1 because Sparse isn't expecting a GCC option with that
> > format.
>
> Please try --param=allow-store-data-races=0 instead.
How reliable is this format across
On Mon, Jun 16, 2014 at 1:07 AM, Prathamesh Kulkarni
wrote:
> On Sat, Jun 14, 2014 at 12:43 PM, Richard Biener
> wrote:
> I have attached patch that tries to implement decision tree using the
> above algorithm.
> (haven't done for built-in function yet, but that would be similar to
> expr, so i g
Dan Carpenter writes:
> Adding "--param allow-store-data-races=0" to the GCC options for the
> kernel breaks C=1 because Sparse isn't expecting a GCC option with that
> format.
Please try --param=allow-store-data-races=0 instead.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key f
Adding "--param allow-store-data-races=0" to the GCC options for the
kernel breaks C=1 because Sparse isn't expecting a GCC option with that
format.
It thinks allow-store-data-races=0 is the name of the file we are trying
to test. Try use Sparse on linux-next to see the problem.
$ make C=2 mm/sl
On Thu, Jun 12, 2014 at 7:59 PM, Zdenek Dvorak wrote:
> Hi,
>
>> > I noticed there is below code/comments about may_be_zero field in loop
>> > niter desc:
>> >
>> > tree may_be_zero;/* The boolean expression. If it evaluates to true,
>> >the loop will exit in the first itera
17 matches
Mail list logo
