Re: [trunk+v3] Thumb and interworking manipulation goals

[Bart Veer <bartv at ecoscentric dot com>]

>>>>> "John" == John Dallaway <john@dallaway.org.uk> writes:

    John> This patch merges goals for CYGHWR_THUMB and
    John> CYGBLD_ARM_ENABLE_THUMB_INTERWORK to allow selective
    John> application of CDL solutions within the eCos Configuration
    John> Tool. Workaround for Bugzilla 1000707. Checked-in.

I am not sure why this is necessary. Enabling/disabling thumb mode or
interwork support should update CYGBLD_ARCH_CFLAGS and
CYGBLD_ARCH_LDFLAGS, and all ARM targets should be using those for the
default_value's of CYGBLD_GLOBAL_CFLAGS and CYGBLD_GLOBAL_LDFLAGS. So
normally the flags would update automatically, the constraints would
be satisfied, and there is no need for the configtool or the user to
worry about any of this.

The only scenario I can think of where this might be a problem is if a
user starts editing CYGBLD_GLOBAL_CFLAGS or CYGBLD_GLOBAL_LDFLAGS, and
only then manipulates the thumb and interwork settings. Is that worth
worrying about? Or are there other scenarios where the right thing
does not just happen automatically?

The older version of the CDL managed it all with just eight lines of
constraints. The new version requires fourteen, and personally I find
it less clear. It is not a big deal, but I would just like to
understand why the change is necessary.

Bart

-- 
Bart Veer                                   eCos Configuration Architect
eCosCentric Limited    The eCos experts      http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.