From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v2 1/5] symbols: prefix static symbols with their source file names
Date: Mon, 2 Nov 2015 13:47:07 +0000 [thread overview]
Message-ID: <1446472027.3088.41.camel@citrix.com> (raw)
In-Reply-To: <562E217102000078000AE89F@prv-mh.provo.novell.com>
On Mon, 2015-10-26 at 05:49 -0600, Jan Beulich wrote:
> This requires adjustments to the tool generating the symbol table and
> its as well as nm's invocation.
>
> Note: Not warning about duplicate symbols in the EFI case for now, as
> a binutils bug causes misnamed file name entries to appear in EFI
> binaries' symbol tables when the file name is longer than 18 chars.
> (Not doing so also avoids other duplicates getting printed twice.)
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> v2: Also special case file names with directory part (along with
> object ones). Mirror xen-syms linking changes to ARM, but for now
> without generating warnings.
Thanks for taking care of ARM. I assume "without generating warnings"
differs from the x86 behaviour? Is there some followup which us ARM folks
ought to be looking into making?
Ian.
next prev parent reply other threads:[~2015-11-02 13:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 10:47 [PATCH v2 0/5] disambiguate symbol names (part 2) Jan Beulich
2015-10-26 11:49 ` [PATCH v2 1/5] symbols: prefix static symbols with their source file names Jan Beulich
2015-10-28 12:55 ` Andrew Cooper
2015-10-28 13:25 ` Jan Beulich
2015-10-28 13:42 ` Andrew Cooper
2015-10-28 14:29 ` Jan Beulich
2015-11-02 13:47 ` Ian Campbell [this message]
2015-11-02 13:55 ` Jan Beulich
2015-11-02 14:54 ` Ian Campbell
2015-11-02 14:58 ` Jan Beulich
2015-11-02 15:11 ` Ian Campbell
2015-10-26 11:50 ` [PATCH v2 2/5] compat: enforce distinguishable file names in symbol table Jan Beulich
2015-10-28 13:08 ` Andrew Cooper
2015-11-02 15:20 ` Ian Campbell
2015-11-02 16:11 ` Jan Beulich
2015-11-03 12:22 ` Ian Campbell
2015-11-03 12:50 ` Jan Beulich
2015-11-03 13:39 ` Ian Campbell
2015-11-03 15:31 ` Jan Beulich
2015-11-03 15:42 ` Ian Campbell
2015-10-26 11:51 ` [PATCH v2 3/5] x86/mm: override stored file names for multiply built sources Jan Beulich
2015-10-26 12:52 ` Andrew Cooper
2015-10-26 14:34 ` Martin Pohlack
2015-10-26 14:57 ` George Dunlap
2015-10-26 15:12 ` Jan Beulich
2015-10-26 16:27 ` George Dunlap
2015-10-26 11:52 ` [PATCH v2 4/5] x86/mm: build map_domain_gfn() just once Jan Beulich
2015-10-26 12:52 ` Andrew Cooper
2015-10-26 14:58 ` George Dunlap
2015-10-26 11:53 ` [PATCH v2 5/5] x86/mm: only a single instance of gw_page_flags[] is needed Jan Beulich
2015-10-26 14:59 ` George Dunlap
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=1446472027.3088.41.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).