This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: build-many-glibcs.py question (updating for multilibs on aarch64)
- From: Steve Ellcey <sellcey at caviumnetworks dot com>
- To: Joseph Myers <joseph at codesourcery dot com>, Steve Ellcey <sellcey at cavium dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Mon, 12 Dec 2016 15:26:44 -0800
- Subject: Re: build-many-glibcs.py question (updating for multilibs on aarch64)
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Steve dot Ellcey at cavium dot com;
- References: <201612122202.uBCM2JuU006047@sellcey-lt.caveonetworks.com> <alpine.DEB.2.20.1612122315290.11503@digraph.polyomino.org.uk>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On Mon, 2016-12-12 at 23:18 +0000, Joseph Myers wrote:
> On Mon, 12 Dec 2016, Steve Ellcey wrote:
>
> >
> > @@ -126,9 +126,15 @@ class Context(object):
> > no_isolate = ('-fno-isolate-erroneous-paths-dereference'
> > ' -fno-isolate-erroneous-paths-attribute')
> > self.add_config(arch='aarch64',
> > - os_name='linux-gnu')
> > + os_name='linux-gnu',
> > + gcc_cfg=['--with-multilib-
> > list=lp64,ilp32'],
> > + glibcs=[{},
> > + {'variant': 'ilp32', 'ccopts': '-
> > mabi=ilp32'}])
> > self.add_config(arch='aarch64_be',
> > - os_name='linux-gnu')
> > + os_name='linux-gnu',
> > + gcc_cfg=['--with-multilib-
> > list=lp64,ilp32'],
> > + glibcs=[{},
> > + {'variant': 'ilp32', 'ccopts': '-
> > mabi=ilp32'}])
> Although building a multilib GCC is logically correct, it's probably not a
> good idea until the stable GCC, binutils and Linux kernel versions used in
> build-many-glibcs.py all have the required support for ILP32, as including
> ILP32 glibc in the same GCC build as LP64 would lose LP64 testing if
> missing kernel headers support for ILP32 results in the ILP32 build
> failing.
>
> Thus, if missing kernel headers support makes the ILP32 build fail, the
> compiler builds for ILP32 should be kept separate until the ILP32 kernel
> headers support is in an actual kernel release, which is used by
> build-many-glibcs.py.
That seems reasonable. What arch names would you suggest for the ILP32
builds? I would probably go with aarch64_ilp32 and aarch32_be_ilp32
unless there was a reason to use something else.
Steve Ellcey
sellcey@caviumnetworks.com