[Bug gas/5860] Error: too many positional arguments

[apjain at cisco dot com]

------- Additional Comments From apjain at cisco dot com  2008-03-05 14:07 
-------
Subject: RE:  Error: too many positional arguments

Hi,

Thanks for the reply

Ok, sorry for the confusion.
I did not give complete details.

It normally happens when the defines are in a .macro definition

For ex:

An Asm instruction

 LOAD32  r4,FISRT_BLOCK_END

Where as
     .macro LOAD32 reg,val
        .if ((0xffff8000 <= (\val) ) && ( (\val) <= 0x00007fff))
         li     \reg, \val
        .else
         .if ~(\val) & 0xffff8000
          lis   \reg, HIADJ(\val)
         .else
          lis   \reg, 0x0000
         .endif
         .if (\val) & 0xffff
         addi  \reg, \reg, LO(\val)
         .endif
        .endif
        .endm

And

#define FISRT_BLOCK_END   (LOCAL_MEM_LOCAL_ADRS+EXC_MSG_OFFSET - 4)

Gives too many positional  argumnet error

If I change the definition to  
#define FISRT_BLOCK_END   (LOCAL_MEM_LOCAL_ADRS+EXC_MSG_OFFSET-4)

It is fine

I think there is a similar bug Id 1077, but still in open state

Thanks
aparna

-----Original Message-----
From: amodra at bigpond dot net dot au
[mailto:address@hidden 
Sent: Tuesday, March 04, 2008 3:24 PM
To: Aparna Jain (apjain)
Subject: [Bug gas/5860] Error: too many positional arguments


------- Additional Comments From amodra at bigpond dot net dot au
2008-03-04 09:53 ------- Please attach a test case.  Your bug report
doesn't make sense.  You say you are using #define, ie. C preprocessor
macros, but complain about a gas macro error message.

-- 
           What    |Removed                     |Added
------------------------------------------------------------------------
----
             Status|NEW                         |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=5860

------- You are receiving this mail because: ------- You reported the
bug, or are watching the reporter.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5860

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.