[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/836] New: GAS ".set" pseudo op-code handling

From: jp dot subhash at samsung dot com
Subject: [Bug gas/836] New: GAS ".set" pseudo op-code handling
Date: 8 Apr 2005 22:58:25 -0000


I am using GNU assembler 2.15 (on WIN 2000)
I have few questions about ".set" pseudo op-code
Please check with following codes.

    .set tuv, 1
    .long tuv
    .set tuv, _undef+2
    .long tuv

In above case first .long evaluates to .long 1
But in second .long no relocation information is generated, _undef is droped.
Should GAS generate any relocation here? 

    .set tuv, _undef
    .set tuv, tuv+1
    .long tuv

For above code GAS showed "symbol definition loop encountered" error. But if
you change def of 'tuv' as,

    .set tuv, 1
    .set tuv, tuv+_undef
    .long tuv

Then no error is generated (but no relocation also).

Is that the absolute value gets the high priority? Please let me know 
how ".set" is processed. 

Thanks in advance
Best regards

           Summary: GAS ".set" pseudo op-code handling
           Product: binutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gas
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: jp dot subhash at samsung dot com
                CC: bug-binutils at gnu dot org


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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]