delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1996/03/14/17:41:01

Message-Id: <s14954f8.036@MAIL.TAIT.CO.NZ>
Date: Fri, 15 Mar 1996 11:30:28 +1200
From: Bill Currie <bill_currie AT MAIL DOT TAIT DOT CO DOT NZ>
To: djgpp-workers AT delorie DOT com
Subject: Re: A separate section for locked memory?

On 15/3/96  9:37 am, Mat Hostetter <mat AT ardi DOT com> did thus say >>>
> It can be a real hassle locking down all variables touched at
> interrupt time.  To be truly safe, each C variable being locked
> requires a separate DPMI call to lock it down, which is inefficient
> and ends up locking down lots of scattered pages here and there.
> 
> Would it be possible to add a special magic linker section for
> "locked" memory, that gets locked down in crt0.S (or somesuch) with
> one DPMI call?
> 
> So I could say in gcc:
> 
> volatile int timer_ticks __attribute__ ((section ("locked"))) = 0;
> 
> and have this variable automatically be in locked memory.  I've
> appended the gcc.info information on the section attribute.
> 
> -Mat

I think this is a great idea.  If possible this should be done for code as well as data.


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019