This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [GSOC] LTO dump tool project
- From: Martin Liška <mliska at suse dot cz>
- To: Hrishikesh Kulkarni <hrishikeshparag at gmail dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Cc: Jan Hubicka <jh at suse dot cz>, Richard Biener <richard dot guenther at gmail dot com>, Martin Jambor <mjambor at suse dot cz>
- Date: Tue, 29 May 2018 19:38:12 +0200
- Subject: Re: [GSOC] LTO dump tool project
- References: <CAL+0whRqd8c9ZTs9Q0OektMBYr6MhEDoKw+dtKt_JC8m3xjtBg@mail.gmail.com>
On 05/29/2018 07:03 PM, Hrishikesh Kulkarni wrote:
Hi,
My exams have finally ended and I have started working on the GSOC project.
I have forked GCC mirror (https://github.com/hrisearch/gcc) and
created a option for dumping functions and variables used in IL.
Please find the patch attached herewith.
Hello.
Good start. You branched the repository but your forget to push the commit
you sent as attachment. Second issues is that the patch is not against
GCC trunk, but against your local branch. Thus one can't apply that.
About the options:
- once you send a new functionality, it's fine to paste a sample output
- for now I would remove the dummy flag_lto_dump flag
- I would expect for -fdump-lto-list something like what nm does:
$ nm main.o
00000000 T main
00000000 T mystring
00000000 C pole
Then of course you can add some level of verbosity which can print what you have.
Would be also handy during the time to come up with some sorting, but it can wait.
That said, the direction is fine. Please carry on.
Thanks,
Martin
Regards,
Hrishikesh