From: cartercheng@gmail.com (Carter Cheng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: link time analysis for the kernel.
Date: Fri, 12 Oct 2018 02:55:10 +0800 [thread overview]
Message-ID: <CALS6=qVc1E7=HW3fL5dfKQqQ4mgmt10n_ZKPd1fxodS6+-o+8A@mail.gmail.com> (raw)
In-Reply-To: <11375591539280963@myt1-06117f29c1ea.qloud-c.yandex.net>
Actually I have compiled and installed kernels before. I am wondering
however if LTO still works for compiling kernel images on clang or gcc
since my understanding is the kernel code includes a kernel loader which
loads the ELF format but the image of an OS kernel is loaded either
directly or via a bootloader which my understanding is cannot read ELF(is
this correct?).
On Fri, Oct 12, 2018 at 2:02 AM <o@goosey.org> wrote:
>
>
> 11.10.2018, 17:48, "Carter Cheng" <cartercheng@gmail.com>:
>
> Hi,
>
>
>
> Hello,
>
> I want to ask pardon me and have you ever compiled a linux kernel?
> In my opinion you should first examine gcc ld and make process :)
>
> The elf format executable format and the process after compiling the c
> code.
> Please read:
>
> http://www.ntu.edu.sg/home/ehchua/programming/cpp/gcc_make.html
>
> keep calm and go step by step and continue to learn c, gcc, ld, make, c
> code compile to machine code.
>
> Ozgur
>
>
>
>
> There are some detaills about the current procedures for linking the
> kernel that I am unfamiliar with. My understanding is that GCC and Clang
> both have the ability to do link time analysis and transforms on code but
> is it possible to write link time passes that will run on the kernel since
> the linking phase is a bit different (i.e. doesnt produce an ELF file)?
>
> Regards,
>
> Carter.
> ,
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181012/bcf8c058/attachment.html>
next prev parent reply other threads:[~2018-10-11 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 13:45 link time analysis for the kernel Carter Cheng
2018-10-11 18:02 ` o at goosey.org
2018-10-11 18:55 ` Carter Cheng [this message]
2018-10-11 19:04 ` Ozgur
2018-10-11 19:07 ` Ozgur
2018-10-11 19:46 ` Carter Cheng
2018-10-12 2:20 ` valdis.kletnieks at vt.edu
2018-10-12 6:49 ` Carter Cheng
2018-10-12 7:05 ` Ozgur
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='CALS6=qVc1E7=HW3fL5dfKQqQ4mgmt10n_ZKPd1fxodS6+-o+8A@mail.gmail.com' \
--to=cartercheng@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 NNTP newsgroup(s).