Menu
▾
▴
[sdcc-devel] [ sdcc-Bugs-968957 ] Case and other incompatabilities with gpasm
|
From: SourceForge.net <no...@so...> - 2004-07-03 08:09:39
|
Bugs item #968957, was opened at 2004-06-08 18:21 Message generated for change (Settings changed) made by vrokas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=968957&group_id=599 Category: pic16 target >Group: unreproducable >Status: Deleted >Resolution: Rejected Priority: 5 Submitted By: Alexander R. Enzmann (xan-der) Assigned to: Vangelis Rokas (vrokas) Summary: Case and other incompatabilities with gpasm Initial Comment: .asm files generated by SDCC seem to be slightly incompatible with gpasm. Directives are being generated in upper case (e.g., LOW, HIGH, #LINE, #FILE), wheras the lexical analyzer in gpasm wants lower case (low, high, #line, #file). Errors look like this: Blink1.asm:8:Error [103] syntax error Blink1.asm:185:Error [103] syntax error Blink1.asm:188:Error [103] syntax error An additional problem is the line: list p=18f1220 gpasm needs the "p" in front of the processor type: list p=p18f1220 sdcc is stripping the "p", even when specified on the command line. Running gpasm with case insensitivity doesn't help, because the case matching (or lack thereof) is done in the gpasm file "scan.l". MPASM (6.5) also fails to assemble the output. sdcc version info: SDCC : pic16/pic14 2.4.1 (Jun 8 2004) (MSVC) gpasm: gpasm-0.12.1 beta ---------------------------------------------------------------------- Comment By: Vangelis Rokas (vrokas) Date: 2004-06-08 21:35 Message: Logged In: YES user_id=770505 You don't provide enough information to trace the problem. SDCC has been producing uppercase (and lowercase sometimes) gpasm directives and instructions without problems for quite a long time. What command line arguments are you using? Can you send the source? Or the .asm file? My version of gputils also, works fine with the list p=18f452 I cannot speak for MPASM, cause I haven't tested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=968957&group_id=599 |