Reminder !!!
~Umesh
On Wed, Jul 18, 2018 at 6:01 PM, Umesh Kalappa wrote:
> Hi Nagy/Ramana,
>
> Please help us to review the attached patch and do let me know your comments .
>
> No regress in the gcc.target suite for arm target.
>
> Thank you
> ~Umesh
>
> O
Thank you all for your comments .
Wilco,
We tried some of the normalisation numbers and the fix works and please
could you help us with the input ,where if you see that fix breaks down.
Thank you again
~Umesh
On Fri, Jul 20, 2018, 7:07 PM Wilco Dijkstra wrote:
> Hi Umesh,
>
> Looking at your
Umesh Kalappa
+
+ PR libgcc/86512
+ * config/arm/ieee754-df.S :Don't normalise the denormal result.
+ * config/arm/ieee754-sf.S:Likewise.
+
+
+++ gcc/testsuite/ChangeLog (working copy)
@@ -1,3 +1,8 @@
+2018-07-18 Umesh Kalappa
+
+ PR libgcc/86512
+ * gcc.target/arm
Dijkstra wrote:
> Umesh Kalappa wrote:
>
>> We tried some of the normalisation numbers and the fix works and please
>> could you help us with the input ,where if you see that fix breaks down.
>
> Well try any set of inputs which require normalisation. You'll find these no
ns.
>
> R.
>
> On 23/07/18 08:46, Umesh Kalappa wrote:
>> Thank you Wilco for the inputs and we agree that the fix break down
>> for the case.
>>
>> Meanwhile ,attached patch will take care the inputs and we are testing
>> the patch vigorously ,would you r
Hi,
Any more suggestions or comments on the patch ?
Thank you
~Umesh
On Tue, Jul 24, 2018, 2:08 PM Umesh Kalappa
wrote:
> Thank you All for the suggestions and we tried runing the GCC
> testsuite and found that no regression with the fix and also ran the
> our regress
Hi Nagy/Ramana,
Please help us to review the attached patch and do let me know your comments .
No regress in the gcc.target suite for arm target.
Thank you
~Umesh
On Tue, Jul 17, 2018 at 4:01 PM, Umesh Kalappa wrote:
> Will do, thanks.
> Thanks
>
> On Tue, Jul 17, 2018, 3:
Hi All,
the following patch fix the subjected issue
Index: gcc/cp/parser.c
===
--- gcc/cp/parser.c (revision 266026)
+++ gcc/cp/parser.c (working copy)
@@ -24615,6 +24615,8 @@
{
tree expr;
Thank you Richard,
Made the required changes ,ok to commit ?
Thank you
~Umesh
On Thu, Nov 15, 2018 at 4:02 PM Richard Biener
wrote:
>
> On Thu, Nov 15, 2018 at 10:02 AM Umesh Kalappa
> wrote:
> >
> > Hi All,
> >
> > The attached patch (pr85667.patch) fixes th
Thank you Marek,Appreciate your valuable feedback on the patch .
Attached the latest ,please do let us know your thoughts.
~Umesh
On Thu, Nov 15, 2018 at 9:26 PM Marek Polacek wrote:
>
> On Thu, Nov 15, 2018 at 02:26:24PM +0530, Umesh Kalappa wrote:
> > Thank you Marek fo
My bad ,
attached the same now .
~Umesh
On Fri, Nov 16, 2018 at 2:38 PM Richard Biener
wrote:
>
> On Fri, Nov 16, 2018 at 9:07 AM Umesh Kalappa
> wrote:
> >
> > Thank you Richard,
> >
> > Made the required changes ,ok to commit ?
>
> Can you attach th
l let know for any regressions .
Meanwhile ,Please let us know your thoughts on the patch.
Thank you
~Umesh
On Wed, Nov 14, 2018 at 2:55 AM Jason Merrill wrote:
>
> On Tue, Nov 13, 2018 at 10:40 AM Marek Polacek wrote:
> > On Tue, Nov 13, 2018 at 11:49:55AM +0530, Umesh Kalap
Hi All,
The attached patch (pr85667.patch) fixes the subjected issue .
we tested on x86_64(linux and windows both) and no regress found .
ok to commit ?
Thank you
~Umesh
pr85667.patch
Description: Binary data
wrote:
>
> On Wed, Nov 14, 2018 at 09:55:39PM +0530, Umesh Kalappa wrote:
> > My bad Marek and thank you for pointing that out.
> >
> > Please find the attached correct one (pr52869.patch) .
>
> Index: gcc/cp/ChangeLog
> ===
Edited the subjected for the proper PR no.
~Umesh
On Thu, Nov 15, 2018 at 2:32 PM Umesh Kalappa wrote:
>
> Hi All,
>
> The attached patch (pr85667.patch) fixes the subjected issue .
> we tested on x86_64(linux and windows both) and no regress found .
>
> ok to commit ?
>
> Thank you
> ~Umesh
My bad Marek and thank you for pointing that out.
Please find the attached correct one (pr52869.patch) .
~Umesh
pr52869.patch
Description: Binary data
>>We are runing the make check-gcc(x86_64) and will let know for any
>>regressions .
No regress found .
~Umesh
On Wed, Nov 14, 2018 at 5:18 PM Umesh Kalappa wrote:
>
> Thank you Jason and Marek for the suggestions .
>
> Attached patch(pr86512.patch) along the Changel
Thank you Segher, will work on your suggestions.
Umesh
On Tue, Dec 11, 2018, 19:23 Segher Boessenkool Hi Umesh,
>
> On Tue, Dec 11, 2018 at 05:30:48PM +0530, Umesh Kalappa wrote:
> > Please find the attached patch for the subjected issue .
> >
> > Do please l
Thank you Jakub for the information.
Will make a note of it.
Umesh
On Tue, Dec 11, 2018, 17:58 Jakub Jelinek On Tue, Dec 11, 2018 at 05:30:48PM +0530, Umesh Kalappa wrote:
> > Hi All,
> >
> > Please find the attached patch for the subjected issue .
> >
> > Do pl
Hi All,
Please find the attached patch for the subjected issue .
Do please let me know your thoughts and comments on the same .
Thank you
~Umesh
pr84762.patch
Description: Binary data
you
~Umesh
On Fri, Nov 23, 2018 at 3:56 PM Umesh Kalappa wrote:
>
> Hi Richard,
>
> for the subjected issue , we found few suggestions to handle the issue like
>
> 1. be more conservative(target specific) and defining the peephole in
> the md file to handle the patterns like a
; On Fri, Nov 16, 2018 at 4:57 PM Jakub Jelinek wrote:
>>
>> On Fri, Nov 16, 2018 at 04:21:25PM +0530, Umesh Kalappa wrote:
>> > My bad ,
>> > attached the same now .
>>
>> +2018-11-15 Lokesh Janghel
>>
>> Two spaces before < instea
Hi Jakub and All,
We don't have the commit access ,can someone please commit for us ?
~Umesh
On Wed, Nov 21, 2018, 18:37 Jakub Jelinek On Wed, Nov 21, 2018 at 06:06:41PM +0530, Umesh Kalappa wrote:
> > Thank you for the inputs and please find the attachment for the update
> patch.
Thank you for the inputs and please find the attachment for the update patch.
Do please let us know your comments on the same
~Umesh
On Tue, Nov 20, 2018 at 3:03 PM Jakub Jelinek wrote:
On Mon, Nov 19, 2018 at 04:08:29PM +0530, Lokesh Janghel wrote:
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
>>Before getting started with reviewing the patch , the first question
is whether you have a copyright assignment on file or does your
employer have one on record with the FSF ?
Ramana, We asked for copyright assignment form ,with details asked by
copyright-cl...@fsf.org(craig)
@ ass...@gnu.org.
25 matches
Mail list logo
