On 19 September 2017 at 01:35, Martin Sebor wrote:
> On 09/18/2017 01:06 PM, Prasad Ghangal wrote:
>>
>> Hi,
>>
>> This was discussed a few time ago in this email thread :
>> https://gcc.gnu.org/ml/gcc/2016-02/msg00235.html
>>
>> As per the discussion
Hi,
This was discussed a few time ago in this email thread :
https://gcc.gnu.org/ml/gcc/2016-02/msg00235.html
As per the discussion, the attached patch produces warning message for
excess elements in array initialization along with number of expected
and extra elements and underlined extra elemen
On 16 August 2016 at 14:10, Richard Biener wrote:
> On Mon, Aug 15, 2016 at 8:59 PM, Prasad Ghangal
> wrote:
>> On 11 August 2016 at 15:58, Richard Biener
>> wrote:
>>> On Thu, Aug 11, 2016 at 7:47 AM, Prasad Ghangal
>>> wrote:
>>>> In this
On 11 August 2016 at 15:58, Richard Biener wrote:
> On Thu, Aug 11, 2016 at 7:47 AM, Prasad Ghangal
> wrote:
>> In this patch I am trying to parse gimple call. But I am getting weird
>> gimple dump for that.
>>
>> for this testcase:
>> int __GIMPLE() bar()
, cgraph_uid=1,
symbol_order=1)*/
void
foo ()
{
int b;
bb_2:
b_3 = bar ();
return;
}
On 9 August 2016 at 14:37, Richard Biener wrote:
> On Sun, Aug 7, 2016 at 3:19 PM, Prasad Ghangal
> wrote:
>> On 4 August 2016 at 18:29, Richard Biener wrote:
>>> On Thu, Aug 4, 20
On 4 August 2016 at 18:29, Richard Biener wrote:
> On Thu, Aug 4, 2016 at 1:31 PM, Prasad Ghangal
> wrote:
>> On 2 August 2016 at 14:29, Richard Biener wrote:
>>> On Mon, Aug 1, 2016 at 4:52 PM, Prasad Ghangal
>>> wrote:
>>>> Hi,
>>>>
On 2 August 2016 at 14:29, Richard Biener wrote:
> On Mon, Aug 1, 2016 at 4:52 PM, Prasad Ghangal
> wrote:
>> Hi,
>>
>> I am trying to replace c_parser_paren_condition (parser) in
>> c_parser_gimple_if_stmt by c_parser_gimple_paren_condition (parser) as
>&g
Hi,
I am trying to replace c_parser_paren_condition (parser) in
c_parser_gimple_if_stmt by c_parser_gimple_paren_condition (parser) as
described in the patch
I am trying test case
void __GIMPLE () foo ()
{
int a;
bb_2:
if (a == 2)
goto bb_3;
else
goto bb_4;
bb_3:
a_2 = 4;
bb_4:
Thanks,
Prasad
On 29 July 2016 at 12:55, Richard Biener wrote:
> On Fri, Jul 29, 2016 at 9:03 AM, Prasad Ghangal
> wrote:
>> Thanks,
>> Prasad
>>
>>
>> On 29 July 2016 at 06:56, Prathamesh Kulkarni
>> wrote:
>>> On 29 July 2016 at 00:01, P
Thanks,
Prasad
On 29 July 2016 at 06:56, Prathamesh Kulkarni
wrote:
> On 29 July 2016 at 00:01, Prasad Ghangal wrote:
>> On 27 July 2016 at 14:22, Richard Biener wrote:
>>> On Tue, Jul 26, 2016 at 11:38 PM, Prathamesh Kulkarni
>>> wrote:
>>>> On 27 Ju
On 27 July 2016 at 14:22, Richard Biener wrote:
> On Tue, Jul 26, 2016 at 11:38 PM, Prathamesh Kulkarni
> wrote:
>> On 27 July 2016 at 00:20, Prasad Ghangal wrote:
>>> On 20 July 2016 at 18:28, Richard Biener wrote:
>>>> On Wed, Jul 20, 2016 at 1:46 PM
On 20 July 2016 at 18:28, Richard Biener wrote:
> On Wed, Jul 20, 2016 at 1:46 PM, Prathamesh Kulkarni
> wrote:
>> On 20 July 2016 at 11:34, Richard Biener wrote:
>>> On Tue, Jul 19, 2016 at 10:09 PM, Prasad Ghangal
>>> wrote:
>>>> On 19 July
On 19 July 2016 at 11:04, Richard Biener wrote:
> On July 18, 2016 11:05:58 PM GMT+02:00, David Malcolm
> wrote:
>>On Tue, 2016-07-19 at 00:52 +0530, Prasad Ghangal wrote:
>>> On 19 July 2016 at 00:25, Richard Biener
>>> wrote:
>>> > On July 18,
On 19 July 2016 at 00:25, Richard Biener wrote:
> On July 18, 2016 8:28:15 PM GMT+02:00, Prasad Ghangal
> wrote:
>>On 15 July 2016 at 16:13, Richard Biener
>>wrote:
>>> On Sun, Jul 10, 2016 at 6:13 PM, Prasad Ghangal
>>> wrote:
>>>> On 8 July
On 15 July 2016 at 16:13, Richard Biener wrote:
> On Sun, Jul 10, 2016 at 6:13 PM, Prasad Ghangal
> wrote:
>> On 8 July 2016 at 13:13, Richard Biener wrote:
>>> On Thu, Jul 7, 2016 at 9:45 PM, Prasad Ghangal
>>> wrote:
>>>> On 6 July 2016 at 14:24,
On 8 July 2016 at 13:13, Richard Biener wrote:
> On Thu, Jul 7, 2016 at 9:45 PM, Prasad Ghangal
> wrote:
>> On 6 July 2016 at 14:24, Richard Biener wrote:
>>> On Wed, Jul 6, 2016 at 9:51 AM, Prasad Ghangal
>>> wrote:
>>>> On 30 June 2016 at 17:10,
On 6 July 2016 at 14:24, Richard Biener wrote:
> On Wed, Jul 6, 2016 at 9:51 AM, Prasad Ghangal
> wrote:
>> On 30 June 2016 at 17:10, Richard Biener wrote:
>>> On Wed, Jun 29, 2016 at 9:13 PM, Prasad Ghangal
>>> wrote:
>>>> On 29 June 2016 at 22:15,
On 30 June 2016 at 17:10, Richard Biener wrote:
> On Wed, Jun 29, 2016 at 9:13 PM, Prasad Ghangal
> wrote:
>> On 29 June 2016 at 22:15, Richard Biener wrote:
>>> On June 29, 2016 6:20:29 PM GMT+02:00, Prathamesh Kulkarni
>>> wrote:
>>>>On 18 Jun
On 4 July 2016 at 15:17, Richard Biener wrote:
> On Sun, Jul 3, 2016 at 9:34 AM, Prasad Ghangal
> wrote:
>> In this patch, I am passing labels and vars with internal function and
>> handling them in tree-cfg for parsing PHI.
>> For first label, label_to_block() gives c
a;
int a_2;
int a_3;
int a_1;
bb_2:
a_2 = 3;
goto bb_4;
bb_3:
a_3 = 6;
goto bb_4;
bb_4:
a_1 = __PHI (bb_2: a_2, bb_3: a_3);
a_1 = a_1 + 1;
return;
}
On 1 July 2016 at 17:33, Richard Biener wrote:
> On Fri, Jul 1, 2016 at 1:57 PM, Prasad Ghangal
> wrote:
>>
On 29 June 2016 at 12:42, Richard Biener wrote:
> On Tue, Jun 28, 2016 at 4:16 PM, Prasad Ghangal
> wrote:
>> Hi,
>>
>> For handling PHI, it expects cfg to be built before. So I was
>> wondering how are we going to handle this? Do we need to build cfg
>> while
On 29 June 2016 at 22:15, Richard Biener wrote:
> On June 29, 2016 6:20:29 PM GMT+02:00, Prathamesh Kulkarni
> wrote:
>>On 18 June 2016 at 12:02, Prasad Ghangal
>>wrote:
>>> Hi,
>>>
>>> I tried hacking pass manager to execute only given passes. Fo
Hi,
For handling PHI, it expects cfg to be built before. So I was
wondering how are we going to handle this? Do we need to build cfg
while parsing only?
Thanks,
Prasad
On 27 June 2016 at 14:16, Richard Biener wrote:
> On Sun, Jun 26, 2016 at 5:55 PM, Prasad Ghangal
> wrote:
>> Hi Richard,
>>
>> For the first stage of the project, I have completed the following things -
>> parsed -- assign-statement, labeled-statement, if-statem
ll act as a entry point to the pipeline and will execute passes
starting from given pass.
Thanks,
Prasad Ghangal
diff --git a/gcc/c-family/c-common.c b/gcc/c-family/c-common.c
index 4568cf6..f2e62ca 100644
--- a/gcc/c-family/c-common.c
+++ b/gcc/c-family/c-common.c
@@ -511,6 +511,7 @@
Hi,
This patch parses simple assignment statement
int a;
void __GIMPLE foo()
{
a = 1;
}
but it does not produce gimple dump. In debugging I found that
cfun->gimple_body is not NULL and it contains GIMPLE_ASSIGN statement.
Am I missing something ?
Thanks,
Prasad Ghangal
On 31 May 2016
On 1 June 2016 at 15:19, Richard Biener wrote:
> On Wed, Jun 1, 2016 at 9:19 AM, Prathamesh Kulkarni
> wrote:
>> On 30 May 2016 at 20:45, Prasad Ghangal wrote:
>>> Hi,
>>>
>>> As David suggested in his rtlfe patch,
>>> this p
en_is_not (parser, CPP_CLOSE_BRACE))
+{
+c_parser_consume_token (parser);
+}
+
+ c_parser_consume_token (parser);
+}
+
#include "gt-c-c-parser.h"
GIMPLE function body consists of GIMPLE statements. For parsing GIMPLE
function body, we need to populate gimple body with gimple statements
which will emit GIMPLE as it is.
I would like to hear suggestions about how can I emit GIMPLE directly from FE.
Thanks,
Prasad Ghangal
On 7 May 2016 at 16:37, Richard Biener wrote:
> On May 6, 2016 3:14:03 PM GMT+02:00, Prasad Ghangal
> wrote:
>>On 6 May 2016 at 16:09, Richard Biener
>>wrote:
>>> On Wed, May 4, 2016 at 4:29 PM, Prasad Ghangal
>> wrote:
>>>> On 4 May 2016 at 15:54,
Hi,
I am selected for Google Summer of Code 2016 under GNU-GCC
organization. In order to start working on the project, I need to file
copyright assignment.
So I would like to receive required forms for the same.
Thanks,
Prasad Ghangal
On 6 May 2016 at 16:09, Richard Biener wrote:
> On Wed, May 4, 2016 at 4:29 PM, Prasad Ghangal
> wrote:
>> On 4 May 2016 at 15:54, Richard Biener wrote:
>>> On Wed, May 4, 2016 at 11:46 AM, Prasad Ghangal
>>> wrote:
>>>> On 4 May 2016 at 13:02, Richar
On 4 May 2016 at 15:54, Richard Biener wrote:
> On Wed, May 4, 2016 at 11:46 AM, Prasad Ghangal
> wrote:
>> On 4 May 2016 at 13:02, Richard Biener wrote:
>>> On Wed, May 4, 2016 at 8:41 AM, Prasad Ghangal
>>> wrote:
>>>> Hi !
>>>> Curr
On 4 May 2016 at 13:02, Richard Biener wrote:
> On Wed, May 4, 2016 at 8:41 AM, Prasad Ghangal
> wrote:
>> Hi !
>> Currently I am trying to introduce new command line option -fgimple,
>> for that I am adding this to c.opt
>>
>> diff --git a/gcc/c-family
which will parse gimple body.
For pass manager, basic idea is to introduce new member to struct
function as pass_list and modify function execute_pass_list to run
only passes in pass list.
Thanks,
Prasad Ghangal
Hi all !
Sorry this is little late reply. Accepted projects for GSoC are
announced. gcc has accepted 3 proposals this year. I want to thank gcc
community for accepting proposal for GIMPLE FE project. I will give my
best to complete the project.
Thanks,
Prasad Ghangal
Hi!
Regarding PR64955, I was observing function format_type_warning() (in
c-family/c-format.c), how can I get format specifier for arg_type?
Say, if tree arg_type stores 'char', then how can I get its format i.e. 'c' ?
Thanks,
Prasad Ghangal
On 5 March 2016 at 01:06, David Malcolm wrote:
> On Wed, 2016-02-24 at 17:56 +0530, Prasad Ghangal wrote:
>> Thanks Prathamesh and Joseph for your suggestions.
>>
>> Here is my updated patch :
>>
>> for test cases:
>>
>> const int array[5] = {1, 2,
Thanks everyone for suggestions,
Here is my updated proposal. I know its too late but can somebody review it?
https://drive.google.com/file/d/0B2S9OoautWxsbVBkWDY3VDNkdGc/view?usp=sharing
On 25 March 2016 at 08:46, Prathamesh Kulkarni
wrote:
> On 25 March 2016 at 01:15, Prasad Ghangal wr
On 24 March 2016 at 19:01, Richard Biener wrote:
> On Thu, Mar 24, 2016 at 12:27 AM, Prasad Ghangal
> wrote:
>> Hi!
>>
>> I have attached my gsoc proposal, please review it. Let me know if I
>> have missed or misunderstood anything
>
> Please re-word the Abst
Hi!
Here is the link my gsoc proposal, please review it. Let me know if I
have missed or misunderstood anything
https://drive.google.com/file/d/0B2S9OoautWxsbVBkWDY3VDNkdGc/view
Thanks and Regards,
Prasad Ghangal
On 22 March 2016 at 19:23, Richard Biener wrote:
> On Tue, Mar 22, 2016 a
at 04:43:35AM +0530, Prasad Ghangal wrote:
>> Hi!
>>
>> Sorry for the late reply.
>>
>> I was observing gimple dumps and my initial findings are, to parse
>> gimple, we have to add support for following components to C FE
>>
>> *basic blocks
>
think -fgimple would only enable recognizing the __GIMPLE keyword,
> I wouldn't change all defs to GIMPLE with it.
>
> Richard.
>
>> Thanks,
>> Prathamesh
>>>
>>> In private discussion we somewhat agreed (Micha - correct me ;)) that
>>> iff the GIMPLE FE would replace the C FE function body parsing
>>> completely (re-using name lookup infrastructure of course) and iff the
>>> GIMPLE FE would emit GIMPLE directly (just NULL DECL_SAVED_TREE
>>> and a GIMPLE seq in DECL_STRUCT_FUNCTION->gimple_body)
>>> then "re-using" the C FE would be a way to greatly speed up success.
>>>
>>> The other half of the project would then be to change the pass manager
>>> to do something sensible with the produced GIMPLE as well as making
>>> our dumps parseable by the GIMPLE FE.
>>>
>>> Richard.
--
Thanks and Regards,
Prasad Ghangal
gimple (we will have
to modify CFG, PHI nodes accordingly)
2. Do we have to develop new grammar for gimple-C ?
--
Thanks and Regards,
Prasad Ghangal
of the project for gsoc so
that I can start preparing for proposal.
>
> Richard.
>
--
Thanks and Regards,
Prasad Ghangal
Hi!
On stackoverflow
http://stackoverflow.com/questions/21660563/can-gcc-compile-gimple,
they said GIMPLE FE project is dead. Please let me know if I can work
on it for gsoc.
On 5 March 2016 at 03:01, Prasad Ghangal wrote:
> Hi!
>
> I am interested to work on Gimple FE project for
Hi!
I am interested to work on Gimple FE project for gsoc16. I would like
to know the scope of the project for gsoc. Also anyone like to mentor
me for the project?
Thanks and Regards,
Prasad Ghangal
ven there.
>
> In particular, see
> http://lists.gnu.org/archive/html/summer-of-code/2016-03/msg8.html
>
>
--
Thanks and Regards,
Prasad Ghangal
PING
I would like to know if there is other better way of doing this.
On 24 February 2016 at 17:56, Prasad Ghangal wrote:
> Thanks Prathamesh and Joseph for your suggestions.
>
> Here is my updated patch :
>
> for test cases:
>
> const int array[5] = {1, 2, 3};
>
, 193;
^
68425.c:14:1: error: expected declaration or statement at end of input
}
^
Any suggestions?
--
Thanks and Regards,
Prasad Ghangal
Index: gcc/c/c-parser.c
t those locations are not saved in all trees). In fact, I see that
> there is already a lot of location passing in the corresponding code,
> but probably all of them refer to input_location or some such.
>
> Cheers,
>
> Manuel.
--
Thanks and Regards,
Prasad Ghangal
= { 1, 2, 3 ,6 ,89 ,193};
^
--
Thanks and Regards,
Prasad Ghangal
Hi !
I am trying to fix bug 38612
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38612).
As mentioned in comment 4, I am changing warning message in
typeck2.c. TREE_TYPE(datum) gives type as 'X', but I want 'X*' also
how to add notes as suggested in the comment ?
--
Thanks
,
Prasad Ghangal
ntainers may even have different opinions.
I agree with Manuel (and his comments on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17896) that we should
follow clang here and show fix-it hint "& will evaluate the boolean
expression to its right, did you mean '&&'?". That will be more clear
message than "suggest && instead of & when joining booleans".
So I am asking community for their suggestion.
--
Thanks and Regards,
Prasad Ghangal
Hi!
I would like to solve "Bug 17896 - The expression (a>0 & b>0) should
give clearer warning message (-Wparentheses)"
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17896) but I am new to
gcc internals.
Can someone please guide me how to do it?
--
Thanks and Regards,
Prasad Ghangal
On 01/09/2016 06:10 PM, Prasad Ghangal wrote:
>> Hi,
>> I am Prasad Ghangal, a BTech student and I really want to contribute
>> in gcc, but I am new to open source community.
>> I can code in C,C++ and know little python. I have successfully built
>> gcc on my local
Hi,
I am Prasad Ghangal, a BTech student and I really want to contribute
in gcc, but I am new to open source community.
I can code in C,C++ and know little python. I have successfully built
gcc on my local machine as instructed.
So can someone please help me getting started?
--
Thanks,
Prasad
57 matches
Mail list logo
