build-many-glibcs.py question (updating for multilibs on aarch64)

[Steve Ellcey]

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