[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: AW: AW: [avr-gcc-list] Compiler error

From: Mark E. Scott Jr.
Subject: RE: AW: AW: [avr-gcc-list] Compiler error
Date: Tue, 31 May 2005 14:03:41 -0500

The compiler I used for the PIC processor had two memory modes, small
and large, and had a compiler option that I could also specify whether
pointers were 16 or 24 bit.  It would also use a bit of the pointer to
indicate whether the data was in ROM or RAM, for things like passing
const strings.

Mark E. Scott, Jr.
AWS, Inc.
512-478-7727 x 122

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Joerg Wunsch
Sent: Tuesday, May 31, 2005 4:20 AM
To: address@hidden
Subject: Re: AW: AW: [avr-gcc-list] Compiler error

"Haase Bjoern (PT-BEU/EMT) *" <address@hidden> wrote:

>>Which would be kinda neat in order to support the ATmega256's 24-bit
>>(code) address space, btw.

> IIUC, Marek is trying hard to keep working with 2-Byte pointers by
> introducing jump stubs in the lower 64k memory for functions
> residing in > 128k memory. So there will most probably never be need
> for 3-Byte pointers.

I think both ideas have some merit.  24-bit pointers are a universal
solution (like a "huge" memory model) to the problem, the jump stubs
sound like a hack at first, although I agree they might perhaps
eventually even save some code (like the jump stubs IAR is using for
16 K ROM devices).

J"org Wunsch                                           Unix support

AVR-GCC-list mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]