From: Alan Modra <amodra@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH] powerpc/32: Include .branch_lt in data section
Date: Sun, 18 Nov 2018 18:56:52 +1030 [thread overview]
Message-ID: <20181118082652.GA21617@bubble.grove.modra.org> (raw)
In-Reply-To: <87wopetslj.fsf@concordia.ellerman.id.au>
On Thu, Nov 15, 2018 at 11:47:52PM +1100, Michael Ellerman wrote:
> Alan Modra <amodra@gmail.com> writes:
>
> > On Wed, Nov 14, 2018 at 01:32:18PM +1030, Joel Stanley wrote:
> >> I wasn't sure where this should go or if the ordering matters.
> >
> > The usual answer is: "Look at where the section goes in the standard
> > linker scripts." But that doesn't apply here. The section will be
> > empty for a kernel build so it doesn't matter where it goes.
>
> If it's empty why don't we just discard it?
That can be a recipe for finding linker bugs. Not that I'm against
you finding linker bugs. ;-)
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2018-11-18 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 3:02 [PATCH] powerpc/32: Include .branch_lt in data section Joel Stanley
2018-11-14 4:00 ` Alan Modra
2018-11-15 12:47 ` Michael Ellerman
2018-11-18 8:26 ` Alan Modra [this message]
2018-12-19 9:51 ` Michael Ellerman
2019-02-08 13:02 ` Michael Ellerman
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=20181118082652.GA21617@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).