This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Ulrich Drepper wrote: > Changing the patches for 2.2 is definitely required. OK, will do. BTW, I have a question about multilib. There's two processor type, SH-3 and SH-4. SH-4 has FPU and larger cache. All the (user space) code compiled for SH-3 works on SH-4. Besides, both processor support both endianess. In GCC, they are supported by multilib. In GCC, target sh-unknown-linux-gnu builds, say: libgcc.a ----- SH-3 little endian m4/libgcc.a ----- SH-4 little endian mb/libgcc.a ----- SH-3 big endian mb/m4/libgcc.a ----- SH-4 big endian (actually, sh-unknown-linux-gnu are not yet supported in GCC, we'll send patches) Should we support things like this for GNU C Library? Currently, I do configure for each target (sh3-unknown-linux-gnu, sh4-unknown-linux-gnu with different compiler switch (-mb for bigendian)), on installation. It would be better it built all of them with target sh-unknown-linux-gnu... Please let me know your opinion. --
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |