From: Alan Modra <amodra@gmail.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Christophe Lyon <christophe.lyon@linaro.org>,
binutils <binutils@sourceware.org>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: GENERATE_SHLIB_SCRIPT vs. EMBEDDED
Date: Fri, 8 Nov 2019 21:04:12 +1030 [thread overview]
Message-ID: <20191108103411.GU6708@bubble.grove.modra.org> (raw)
In-Reply-To: <20191108051839.GA35767@ubuntu-m2-xlarge-x86>
I'm reverting the patch. My reasons for making it in the first place
were bogus. The ELF file header and program headers are of course
still present in a file created by targets that set EMBEDDED, and the
fact that EMBEDDED stops them being included in the memory image only
affects some uses of those headers. I still don't recommend creating
shared libraries for Linux using -maarch64elf but the resulting shared
library isn't as silly as what I thought.
--
Alan Modra
Australia Development Lab, IBM
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-08 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fb6030c6-f96d-8219-61f9-548dfc9c5b5a@redhat.com>
[not found] ` <20191028235341.GD3663@bubble.grove.modra.org>
[not found] ` <20191105040135.GG6708@bubble.grove.modra.org>
[not found] ` <CAKdteOa8Mf_MOd4Hf8jkcCcgo4bPH8Lss2QCHMu5BBog6N+19Q@mail.gmail.com>
[not found] ` <20191105100317.GI6708@bubble.grove.modra.org>
[not found] ` <20191107073700.GA22249@ubuntu-m2-xlarge-x86>
[not found] ` <20191107074330.GP6708@bubble.grove.modra.org>
[not found] ` <20191107172514.GA9267@ubuntu-m2-xlarge-x86>
[not found] ` <20191107234842.GS6708@bubble.grove.modra.org>
2019-11-08 5:18 ` GENERATE_SHLIB_SCRIPT vs. EMBEDDED Nathan Chancellor
2019-11-08 10:34 ` Alan Modra [this message]
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=20191108103411.GU6708@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=binutils@sourceware.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=natechancellor@gmail.com \
--cc=will@kernel.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).