+++ John Rigby [2010-10-06 08:31 -0600]:
I'm really sorry to have started this, but for completeness here is
the rest of the story. The hypothetical scenario is a developer that
maintains u-boot for multiple platforms. Using a codesourcery or eldk
(from denx.de) toolchain one can use the
+++ Andrew Stubbs [2010-10-07 12:46 +0100]:
On 07/10/10 12:03, Wookey wrote:
A possible solution to the problem would be to include the sources to
libgcc.a in the installation, and teach gcc to compile it on-the-fly, as
necessary.
If it was possible to separate-out libgcc somewhat so
Hi,
On Thu, Oct 7, 2010 at 3:13 PM, Wookey woo...@wookware.org wrote:
[...]
And whilst on the subject - do the other libs like gomp mudflap and
erm any others that come of of toolchain builds need to be built in
the same set of flavours or is this issue restricted to libgcc?
I think that
I believe that the libgcc.a in our toolchain contains Thumb-2 code. I
verified this by doing objdump on libgcc.a and I see combinations of
16 and 32 bit instructions. So does that mean that the toolchain is
only usable for ARM versions that support Thumb-2?
Thanks,
John
On Wed, Oct 6, 2010 at 11:23 AM, John Rigby john.ri...@linaro.org wrote:
Thanks Michael. Just wanted to make sure I understood. The do no
harm goal and the Thumb2 libgcc seem to be somewhat contradictory
however. I realize that choices need to be made and only odd ducks
like me will likely
On Tue, Oct 05, 2010 at 04:23:01PM -0600, John Rigby wrote:
Thanks Michael. Just wanted to make sure I understood. The do no
harm goal and the Thumb2 libgcc seem to be somewhat contradictory
however. I realize that choices need to be made and only odd ducks
like me will likely run into
