> > I get the same "mask the shift value before shifting" effect with gcc on > x86 and x86_64. But the compiler is calculating "(1 << 32)" as 0 rather > than 1. This is an inconsistency in the compiler, and arguably it is > /this/ target that is flawed, not the msp430 target. However, since (as > we already know) such shifts are undefined, the compiler is free to > produce different values in different circumstances. >
What about the other MSP compilers like the TI one? How do they handle this? Shouldn't there be a consistency in case of porting code from one compiler to another? ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
