> I am new to using SDCC for PICs under Windows. When I compile using
> and exampe C pgm, eg p.c :
> c:\sdcc --debug -mpic14 -p16f628a p.c
> I get a warning message : p.asm:168:Warning  directive ignored
> when debug info is disabled
> But if I use:
> c:\sdcc -mpic14 -p16f628a p.c the warning message does not appear.
> May I know what does Warning  mean, can I just ignore it ?
This is really rather a gputils question, but be this at it may:
In debug mode, SDCC emits extra .line directives in the .asm files to
allow debuggers to match code and C source lines.
These directives are ignored by gpasm unless you tell it to generate
extra debug information in the COFF file using the -g switch to gpasm.
SDCC should invoke gpasm with this switch set if --debug is specified,
BUT (for my money) gpasm crashes more often than not when told to emit
this debug output.
Hence sdcc does not pass -g to gpasm even if it has emitted .line
directives, which in turn makes gpasm kind of angry, filling your screen
To cut a long story short: Just ignore these gpasm warnings---better
still: do not use the --debug switch to sdcc for pic14/pic16 devices.
Someone also ought to file a bug report with gputils after having
verified that this problem persists in the most current code...
PS: You might have considered reading the .asm file at the indicated
location (line 168) yourself... The number after filenames (usually
separated by colons) more often than not gives a line number; warnings
and errors often arise in the vicinity of the stated line.