From: "ANKESH PANDEY ." <f20200104@hyderabad.bits-pilani.ac.in>
To: gcc@gcc.gnu.org
Subject: GSoC 2023
Date: Sun, 19 Mar 2023 11:31:05 +0530 [thread overview]
Message-ID: <CAJxTYoVSUMtuHBYxxjAdi7aViSRSFh+EKrnHWLFXDor8yjHteg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2756 bytes --]
Hello,
I am Ankesh Pandey, a 3rd year Computer Science Undergraduate.
I am interested in contributing for the following projects:
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*
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.
Hoping to contribute to the organization through GSoC 2023.
Thank you.
--
The information contained in this electronic communication is intended
solely for the individual(s) or entity to which it is addressed. It may
contain proprietary, confidential and/or legally privileged information.
Any review, retransmission, dissemination, printing, copying or other use
of, or taking any action in reliance on the contents of this information by
person(s) or entities other than the intended recipient is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us by responding to this email or telephone and
immediately and permanently delete all copies of this message and any
attachments from your system(s). The contents of this message do not
necessarily represent the views or policies of BITS Pilani.
next reply other threads:[~2023-03-19 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 6:01 ANKESH PANDEY . [this message]
2023-03-21 20:40 ` Martin Jambor
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=CAJxTYoVSUMtuHBYxxjAdi7aViSRSFh+EKrnHWLFXDor8yjHteg@mail.gmail.com \
--to=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).