From: Martin Jambor <mjambor@suse.cz>
To: "ANKESH PANDEY ." <f20200104@hyderabad.bits-pilani.ac.in>
Cc: gcc@gcc.gnu.org
Subject: Re: GSoC 2023
Date: Tue, 21 Mar 2023 21:40:52 +0100 [thread overview]
Message-ID: <ri6v8itvnvv.fsf@suse.cz> (raw)
In-Reply-To: <CAJxTYoVSUMtuHBYxxjAdi7aViSRSFh+EKrnHWLFXDor8yjHteg@mail.gmail.com>
Hello,
On Sun, Mar 19 2023, ANKESH PANDEY . wrote:
> Hello,
>
> I am Ankesh Pandey, a 3rd year Computer Science Undergraduate.
>
> I am interested in contributing for the following projects:
We are delighted you found contributing to GCC interesting.
>
> 1.
>
> Unicode support: Our Lexer and AST do not support Unicode strings and
> identifiers, which we need to be a Rust compiler. The project will require
> a student to work mostly in the Lexer and AST but the changes here will
> ripple all the way through our HIR and code-generation passes. For example,
> in implementing Unicode support, it will make sense to ensure we improve
> location info, so instead of simply passing around Unicode strings in the
> IR's we should create a unique string data structure which also contains
> location info to improve our error diagnostics and debug
> information. *Difficulty:
> Hard Size: 350 hours (large) Mentors: Arthur and/or Philip*
> 2.
>
> Improving user errors: We recently merged code enabling the Rust
> frontend to emit error codes similarly to rustc. We'd like for gccrs to be
> able to emit the same errors codes as rustc, in order to help bridge the
> gap between our two testsuites and enable us to eventually run the rustc
> one. The student will have to research rustc error codes, their various
> guarantees, and emit them throughout the frontend code. We would also like
> the code responsible for emitting errors to get more fleshed out and allow
> more functionality. Finally, this will also be a good project to start
> looking at a better user experience for gccrs: emitting more errors, in
> more places, with more hints to the users about ways to fix the
> code. *Difficulty:
> Medium Size: 175 (medium) Mentors: Arthur and/or Philip*
>
Please note that Rust-GCC projects are a bit special in the sense that
they are often discussed primarily on Zulip of the gcc-rust team:
https://gcc-rust.zulipchat.com/
So you may want to reach out to them there as well.
> I am really good at C, C++ and have decent experience working with FLEX and
> YACC and hence would be an appropriate candidate for the same.
>
> It would be great if you can give me insights on how I can formalize my
> proposal for GSoC 2023.
I assume you have already read through https://gcc.gnu.org/wiki/SummerOfCode
The page has guidelines on what we expect to find a proposal.
Feel free to ask about any specifics either here on the mailing list or
on the Zulip linked above.
Good luck!
Martin
next prev parent reply other threads:[~2023-03-21 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 6:01 ANKESH PANDEY .
2023-03-21 20:40 ` Martin Jambor [this message]
2023-03-27 13:05 Igor Putovny
2023-03-29 16:24 ` Martin Jambor
2023-03-27 23:26 Igor Putovny
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=ri6v8itvnvv.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=f20200104@hyderabad.bits-pilani.ac.in \
--cc=gcc@gcc.gnu.org \
/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).