--- Additional Comments From rearnsha at gcc dot gnu dot org 2007-07-18
09:44 ---
(In reply to comment #2)
The only guaranteed way is to write
ADR r0, 0f
ORR r0, r0, #1
BX r0
Note, you should use ORR (not ADD) so that it is guaranteed that the bottom bit
is set.
--
http
--- Additional Comments From rearnsha at gcc dot gnu dot org 2007-07-17
15:30 ---
I think you missed telling us about the -thumb option in your testcase.
The answer is no. The ARM ABI says (http://www.arm.com/pdfs/aaelf.pdf), section
4.6.1.5: A linker is not required to generate
--- Additional Comments From rearnsha at gcc dot gnu dot org 2007-07-17
15:19 ---
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?
--
What|Re
--- Additional Comments From rearnsha at gcc dot gnu dot org 2007-07-17
15:11 ---
This is to be expected. In ELF, local labels have type STT_NOTYPE, and these
can't be used for interworking purposes (only labels of type STT_FUNC can).
--
What|Re
--- Additional Comments From rearnsha at gcc dot gnu dot org 2007-07-17
13:42 ---
Fixed on trunk (2.18)
--
What|Removed |Added
Status|NEW
--- Additional Comments From rearnsha at gcc dot gnu dot org 2007-07-17
12:23 ---
.comm foo, 32
# .type foo, %common
uncomment the line to get an error.
nm -fsysv shows
foo |0020| C |OBJECT|0020| |*COM*
--
http
: binutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: gas
AssignedTo: unassigned at sources dot redhat dot com
ReportedBy: rearnsha at gcc dot gnu dot org
CC: bug-binutils at gnu dot org