From: Linus Torvalds <torvalds@linux-foundation.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Vegard Nossum <vegard.nossum@oracle.com>,
Ming Lei <ming.lei@canonical.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] firmware: declare __{start,end}_builtin_fw as pointers
Date: Sun, 26 Jun 2016 10:17:00 -0700 [thread overview]
Message-ID: <CA+55aFzGXmDX5hBcUoBKuUtja0XXZcOGVvmnwK5LgLnSO6oqKg@mail.gmail.com> (raw)
In-Reply-To: <CAOMGZ=FRateUvEMjHt66JZBXbEaFnS7E9UvPxdrJRoAodrEceA@mail.gmail.com>
On Sun, Jun 26, 2016 at 2:24 AM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>
> This is the best I could come up with: assuming gcc is not allowed to
> reason about what's inside the asm(), this is the only way I could
> think of to lose the array information without incurring unnecessary
> overheads. It should also be relatively safe as there is no way to
> accidentally use the underlying arrays without explicitly declaring
> them.
Ugh. I worry about the other places where we do things like this,
depending on the linker just assigning the addresses and us being able
to compare them.
If there is a compiler option to disable this optimization, I would
almost prefer that.. Because we really do have a whole slew of these
things.
Linus
next prev parent reply other threads:[~2016-06-26 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 15:04 [PATCH] firmware: declare __{start,end}_builtin_fw as pointers Vegard Nossum
2016-06-25 21:06 ` Vegard Nossum
2016-06-26 9:24 ` Vegard Nossum
2016-06-26 17:17 ` Linus Torvalds [this message]
2016-10-14 5:52 ` Jiri Slaby
2016-10-14 6:25 ` Vegard Nossum
2016-10-14 6:30 ` Jiri Slaby
2016-06-28 12:23 George Spelvin
2016-06-28 20:08 ` Linus Torvalds
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+55aFzGXmDX5hBcUoBKuUtja0XXZcOGVvmnwK5LgLnSO6oqKg@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=vegard.nossum@gmail.com \
--cc=vegard.nossum@oracle.com \
/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).