From: Martin Jambor <mjambor@suse.cz>
To: Kristiyan Stoimenov <kristoimenov@gmail.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>, David Malcolm <dmalcolm@redhat.com>
Subject: Re: GSoC: Interest in taking the `-ftime-trace` project
Date: Wed, 01 Mar 2023 19:57:24 +0100 [thread overview]
Message-ID: <ri6a60w8fl7.fsf@suse.cz> (raw)
In-Reply-To: <CAEU1ye1wNbYGCkgBoAe4CKfAsiqDKJaJv-FoEFPF31mF8yEX3g@mail.gmail.com>
Hello Kristiyan,
On Wed, Feb 08 2023, 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.
In case you have not noticed, there was a message to this mailing list a
week ago ( https://gcc.gnu.org/pipermail/gcc/2023-February/240756.html )
about a basic implementation of this in a plug-in located at
https://github.com/royjacobson/externis
This may help you with thinking about the task and writing your
proposal. Of course, the resulting project would have to be not a
plugin and aim to give users more insight into the compilation process
to be successful. But it may be a useful starting point.
Apart from that, all David's advice was of course very good (but
meanwhile we got accepted as a mentoring Org).
Good luck!
Martin
next prev parent reply other threads:[~2023-03-01 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 8:57 Kristiyan Stoimenov
2023-02-09 14:18 ` David Malcolm
2023-03-01 18:57 ` Martin Jambor [this message]
[not found] ` <CAEU1ye29N41sHJpQvcMvDnXXHHgXQRC=tcofOsh5LC4p+vUQJg@mail.gmail.com>
2023-03-17 13:55 ` Martin Jambor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ri6a60w8fl7.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kristoimenov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).