This is the mail archive of the
mailing list for the GCC project.
Re: Multilib for ARM in thumb2 mode
- From: Samuel Tardieu <sam at rfc1149 dot net>
- To: Alexandre Pereira Nunes <alexandre dot nunes at gmail dot com>
- Cc: Ramana Radhakrishnan <ramana dot radhakrishnan at arm dot com>, gcc <gcc at gcc dot gnu dot org>
- Date: Fri, 8 May 2009 16:31:02 +0200
- Subject: Re: Multilib for ARM in thumb2 mode
- References: <email@example.com> <3118877665823751004@unknownmsgid> <firstname.lastname@example.org>
* Alexandre Pereira Nunes <email@example.com> [2009-05-08 11:24:14 -0300]
| > Don't you already get this if you created a toolchain with
| > --with-arch=armv7-m and the multilib for thumb ? A toolchain configured for
| > --with-arch=armv7-m and the multilib for thumb would automatically cover
| > this configuration. By default we compile for armv4t and why should one
| > have
| > an additional multi-lib for thumb2 in such a case ?
| And how would someone generate code for an armv4t, or v5, or even v6, with
| thumb1, and other scenarios, using a toolchain built the way you suggest?
| Samuel's idea seems to increase the multilib range to cover most arm
| configurations, and not to generate a build restricted to lesser
| configurations. To cope with your idea and still get the other cases, one
| would have to tweak the multilib configuration anyway, so Samuel's idea
| seems the way to go from the start.
Yes, this is exactly what I was thinking: cover more configurations. For
example, in the engineering school where I teach, we have many ARM boards
with different CPUs, and we would really like to have a single cross-compiler
that our students can use or install on their own machines.