On Thu, Mar 02, 2006, Darren Salt wrote: > I demand that Johannes Stezenbach may or may not have written... > > [snip] > > But I agree with you, possibly breaking ARM binary compatibility by > > introducing new enum values isn't something I am personally worried about. > > arm-riscos-gcc uses -fno-short-enums by default. I'd be surprised if it's > different for arm-linux-gnu-gcc, though; ARMv3 doesn't have any 16-bit and > signed-byte memory access instructions, ARMv4 and later do, and I'm not sure > about ARMv3T (probably does due to the Thumb extension). (It's also worth > mentioning that these extra instructions have a more restricted constant > offset range: ±255 rather than ±4095 bytes.) > > FWIW, this Risc PC has a StrongARM but was designed for ARM610. It's > pointless even trying to attach a DVB device to it, though... http://www.arm.com/products/DevTools/ABI.html seems to disagree: The base ABI specification says that enums take the smalles int type which can represent all the enum values, and I didn't find (after 10 minutes of searching) any Linux/UNIX specific part which would say something different. If someone has an ARM/Linux toolchain at hand I'd be interested what it actually does. Johannes _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb