public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Hu <jameshu2022@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Incremental LTO Project
Date: Fri, 8 Sep 2023 07:26:20 -0400	[thread overview]
Message-ID: <CAK7_PN1OeETj42+N9sRK9nVzGkAeOTUBKk7ohPE4mcCbQ-nU3w@mail.gmail.com> (raw)
In-Reply-To: <87edj96shu.fsf@euler.schwinge.homeip.net>

[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]

Ah, I see. I was interested as a contributor but outside of the official
GSoC program. But I'm assuming that because there is a talk on incremental
LTO, it has already been implemented, correct? Other than that, thanks for
your help!

On Fri, Sep 8, 2023 at 3:20 AM Thomas Schwinge <thomas@codesourcery.com>
wrote:

> Hi!
>
> On 2023-09-07T19:00:49-0400, James Hu via Gcc <gcc@gcc.gnu.org> wrote:
> > I noticed that adding incremental LTO was a GSoC project that was not
> > claimed this cycle (
> >
> https://summerofcode.withgoogle.com/programs/2023/organizations/gnu-compiler-collection-gcc
> ).
> > I was curious about working on this project, but wanted to check on the
> > state of the project.
>
> Thanks for your interest!  (... as a potential contributor, I presume?)
>
> > Has it already been completed? Is someone actively
> > working on it?
>
> Yesterday, when browsing the schedule of the GNU Tools Cauldron 2023,
> <https://gcc.gnu.org/wiki/cauldron2023>, I noticed there's going to be a
> presentation on "Incremental LTO in GCC" (Michal Jireš),
> <
> https://gcc.gnu.org/wiki/cauldron2023#cauldron2023talks.incremental_lto_in_gcc
> >.
>
> > If not, what would be the appropriate method to contact the
> > mentor (Jan Hubička)?
>
> He's reading this list, but I've now also put Honza in CC.
>
>
> Grüße
>  Thomas
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201,
> 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer:
> Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München;
> Registergericht München, HRB 106955
>

  reply	other threads:[~2023-09-08 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 23:00 James Hu
2023-09-08  7:20 ` Thomas Schwinge
2023-09-08 11:26   ` James Hu [this message]
2023-09-10 21:25   ` Jan Hubicka
2023-09-27  0:11     ` Thomas Schwinge

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=CAK7_PN1OeETj42+N9sRK9nVzGkAeOTUBKk7ohPE4mcCbQ-nU3w@mail.gmail.com \
    --to=jameshu2022@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=thomas@codesourcery.com \
    /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).