public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rishi Raj <rishiraj45035@gmail.com>
To: gcc@gcc.gnu.org, mjambor@suse.cz, hubicka@ucw.cz
Subject: [GSOC] few question about Bypass assembler when generating LTO object files
Date: Sun, 2 Apr 2023 03:05:58 +0530	[thread overview]
Message-ID: <CA+1a67My5J=DHDWETr4vHncGPhqLEMM02=RLmWUq0uDeOgozKA@mail.gmail.com> (raw)

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

Hii Everyone,
I had already expressed my interest in the " Bypass assembler when
generating LTO object files" project and making a proposal for the same. I
know I should have done it earlier but I was admitted to the hospital for
past few days :(.
I have a few doubts.
1)

"One problem is that the object files produced by libiberty/simple-object.c
(which is the low-level API used by the LTO code)
are missing some information (such as the architecture info and symbol
table) and API of the simple object will need to be extended to handle
that" I found this in the previous mailing list discussion. So who
output this information currently in the object file, is it assembler?

Also in the current patch for this project by Jan Hubica, from where
are we getting these information from? Is it from crtbegin.o?

2)
"Support in driver to properly execute *1 binary." I found this on Jan
original patch's email. what does it mean

exactly?

Regards

Rishi Raj

             reply	other threads:[~2023-04-01 21:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 21:35 Rishi Raj [this message]
2023-04-03 19:55 ` Rishi Raj
2023-04-03 23:05   ` Jan Hubicka
2023-04-04  0:27     ` Rishi Raj
2023-04-04  0:32       ` Fwd: " Rishi Raj
2023-04-04  8:15       ` Martin Jambor
2023-04-04 10:25       ` Jan Hubicka
2023-04-04 13:07         ` Rishi Raj
2023-04-04 13:59           ` Jan Hubicka

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='CA+1a67My5J=DHDWETr4vHncGPhqLEMM02=RLmWUq0uDeOgozKA@mail.gmail.com' \
    --to=rishiraj45035@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=mjambor@suse.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).