On Fri, 2014-02-14 at 12:32 +0100, David Brown wrote: > On 14/02/14 11:19, Brian Drummond wrote: > > On Fri, 2014-02-14 at 09:39 +0100, David Brown wrote: > >> On 14/02/14 00:12, Brian Drummond wrote: > >>> I have built a crosscompiler for the MSP430, using a gcc4.9 snapshot > >>> (gcc-4.9-20140112) > >>> ... what C code fragment would > >>> cause the "enable_interrupts" instruction to be emitted, and generate > >>> "EINT" in the assembler or object output? > That's true - so discussions about the internals of the new msp430 port > are not going to get a big following on the mspgcc users list. But we > on that list are certainly interested in /using/ the new port - once it > is considered fully stable and "released" by TI (including library, > debugger, etc., not just the compiler) then many people there will start > using it. I suspect the official TI release will be built with Ada disabled. So until proved wrong, I need to build my own. > I agree that if these functions are available within the msp430 port of > gcc, then they should be exposed as builtins (and the documentation > should reflect that). I tried looking at the testsuite, which does exercise the builtins, to see how that was ported; e.g. gcc/testsuite/gcc.target/msp430/builtins_bic_sr.c And ... there is no gcc/testsuite/gcc.target/msp430/ folder at all in gcc4.9 yet. > I note that there are a couple of builtins documented: > > <http://gcc.gnu.org/onlinedocs/gcc/MSP430-Built-in-Functions.html> > > These two functions could not be implemented with inline assembly, and > thus /must/ be made as builtins. I haven't got as far as testing these two yet. Hopefully today. - Brian
