Re: GSoC: Interest in taking the `-ftime-trace` project

[David Malcolm <dmalcolm@redhat.com>]

On Wed, 2023-02-08 at 10:57 +0200, Kristiyan Stoimenov via Gcc wrote:
> Hello,
> 
> I would like to ask whether I could be part of the upcoming GSoC. I
> have
> been wanting to contribute to the project for some time now and I
> think
> that this would be a nice opportunity for that.
> 
> I have looked into the different starter projects that are offered in
> the
> [Wiki GSoC page](https://gcc.gnu.org/wiki/SummerOfCode) and I was
> particularly interested in the `-ftime-trace` project. The following
> is
> what is given as a short description about the problematic:
> "Implement something similar to Clang's -ftime-trace feature which
> generates performance reports that show where the compiler spends
> compile
> time. For more information, please check the following blog post.
> There's
> also an existing bugzilla entry for this (if this becomes a GSoC
> project,
> the assignee will of course change). Required skills include C/C++
> and
> finding a way through a large code-base."
> 
> I am looking forward to your response.

Hi Kristiyan

Thanks for your interest in the project, and welcome!

I've been hoping someone would implement -ftime-trace, so I'm keen to
see this project go ahead.   I could potentially be a mentor for this
project (though I might be busy mentoring static analyzer projects, so
if anyone else wants to step forward, that would be good).

Note that Google hasn't yet formally announced which organizations will
be part of GSoC 2023, which happens on February 22nd:
  https://developers.google.com/open-source/gsoc/timeline

You might want to try building GCC from source and trying your hand at
hacking in a simple "hello world" print statement or similar.  See
e.g.:
  https://gcc-newbies-guide.readthedocs.io/en/latest/index.html
for a guide on getting started with that.

Hope this is helpful, and welcome again
Dave