Re: ARM assembler: labels
- From: "Roman Mashak" <mrv@xxxxxxxx>
- Date: Tue, 26 Aug 2008 08:12:30 -0700
Hello, Paul!
You wrote on Mon, 25 Aug 2008 11:42:18 +0300:
PK> Typically label1 and label2 would be descriptive names.
PK> Look at the code where you have the branch/jump instruction to
PK> label1/label2 and there are typically different reasons to going to
PK> either label1 or label2.
This is snippet from the "AT91sam7s getting started" startup code by Atmel:
[skip includes and defines]
/* Application startup entry point */
..globl reset_handler
..align 4
..section .vectors
..arm
/* Exception vectors (should be a branch to be detected as a valid code by
the rom */
_exception_vectors:
reset_vector:
ldr pc, =reset_handler
undef_vector:
b undef_vector /* Undefined Instruction */
......
'_exception_vectors' is not referred anywhere else in the code. I was asking
about such situations. Perhaps Atmel guys writing this code just forgot to
erase old label or they might have left it deliberately for some reason.
PK> For instance, if instruction1/2 are part of a common error handler, it
PK> is practical to list the name of each error contrition with different
PK> label names, although the error handler code is common.
With best regards, Roman Mashak. E-mail: mrv@xxxxxxxx
.
- Follow-Ups:
- Re: ARM assembler: labels
- From: Everett M. Greene
- Re: ARM assembler: labels
- From: Mark L Pappin
- Re: ARM assembler: labels
- Prev by Date: RMII support for Micrel KS8893
- Next by Date: Re: i need help
- Previous by thread: RMII support for Micrel KS8893
- Next by thread: Re: ARM assembler: labels
- Index(es):
Relevant Pages
|
