search for: everywon

...involved in lifting in new instructions. Then, these passes would be left untouched, for the sake of maintainability. These passes could be copied for fixed point versions. This would mean a just a little slower compiler (dual passes in some cases), for the case of a separation of the code that not everywone is interested in. Then, these passes could be run just by the DSP targets that need them, and the integer developers would not have to worry at all (perhaps by explicitly excluding fixed point instructions here and there, though). Another idea is to introduce a scheme of intrinsics and perhaps h...

...Then, these passes would be > > left untouched, for the sake of maintainability. These passes could > > be copied for fixed point versions. This would mean a just a little > > slower compiler (dual passes in some cases), for the case of a > > separation of the code that not everywone is interested in. Then, > > these passes could be run just by the DSP targets that need them, > > and the integer developers would not have to worry at all (perhaps > > by explicitly excluding fixed point instructions here and there, > > though). > > Ah now it makes...

...in new instructions. Then, these passes would be > left untouched, for the sake of maintainability. These passes could > be copied for fixed point versions. This would mean a just a little > slower compiler (dual passes in some cases), for the case of a > separation of the code that not everywone is interested in. Then, > these passes could be run just by the DSP targets that need them, and > the integer developers would not have to worry at all (perhaps by > explicitly excluding fixed point instructions here and there, > though). Ah now it makes sense: you want the existing...

...passes would be >>> left untouched, for the sake of maintainability. These passes could >>> be copied for fixed point versions. This would mean a just a little >>> slower compiler (dual passes in some cases), for the case of a >>> separation of the code that not everywone is interested in. Then, >>> these passes could be run just by the DSP targets that need them, >>> and the integer developers would not have to worry at all (perhaps >>> by explicitly excluding fixed point instructions here and there, >>> though). >> >...

...; >>> left untouched, for the sake of maintainability. These passes could > >>> be copied for fixed point versions. This would mean a just a little > >>> slower compiler (dual passes in some cases), for the case of a > >>> separation of the code that not everywone is interested in. Then, > >>> these passes could be run just by the DSP targets that need them, > >>> and the integer developers would not have to worry at all (perhaps > >>> by explicitly excluding fixed point instructions here and there, > >>> thou...