RFC: Test optimizations for multiple architectures

H.J. Lu hjl.tools@gmail.com
Fri Nov 12 00:00:00 GMT 2010


On Thu, Nov 11, 2010 at 3:28 PM, David Miller <davem@davemloft.net> wrote:
> From: Roland McGrath <roland@redhat.com>
> Date: Thu, 11 Nov 2010 14:42:22 -0800 (PST)
>
>>> --enable-test-multi-arch is intended for development build, not for production
>>> build. My glibc development build environment is totally separate from the
>>> production build environment. That is true for my gcc, binutils and gdb builds.
>>
>> People who have to maintain production builds need to run full test suites
>> on the actual production code.
>
> I fully agree with Roland on this point.
>
> It would be a huge step backwards if distributions have to enable this
> new set of build cases just to get proper coverage of the individual
> cpu mask bit ifunc cases each time they build their glibc package
> (which we do want them to do).
>

1. Roland suggestion is orthogonal to mine.
2. Roland suggestion may not be easy to implement safely.
3. Even if it works, use it in a test script to cover all cases is complex.
4. We can enable --enable-test-multi-arch by default and change
"make install" to remove libc-test.o from libc.a and libc-test.os from
libc.so when installing libc.

Again, this only covers the testing part, not the granting user control
part, which is a separate issue.


-- 
H.J.



More information about the Libc-alpha mailing list