From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by sourceware.org (Postfix) with ESMTPS id 4D3A43858D3C for ; Tue, 21 Mar 2023 20:40:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 4D3A43858D3C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=suse.cz Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 33DAB226CF; Tue, 21 Mar 2023 20:40:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1679431253; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=r+Gn9UdMH2REka35PvaAQBJWL3cF8Ldc8tKxWLxPjXA=; b=uLkQu3bb4K+rL9PvUD9m7WyPTfNcu79pjkQQbVGG7MVP2DmhRQFyYFzyL+IHnCRmNWhimX XPrOsrFA2Xmtp4xSq+/YdSzhiyacPC8ZeSykZSqmDqgJGZeQsahck0h1+jZ0gPqekP9Wzg LP03UrVt/AcZhTmDq+820G+JK66FEoc= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1679431253; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=r+Gn9UdMH2REka35PvaAQBJWL3cF8Ldc8tKxWLxPjXA=; b=3Gs8qchHiYcG7S3G/MOfhq3usa5Ij6ObBJaHnHizsQrTq9fjMGNRXPw/TGr2FTQfdikZYf F+KFmF8JHGNPKCAA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 1FAEF13451; Tue, 21 Mar 2023 20:40:53 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id mblEBlUWGmRRAgAAMHmgww (envelope-from ); Tue, 21 Mar 2023 20:40:53 +0000 From: Martin Jambor To: "ANKESH PANDEY ." Cc: gcc@gcc.gnu.org Subject: Re: GSoC 2023 In-Reply-To: References: User-Agent: Notmuch/0.37 (https://notmuchmail.org) Emacs/28.2 (x86_64-suse-linux-gnu) Date: Tue, 21 Mar 2023 21:40:52 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,SPF_HELO_NONE,SPF_SOFTFAIL,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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