Bug 4651 - chained .req do not work
Summary: chained .req do not work
Status: RESOLVED WONTFIX
Alias: None
Product: binutils
Classification: Unclassified
Component: gas (show other bugs)
Version: 2.15
: P2 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-15 14:30 UTC by Axel Heider
Modified: 2022-09-30 02:40 UTC (History)
1 user (show)

See Also:
Host: i386/cygwin
Target: ARM
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Heider 2007-06-15 14:30:36 UTC 
--------------------------
rsXX1	     .req r0
rsXX2	     .req rsXX1
--------------------------

causes error "Warning: register 'rsXX1' does not exist"
Comment 1 Richard Earnshaw 2007-07-17 15:19:26 UTC 
I think it shouldn't be allowed.  Consider:

rsXX1 .req r0
rsXX2 .req rsXX1
      .unreq rsXX1

What value does rsXX2 have now?  What if rsXX1 were further redefined?
Comment 2 Axel Heider 2007-07-17 21:40:06 UTC 
Well, in this case I would actually expect something like an error at ".unreq
rsXX1" with the message ".unreq not allowed, because another .req definition at
line XXX already depends on it". A un-definition of "rsXX1" should not be
allowerd when other things depend on it, too.
Comment 3 Alan Modra 2022-09-30 02:40:32 UTC 
As per comment 1