gnupic: #pragma for memory maps


Previous by date: 1 Jul 2002 04:24:33 -0000 Re: #pragma for memory maps, Kevin L. Pauba
Next by date: 1 Jul 2002 04:24:33 -0000 Re: #pragma for memory maps, Kevin L. Pauba
Previous in thread: 1 Jul 2002 04:24:33 -0000 Re: #pragma for memory maps, Kevin L. Pauba
Next in thread: 1 Jul 2002 04:24:33 -0000 Re: #pragma for memory maps, Kevin L. Pauba

Subject: Re: #pragma for memory maps
From: "Ricardo Amezquita Orozco" ####@####.####
Date: 1 Jul 2002 04:24:33 -0000
Message-Id: <KFIJBHCGMPLHLDAA@mailcity.com>

Right now I`m working in the devices.c file, and as soon as the pragma syntax is defined, I can start working in the .h files.
Please let me know

Ricardo 
--

On 30 Jun 2002 21:37:02 -050  
 Kevin L. Pauba wrote:
>How about:
>
>#pragma memmap START END TYPE [ALIAS_MASK]
>
>which is just easier to implement?
>
>If no one else is working on this, I can.  I don't want to duplicate
>effort, though.
>
>
>On Thu, 2002-06-27 at 23:55, Scott Dattalo wrote:
>> 
>> Ricardo Orozco was working on a program to convert .inc files into .h 
>> files. But, so was Kevin. Not deterred, Ricardo proceeded to adapt his 
>> program to create the PIC specific memory maps that SDCC needs to allocate 
>> registers. In the process, Ricardo suggested that instead of hardcoding 
>> this info in SDCC, that we create compiler pragmas that could be placed in 
>> the include files. Does anyone have opinions on this?
>> 
>> A possible syntax would be:
>> 
>> #pragma memmap START END [ALIAS_MASK] TYPE
>> 
>> where
>> 
>>   memmap - the pragma
>> 
>>   START, END - define the range of memory
>>   ALIAS_MASK - bit mask defining how/if the register range is aliased
>>   TYPE - type of memory in the range.
>> 
>> For example, a partial listing for a 16F877 would look like:
>> 
>> #pragma memmap 0x20 0x6f RAM
>> #pragma memmap 0x70 0x7f 0x180 RAM
>> #pragma memmap 0x02 0x04 0x180 SFR
>> 
>> 
>> The benefit is that as a user you could define a new memory map without 
>> having to modify the SDCC source. The detriment is that somebody has to 
>> write the code to implement this feature. Hmm.
>> 
>> Scott
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ####@####.####
>> For additional commands, e-mail: ####@####.####
>> 
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>


____________________________________________________________
Win a first-class trip to New Orleans and vacation Elvis Style!.
Enter NOW!
http://r.lycos.com/r/sagel_mail/http://www.elvis.lycos.com/sweepstakes/

Previous by date: 1 Jul 2002 04:24:33 -0000 Re: #pragma for memory maps, Kevin L. Pauba
Next by date: 1 Jul 2002 04:24:33 -0000 Re: #pragma for memory maps, Kevin L. Pauba
Previous in thread: 1 Jul 2002 04:24:33 -0000 Re: #pragma for memory maps, Kevin L. Pauba
Next in thread: 1 Jul 2002 04:24:33 -0000 Re: #pragma for memory maps, Kevin L. Pauba


Powered by ezmlm-browse 0.20.