From: Mohamed Atef <mohamedatef1698@gmail.com>
To: gcc@gcc.gnu.org, Martin Jambor <mjambor@suse.cz>,
Jakub Jelinek <jakub@redhat.com>
Subject: Bypass assembler when generating LTO object files
Date: Sun, 18 Dec 2022 20:20:13 +0200 [thread overview]
Message-ID: <CAPFh8NJ_-RZ-rk8ET=34KDCrhGzhcb38qRiRtri7LnOuC1opEg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 173 bytes --]
Hello,
I am interested in working in this project during my free time, is
understanding this https://gcc.gnu.org/wiki/LinkTimeOptimization
A good starting point
Mohamed
next reply other threads:[~2022-12-18 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 18:20 Mohamed Atef [this message]
2023-01-09 18:13 ` Martin Jambor
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='CAPFh8NJ_-RZ-rk8ET=34KDCrhGzhcb38qRiRtri7LnOuC1opEg@mail.gmail.com' \
--to=mohamedatef1698@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).