The compiler creates a temp assembly file which is removed even if the
compilation failed.
I am aware that I am asking a newbie question, so I beg everyone
pardon, but how did you tell the compiler to leave the assembly files
so that you could inspect them and find the bug ??

R#

2009/3/20 Matthias Hartmann <[email protected]>:
> Hi Roberto, hi Sergey,
>
> the problem resides in
> msp430x54xx.h
> and was introduced by the last change in CVS.
> e.g.
> these linses
> #define SFRRPCR_H_          (SFRRPCR_+1)
> sfrb(SFRRPCR_H, SFRRPCR_H_);
> are expanded by the preprocessor to:
> volatile unsigned char SFRRPCR_H asm("(0x0104+1)");
> which is invalid for the assembler.
>
> The lines:
> 50: #define SFRIE1_H_           (SFRIE1_+1)
> 67: #define SFRIFG1_H_          (SFRIFG1_+1)
> 85: #define SFRRPCR_H_          (SFRRPCR_+1)
> should be changed to
> 50: #define SFRIE1_H_           SFRIE1_ + 0x01
> 67: #define SFRIFG1_H_          SFRIFG1_ + 0x01
> 85: #define SFRRPCR_H_          SFRRPCR_ + 0x01
>
> then
> #define SFRRPCR_H_          SFRRPCR_ + 0x01
> sfrb(SFRRPCR_H, SFRRPCR_H_);
> is expanded by the preprocessor to:
> volatile unsigned char SFRRPCR_H asm("0x0104 + 0x01");
> which is valid for the assembler.
>
> @Sergey : If you are reading this, would you please put the above change
> into CVS, thanks.
>
> greetings
>
> Matthias
>
>
> Roberto Padovani schrieb:
>> Hi all,
>>
>> I just built a tool chain with the MSP430X branch, by following the
>> README-MAINTER.txt (thanks Matthias!) and the Wiki instructions.
>> Eveything went well, but when I compile a simple source file (see
>> below) with the -mmcu=msp430x5437, then I get a compilation error; the
>> same source file compiles well with another mcu architecture.
>>
>> //Source file:  main.c
>> #include <signal.h>
>> #include <io.h>
>> int main(void)
>> {
>>       volatile unsigned int cont = 0;
>>       WDTCTL = WDTPW | WDTHOLD;
>>       while(1){
>>               cont = 0xFFFF;
>>               while(cont--);
>>       }
>>       return 0;
>> }
>> // ----end of source file:  main.c
>>
>> The command:          msp430-gcc -O2 -g -mmcu=msp430x5437 -o main.o
>> main.c           gives the following error:
>>
>> C:\DOCUME~1\user\IMPOST~1\Temp/cceIovJc.s: Assembler messages:
>> C:\DOCUME~1\user\IMPOST~1\Temp/cceIovJc.s:137: Error: expected symbol name
>> C:\DOCUME~1\user\IMPOST~1\Temp/cceIovJc.s:138: Error: expected symbol name
>> C:\DOCUME~1\user\IMPOST~1\Temp/cceIovJc.s:139: Error: expected symbol name
>> C:\DOCUME~1\user\IMPOST~1\Temp/cceIovJc.s:140: Error: expected symbol name
>> C:\DOCUME~1\user\IMPOST~1\Temp/cceIovJc.s:141: Error: expected symbol name
>>
>> while the command:      msp430-gcc -O2 -g -mmcu=msp430x2272 -o main.o
>> main.c      compiles just fine.
>>
>> Besides, the assembly temporary file changes everytime and it is
>> deleted automatically, so I cannot inspect it.
>> Is there a way to tell him not to use temporarily files or to keep them ?
>>
>> Is anyone of you working on these MCUs ?
>> I built binutils-2.18 and update the CVS yesterday, is this ok ?
>> I have the following patches, is there anyone missing ?
>>    binutils-14x1-20x1-20x2-20x3-22x4-42x-42x0-461x.patch
>>    binutils-2.17-msp430x24x-msp430x26x.patch
>>    binutils-2.18-14x1-20x1-20x2-20x3-22x4-42x-42x0-461x.patch
>>    binutils-2.18-430X.patch
>>    binutils-2.18-msp430x24x-msp430x26x.patch
>>    binutils-2.19-patch
>>    binutils-ld_scripts.patch
>>    gcc-3.2.3-__FUNCTION__.patch
>>    gcc-3.2.3-cygwin.patch
>>    gcc-3.2.3-mingw.patch
>>    gdb-6.8-430X.patch
>>    insight-6.7.1-64bit.patch
>>    insight-6.7.1-msp430-20080313.patch
>>    msp430-gdb-6.8-fix.patch
>>    msp430-gdb-6.8.patch
>>
>> Thanks a lot for your help!
>>
>> Roberto
>>
>> ------------------------------------------------------------------------------
>> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
>> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
>> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
>> software that enables intelligent coding and step-through debugging.
>> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
>> _______________________________________________
>> Mspgcc-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>>
>>
>>
>>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>

Reply via email to