[sdcc-devel] [ sdcc-Bugs-1631895 ] codeseg/constseg #pragma fail

[SourceForge.net <no...@so...>]

Bugs item #1631895, was opened at 2007-01-10 01:20
Message generated for change (Comment added) made by borutr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1631895&group_id=599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: C-Front End
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: xdh (xdh)
>Assigned to: Borut Razem (borutr)
Summary: codeseg/constseg #pragma fail

Initial Comment:
>sdcc -v
SDCC :mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.3 #4543 (Dec 31 2006) (MINGW32)

#pragma codeseg and #pragma constseg produce errors in the generated assembly oode.

#if 1
#pragma codeseg MYCODE
#endif
#if 0
#pragma constseg MYCONST
#endif
const int g_const = 0xDEAD;
int g_global;  
void main(void)
{
	g_global = 0x1234;
	while (1)
	{}
}
>sdcc area02.c
?ASxxxx-Error-<q> in line 113 of area02.asm
              <q> missing or improper operators, terminators, or delimiters removing area02.rel

The offending code is:
;--------------------------------------------------------
; code
;--------------------------------------------------------
	.area (CODE)
Note the missing area name.

In SDCC.lex, the switch cases:
case P_CODESEG: and case P_CONSTSEG: do not handle the buffer properly (the get_pragma_token call to check for end of line blows away the token containing the token dbuf containing the name).

Similarly, the command line processing for the corresponding --codeseg and --constseg options do not append (CODE) qualifier to the area string.

----------------------------------------------------------------------

>Comment By: Borut Razem (borutr)
Date: 2007-01-10 15:36

Message:
Logged In: YES 
user_id=568035
Originator: NO

fixed in svn revision #4568

Borut

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1631895&group_id=599