This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GSoC Project Ideas
- From: P J P <pjp at fedoraproject dot org>
- To: Patrick Palka <ppalka007 at gmail dot com>, Gcc Mailing List <gcc at gcc dot gnu dot org>
- Date: Mon, 4 Mar 2019 10:56:51 +0000 (UTC)
- Subject: Re: GSoC Project Ideas
- References: <CAKheXZ8sgp1YmQ=vCLBuBCB4iVAAaQVemyiW2AEgYLAL5OO9xw@mail.gmail.com>
- Reply-to: P J P <pj dot pandit at yahoo dot co dot in>
On Monday, 4 March, 2019, 4:37:07 AM IST, Patrick Palka <ppalka007@gmail.com> wrote:
>I am very interested in working on GCC as part of GSoC this year.
>A few years ago I was a somewhat active code contributor[1] and
>unfortunately my contributing waned once I went back to school,
>but I'm excited to potentially have the opportunity to work on GCC again this summer.
>
> * Extend VRP to track unions of intervals
> (inspired by comment #2 of PR72443 [2])
>
> * Make TREE_NO_WARNING more fine-grained
> (inspired by comment #7 of PR74762 [3])
>
> * Make -Wmaybe-uninitialized more robust
> (Inspired by the recent thread to move -Wmaybe-uninitialized to -Wextra [4])
>
> * Bug fixing in the C++ frontend / general C++ frontend improvements
> There are 100s of open PRs about the C++ frontend, and the goal here
> would just be to resolve as many as one can over the summer.
Interesting!
>Would any of these ideas work as a GSoC project?
-> https://gcc.gnu.org/ml/gcc/2019-03/msg00016.html
-> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87210
Could this RFE be considered for a GSoC project?
Thank you.
---
-P J P
http://feedmug.com