Welcome GCC GSoC 2023 participants

2023-05-05 Thread Martin Jambor
Hello,

I am pleased to announce that again we will have six contributors
working on GCC as part of their Google Summer of Code (GSoC) projects
in 2023!  In no particular order:

- Benjamin Priour will be "Extending gcc -fanalyzer C++ support for
  self-analysis."  and the project will be mentored by David Malcolm.

- Eric Feng will be working on "Porting cpychecker to a -fanalyzer
  plugin" and his mentor will also be David Malcolm.

- Ken Matsui will look into C++ and in particular will "Implement
  compiler built-in traits for the standard library traits."  This
  project will be mentored by Patrick Palka.

- Muhammad Mahad will be "Improving user errors" in our new Rust
  front-end and will be mentored by Arthur Cohen and Philip Herron.

- Raiki Tamura has succeeded with a project to "Support Unicode in GCC
  Rust front-end" and the project will also be mentored by Arthur
  Cohen and Philip Herron.

- Rishi Raj will be workin on a project to "Bypass assembler when
  generating LTO object files" in that effort will be mentored by Jan
  Hubička and myself.

I'd like to congratulate all of them for putting together really solid
proposals and wish them best of luck with their projects.

The GSoC program has now entered its "community bonding period" which
lasts until May 28th.  During this time, contributors should get in
touch with their mentors unless you have already done so and probably
start looking quite a bit more at GCC in general.

In the initial discussion with your mentors, please take a while to
talk about the time-frame of your project.  If you are happy with the
standard 12 week duration (mid-term evaluation deadline on July 14th,
final deadline on August 28th) you do not need to do anything.  The
program can however also accommodate non-standard schedules, see the
options at:
https://developers.google.com/open-source/gsoc/help/project-dates

If you want to change the duration of your project, first please reach
an agreement with your mentor and then email me and/or other GSoC
Org-admins.  The change can be done at any point in the program but note
that it will not affect any evaluation which has already started.  (In
the case of the standard schedule this means that an Org-admin has to
enter the change before July 10 to affect the mid-term evaluation and
before August 21st to affect the final evaluation).

Because GCC targets many computer platforms, you may also find it very
useful to get an account on the compile farm so that you can test your
code on a variety of architectures.  For more details, see
https://gcc.gnu.org/wiki/CompileFarm

I'd also like to ask all six accepted contributors to take a few
minutes to familiarize themselves with the legal pre-requisites that
we have for contributing.  There are two options.  The much simpler
one is that copyright remains with you but you provide a "Developer
Certificate of Origin" for your contributions.  You can do that by
adding a "Signed-off-by:" tag to all your patches.  The second option
is to assign your copyright to the Free Software Foundation (if anyone
wants to do this, please let me know and I will help).  More
information about both is at:
https://gcc.gnu.org/contribute.html#legal

Last but not least, feel free to raise any question you may have on an
appropriate mailing list (https://gcc.gnu.org/lists.html) or say hi to
us on the gcc development IRC channel
(https://gcc.gnu.org/wiki/GCConIRC).

If you have any concerns or questions regarding the organizational part
of GSoC 2023 or just don't know who else to reach out to, feel free to
contact me throughout the duration of the program.

Once more, congratulations and good luck!

Martin


Re: Upcoming removal of legacy ranges and conversion to wide_ints.

2023-05-05 Thread Martin Jambor
Hi,

On Tue, Apr 25 2023, Aldy Hernandez via Gcc wrote:
> After GCC 13 is released we will remove legacy range support from the
> compiler, and convert irange's to wide_ints.  I want to give everyone
> a heads up, to help understand what's involved and what the end result is.
>

[...]

>
> 1. Converting users of the old API to the new irange API.
>

[...]

>
> The IPA passes also use the old API, but I have plans (and patches)
> for revamping all of the IPA ranges.  Details below.

Thanks a lot for taking care of this.

[..]

> IPA has been rolling their own ranges forever.  They use a combination
> of the legacy API along with handcrafted pairs of wide_ints (ipa_vr).
> The passes must be divorced of its legacy dependency, and cleaned up a
> bit.  IPA is also very tied to integers and pointers, and I see no
> reason why we can't keep track of float arguments, etc.

Agreed.

>
> I am sitting on a lot of additional patches to do 90% of the
> conversion, but need to consult with the IPA experts on various issues
> before proceeding (for instance, the lifetime of various structures).
> Among these patches are generic vrange LTO streaming functions and
> vrange hashing.  I think it's time we make vrange a first class
> citizen for LTO/hashing and a few other things folks were doing in an
> ad-hoc manner.  This should alleviate the maintenance burden on the
> IPA maintainers going forward.  Note, that the IPA work is a
> follow-up, and only after careful consultation with the relevant
> maintainers.

I need to get up to speed when it comes to the new representation and
new API but I'll be happy to help.

Martin


Fwd: Hosting our gfortran MatterMost workspace

2023-05-05 Thread Jerry D via Gcc

Forgot to copy the list on this.

 Forwarded Message 
Subject: Re: Hosting our gfortran MatterMost workspace
Date: Fri, 5 May 2023 10:24:11 -0700
From: Jerry D 
To: Mark Wielaard 

On 4/29/23 5:36 AM, Mark Wielaard wrote:

Hi,

On Fri, Apr 28, 2023 at 08:55:44PM +0200, Bernhard Reutner-Fischer wrote:

On 28 April 2023 18:46:07 CEST, Mark Wielaard  wrote:

OSUOSL already provides some machines for sourceware/gcc. If you
could put a bit more technical details into that bugzilla issue,
with expected usage (how many people, groups, moderation?) then we
can coordinate and put it on the overseers agenda.


Or you just ask Lance folks over there, but they'll need a ticket
anyway. As long as there is a sensible IRC adapter I'm sure nobody
would mind it.

I'm not sure if anything ever happened to hosting these here, i only
remember a quick poll some time ago locally.


Just let us know what works best for you. If you feel it could be
useful to the rest of the gcc/sourceware community we can coordinate
through the overseers infrastructure ticket:
https://sourceware.org/bugzilla/show_bug.cgi?id=29853
And we'll arrange a machine through Conservancy & OSUOSL.

But if you are more comfortable setting something up just for the
gfortran hackers and wanting to maintain it fully yourself then going
directly to OSUOSL might be easier for you.

Cheers,

Mark


I have sent an email to Lance at osuosl.org and Mark to see if we can 
get started on this.  I am wondering how to migrate what we have now 
over to a new host.  I will have to query the MatterMost web pages.


Regards,

Jerry