public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ankur Saini <arsenic.secondary@gmail.com>
To: Jan Hubicka <hubicka@kam.mff.cuni.cz>
Cc: gcc@gcc.gnu.org
Subject: Re: [GSoC]Bypass assembler when generating LTO object files
Date: Tue, 12 Apr 2022 09:43:34 +0530	[thread overview]
Message-ID: <D2E28315-2036-4B7E-9B2C-B72FBC64C873@gmail.com> (raw)
In-Reply-To: <YlAyZpKtsCauHwhn@kam.mff.cuni.cz>



> On 08-Apr-2022, at 6:32 PM, Jan Hubicka <hubicka@kam.mff.cuni.cz> wrote:
> 
> Ankur,
>> I was browsing the list of submitted GSoC projects this year and the
>> project regarding bypassing assembler when generating LTO object files
>> caught my eye.
> I apologize for late reply.  I would be very happy to mentor this
> project.

Thanks for the reply, but unfortunately, due to some reasons, I would not
be able to take part in GSoC this year.  
But the project seems interesting and would be amazing opportunity to
learn a lot more things for me, so would it be okay if I try to give it a
go outside GSoC if no-one else picks it as their GSoC project this year ?

>> 
>> I already have a gcc built from source (sync-ed with trunk/master) and
>> launched the test-suite on it.
>> 
>> I am currently in process of understanding the primilary patch
>> (https://gcc.gnu.org/legacy-ml/gcc/2014-09/msg00340.html), and
>> experimenting with it.
>> 
>> are there any other things I should be aware of (useful Doc/blog or a
>> bug tracking the project) before proceeding further ?
> 
> I think it is pretty much all that exists.  Basically we will need to
> implement everything that is necessary to stream out valid object file
> directly from GCC rather than going through gas.  The experimental
> prototype sort of worked but it was lacking few things.

When I try to apply that patch on my local branch ( branched from trunk ),
it seem to be incompatible with the current working tree. Is there a
specific branch that I have to apply it to ? or is it due to the recent
file rename patch ( changing extensions from .c to .cc ) ? 

```
$ git apply --check bypass_asm_patch

error: patch failed: Makefile.in:1300
error: Makefile.in: patch does not apply
error: common.opt: No such file or directory
error: langhooks.c: No such file or directory
error: lto/Make-lang.in: No such file or directory
error: lto/lto-object.c: No such file or directory
error: lto/lto.c: No such file or directory
error: lto/lto.h: No such file or directory
error: lto-streamer.h: No such file or directory
error: toplev.c: No such file or directory
```

Thanks 
- Ankur 


  reply	other threads:[~2022-04-12  4:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06 13:30 Ankur Saini
2022-04-08 13:02 ` Jan Hubicka
2022-04-12  4:13   ` Ankur Saini [this message]
2022-04-12  9:18     ` Jan Hubicka
2022-04-12  9:58       ` Richard Biener
2022-04-12 12:31         ` Martin Liška
2022-04-12 12:52           ` Iain Sandoe
2022-04-12 13:41             ` Richard Biener

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=D2E28315-2036-4B7E-9B2C-B72FBC64C873@gmail.com \
    --to=arsenic.secondary@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@kam.mff.cuni.cz \
    /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).