[Bug target/114143] Non-thumb arm32 code in thumb multilib for libgcc and in -mthumb build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114143 --- Comment #6 from Hans-Peter Nilsson --- Can --with-multilib-list=aprofile,rmprofile at least be made the default when no colliding --with-* options are specified? Would that blow up "everyone"'s CI due to the extra build time? If so, perhaps then just for release builds? Or do you suggest another solution? (I hope we agree that there *is* a problem.)
[Bug target/114143] Non-thumb arm32 code in thumb multilib for libgcc and in -mthumb build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114143 --- Comment #5 from Richard Earnshaw --- (In reply to Richard Earnshaw from comment #4) > You're going to need --with-multilib=aprofile,rmprofile if you want the full > set of multilibs. But beware it builds a *lot* of them. Sorry, I mean --with-multilib-list, not --with-multilib. To make things worse, configure will silently ignore options it does not recognize.
[Bug target/114143] Non-thumb arm32 code in thumb multilib for libgcc and in -mthumb build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114143 --- Comment #4 from Richard Earnshaw --- You're going to need --with-multilib=aprofile,rmprofile if you want the full set of multilibs. But beware it builds a *lot* of them. We don't enable this by default because it conflicts with --with-arch, --with-cpu and --with-float configure options. Describing how to pick the right multilib when there are so many to chose from is just too complex to describe when the base architecture isn't nailed down.
[Bug target/114143] Non-thumb arm32 code in thumb multilib for libgcc and in -mthumb build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114143 Hans-Peter Nilsson changed: What|Removed |Added Status|WAITING |NEW --- Comment #3 from Hans-Peter Nilsson --- (In reply to Christophe Lyon from comment #1) > What configure flags did you use? Only --target arm-eabi" ? The exact configure options that were used are (besides --prefix): --target=arm-eabi --with-gnu-ld --with-gnu-as --with-newlib --enable-languages=c,c++,lto --enable-checking=release This particular gcc version was trunk: r14-9089-gb4c88cc717e5 It was built together with newlib as of git 4e77fa9b8bf4 (about 2024-02-13) Binutils as of about 2024-02-21. Also seen with binutils-2.42, gcc-13.2.0, newlib-4.4.0.20231231 so I doubt the exact versions are key. > What does gcc --print-multi-lib say? .; thumb;@mthumb arm/autofp/v5te/fpu;@marm@mfpu=auto@march=armv5te+fp@mfloat-abi=hard thumb/autofp/v7/fpu;@mthumb@mfpu=auto@march=armv7+fp@mfloat-abi=hard > You probably haven't built the correct multilibs. If that suggestion boils down to incorrect configure options or make invocation, for the latter: $ make -j7 then much later $ make install If I can't build a whole-thumb binary then why include the thumb multilibs there at all? If certain --with-* options are a requirement for that, IMO this should at least be documented.
[Bug target/114143] Non-thumb arm32 code in thumb multilib for libgcc and in -mthumb build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114143 Richard Earnshaw changed: What|Removed |Added Last reconfirmed||2024-02-28 Status|UNCONFIRMED |WAITING Ever confirmed|0 |1 --- Comment #2 from Richard Earnshaw --- You probably haven't built the correct multilibs. See Christophe's comments
[Bug target/114143] Non-thumb arm32 code in thumb multilib for libgcc and in -mthumb build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114143 Christophe Lyon changed: What|Removed |Added CC||clyon at gcc dot gnu.org --- Comment #1 from Christophe Lyon --- What configure flags did you use? Only --target arm-eabi" ? What does gcc --print-multi-lib say?
