All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Hollis Blanchard <hollisb@us.ibm.com>,
	xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: Re: [patch] make ELF functions static
Date: Wed, 30 Aug 2006 10:06:42 +0100	[thread overview]
Message-ID: <1156928802.12949.241.camel@localhost.localdomain> (raw)
In-Reply-To: <44F56AAC.76E4.0078.0@novell.com>

On Wed, 2006-08-30 at 09:38 +0100, Jan Beulich wrote:
> >>> Ian Campbell <Ian.Campbell@XenSource.com> 30.08.06 09:03 >>>
> >On Tue, 2006-08-29 at 16:15 -0500, Hollis Blanchard wrote:
> >> Hi Ian, these functions should be static. It would only be a style issue
> >> except PowerPC actually #includes elf.c twice, to support both 32- and
> >> 64-bit ELF binaries. Please apply.
> >
> >Unfortunately they are referenced from outside this file
> >(xen/arch/x86/domain_build.c). 
> >
> >I'm not sure what a good short term fix for you would be. Perhaps some
> >preprocessor/CFLAGS magic to name them xen_elfnote32_foo and
> >xen_elfnote64_foo when compiling powerpc?
> >
> >Hopefully long term the 32-on-64 work that is going on will lead to ELF
> >code which doesn't need to be multiply compiled.
> 
> Why? It's simpler to compile it twice. I already posted draft patches to
> do this, simply introducing an elf32.c that #define-s the relevant
> symbols to alternative names and that only gets compiled when 64-bit
> arches need it for supporting 32-bit binaries.

Fair enough. I should probably have said something like "solves the
problem cleanly for everyone" rather than speculating about how we would
go about it ;-)

Ian.

  parent reply	other threads:[~2006-08-30  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 21:15 [patch] make ELF functions static Hollis Blanchard
2006-08-30  7:03 ` Ian Campbell
2006-08-30  8:38   ` Jan Beulich
2006-08-30  8:44     ` Gerd Hoffmann
2006-08-30  9:06     ` Ian Campbell [this message]
2006-08-30 11:00       ` [XenPPC] " Jimi Xenidis
2006-08-30 11:12         ` Gerd Hoffmann
2006-08-30 11:45         ` Jan Beulich

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=1156928802.12949.241.camel@localhost.localdomain \
    --to=ian.campbell@xensource.com \
    --cc=hollisb@us.ibm.com \
    --cc=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ppc-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.