Hi Fabi,
So know is that a bug?
Not a bug as such, more of a mis-feature. Please could you try out the
attached patch which I think will resolve the problem for you.
Yes, it works with the patch, thanks a lot.
Good - I have checked in a extended version of the patch which adds a
comment
>>The docs states:
>>"You may .set a symbol many times in the same assembly."
>>http://sourceware.org/binutils/docs-2.17/as/Set.html#Set
>
>Although the docs never promise that --defsym will behave in the same way as
>.set.
>
>>So know is that a bug?
>
>Not a bug as such, more of a mis-feature.
At 14:38 24.01.2007 +, Nick Clifton wrote:
>Hi Fabian,
>
>>as.exe --defsym PPC603=1 ...
>>file:
>>.set PPC603, 1 # or PPC603 = 1
>
>>file:32: Error: symbol `PPC603' is already defined
>
>>The docs states:
>>"You may .set a symbol many times in the same assembly."
>>http://sourceware.org/binuti
Hi Fabian,
as.exe --defsym PPC603=1 ...
file:
.set PPC603, 1 # or PPC603 = 1
file:32: Error: symbol `PPC603' is already defined
The docs states:
"You may .set a symbol many times in the same assembly."
http://sourceware.org/binutils/docs-2.17/as/Set.html#Set
Although the docs never pr
Hi
I looked into the archives and couldn't find anything about it. So I don't
know if this is intentional or a regression.
as 2.16.1 happily compiled this:
as.exe --defsym PPC603=1 ...
file:
.set PPC603, 1 # or PPC603 = 1
...
while as 2.17 brings an error:
file: Assembler messages:
file:32: E
