Dear Albert,
In message 20150702000427.562195b4@lilith you wrote:
CONFIG_USE_PRIVATE_LIBGCC should only be an emergency-opt-in, but never ever a default setting.
Well then, should we not revisit commits c3dd823 and 7bfd5ee, which enable CONFIG_USE_PRIVATE_LIBGCC for sh and mips respectively? Either we allow it by default for all architectures, or we forbid it by default for all architectures, but I don't like the idea of a heterogeneous per-arch default setting.
Agreed. I'm really unhappy that I missed these commits (but I have to admit that I don't look too closely at these architectures).
Adding Daniel and Nobuhiro to the address list.
Please correct me if I'm wrong:
- SH: Commit c3dd823 looks as if there was no strong reason for this change, it sounds more like "this works now, so let's do it always".
Is this correct? Then there would be no strong feelings to revert this commit?
- MIPS: Commit 7bfd5ee is more complicatred. MIPS is one of the few architectures (the only one?) were we have both big endian and little endian configurations. This is easy to support within a tool chain. But do we really have MIPS boards that use hard-float? And if so, why would that be the case? U-Boot should not contain any floating point code - if it does, this is an error that needs fixing. As such, this should be a non-issue.
I would expect that any somewhat recent tool chain is now able to support building of both BE and LE MIPS configurations - which are the ones that casue problems here?
Best regards,
Wolfgang Denk