• State Not Answered
  • Locked Locked
  • Replies 19 replies
  • Subscribers 22 subscribers
  • Views 38049 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IF statement in assembly

Sergio brasil

I'm wondering, Does assembler support if staments? (like a C program) Tried something very simple:

org 0h
sjmp BEGIN

org 50h
BEGIN:
	IF R0 == #45
		MOV A, #54
		CPL A
	ELSE
		MOV A, #45
		CPL A
	ENDIF
END

After building and enter debug mode I found this code seems to be a #ifdef like statement instead of a C like if-then-else statement. Did I do something wrong or the assembler does no support if statement?

Parents
  • 0 in reply to Andy Neil

    The implication behind the question is that the OP wants to use assembler because he believes it will be more efficient than 'C'.
    Thus, making the assembler inefficient to match the convenience of 'C' entirely defeats the object!

    This also serves to illustrate the fallacy of assuming that something written in assembler will inherently be more efficient than something written in 'C' - you can easily write inefficient assembler if you choose to (or if you don't have the skill to do otherwise).     Its not like one would haphazardly sprinkle the "if" macros all over. They're simply useful comparisons instructions that replace commonly used code sequences and, if at all, sacrifice one or two machine cycles.

    Further, before one so quickly abandons assembler for C at the first requirement of convenience, one might consider there's a reason its called a "macro assembler" and take advantage of it...unless of course they lack the skill to realize this.

Reply
  • 0 in reply to Andy Neil

    The implication behind the question is that the OP wants to use assembler because he believes it will be more efficient than 'C'.
    Thus, making the assembler inefficient to match the convenience of 'C' entirely defeats the object!

    This also serves to illustrate the fallacy of assuming that something written in assembler will inherently be more efficient than something written in 'C' - you can easily write inefficient assembler if you choose to (or if you don't have the skill to do otherwise).     Its not like one would haphazardly sprinkle the "if" macros all over. They're simply useful comparisons instructions that replace commonly used code sequences and, if at all, sacrifice one or two machine cycles.

    Further, before one so quickly abandons assembler for C at the first requirement of convenience, one might consider there's a reason its called a "macro assembler" and take advantage of it...unless of course they lack the skill to realize this.

Children
No data