Grant Edwards @ Sat, 16 Feb 2008 06:11:52 +0000 (UTC) [] >> What i mean by text-processing is, that change code.c, >> depending of what programmer wants (details and features must >> be known). For example to analyze codebase for possible >> unaligned access and to substitute it with access methods >> needed, if another target or more efficient code is going to >> be implemented. [...] > > Sorry, I've no idea what you're saying. That it's OK for a > compiler to generate incorrect code as long as it runs fast?
Yes, if this is 90% or more cases (experimentally, e.g. how often this question was addressed here). Otherwise tools must be expanded or fixed. I think, former is easier way, but probably not understood to evaluate, by way i present it. And as it seems, latter is problem of developer's views (current state of the MSP430 toolchain) or/and money (to pay for implementing feature, someone wants/"thinks, is correct"). ________
