public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: Anastasia3412 <Anastasia3412@proton.me>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	"hubicka@ucw.cz" <hubicka@ucw.cz>
Subject: Re: [GSOC] query about C++: Implement compiler built-in traits for the standard library traits
Date: Fri, 31 Mar 2023 13:53:46 +0200	[thread overview]
Message-ID: <ri6zg7t2l2t.fsf@suse.cz> (raw)
In-Reply-To: <7-jHkZ14MPEOhbnN7r1xYQAtayqu1PEFEjXvYSPMAFiOmnpzt7FPtBxYMc-qI0QhQUuG6OrzUMZt9H6l-lLo58QVdfiFg3_p5ly17Sf0XPI=@proton.me>

Hello,

my apologies for a very late reply, unfortunately we have had an
unpleasant hiccup in our internal miscommunication.

On Thu, Mar 23 2023, Anastasia3412 wrote:
> Thanks, Martin and Jonathan for your suggestion. I have already finished building gcc from source. I was looking at other project ideas and found "Enable incremental Link Time Optimization (LTO) linking" interesting. Can anyone please explain how to proceed further with this? Currently, I am watching videos posted in the getting started section.
>
> ------- Original Message -------
> On Wednesday, March 22nd, 2023 at 5:04 AM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
>
>> On Tue, 21 Mar 2023 at 21:16, Martin Jambor wrote:
>> 
>> > Hello Anastasia,
>> > 
>> > we are very happy that you are considering contributing to GCC.
>> > 
>> > On Mon, Mar 20 2023, Anastasia3412 via Gcc wrote:
>> > 
>> > > Hello Everyone I'm Anastasia.
>> > > 
>> > > I am a prospective GSOC Student. I wish to know if the project C++:
>> > > Implement compiler built-in traits for the standard library traits is
>> > > still available. I have already build and got my hand dirty on
>> > > debugging GCC.
>> > 
>> > Various prospective contributors have shown interest in it but we have
>> > not "promised" it to anyone, I don't think we can, so it is "available."
>> > It has been discussed for example here:
>> > https://gcc.gnu.org/pipermail/gcc/2023-February/240816.html
>
>> We already have two candidates working on it, before their proposal
>> has even been accepted. As a result, I think you'd have to be a very
>> strong candidate to get accepted for that project, and it might be
>> better to pick another one.

after talking to Honza I unfortunately became aware that that project
also already has a student who has also advanced quite far.

At the moment I can only suggest to look at the project proposal to
"Bypass assembler when generating LTO object files," because even though
a few people were interested in it, nobody had applied for it yet and as
far as I know nobody has even really attempted a serious proposal.  The
task is discussed here:

https://gcc.gnu.org/pipermail/gcc/2023-March/240833.html

I know that our late reply made writing a proposal difficult.  But in
order to succeed, it should be enough to show that you have basic
understanding of what needs to be done at the technical level and have
basic understanding of the source code you would need to touch (lto
streaming code and simple-object.c in libiberty).  This project also
would require rather little understanding of compiler theory because it
is mostly about shoveling around data in more efficient form but it
requires some knowledge of the ELF format.

Apologies again for the delay, please feel free to ask any specific
question about the code here or on our IRC channel.

Martin

      reply	other threads:[~2023-03-31 11:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 19:14 Anastasia3412
2023-03-21 21:15 ` Martin Jambor
2023-03-21 23:34   ` Jonathan Wakely
2023-03-23  5:47     ` Anastasia3412
2023-03-31 11:53       ` Martin Jambor [this message]

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=ri6zg7t2l2t.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=Anastasia3412@proton.me \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jwakely.gcc@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).