delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/07/27/22:04:25

Xref: news2.mv.net comp.os.msdos.djgpp:6466
Newsgroups: comp.os.msdos.djgpp
From: tob AT world DOT std DOT com (Tom Breton)
Subject: Re: __attribute__((section))
Message-ID: <Dv838w.KIE@world.std.com>
Reply-To: tob AT world DOT std DOT com
Organization: BREnterprises
References: <838478248 DOT 10640 DOT 0 AT abwillms DOT demon DOT co DOT uk>
Date: Sat, 27 Jul 1996 22:17:20 GMT
Lines: 17
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams) writes:
> While we're at it, if we can put things easily into different
> sections, wouldn't that provide a nice easy method of locking memory
> for hardware interrupt handlers? Stick everything in a '.lock'
> section, with sentinel labels in it so that a "lock_everything()" call
> could lock the entire (guaranteed contiguous) section?
>

If I understand right, the linking part of what you suggest should
not only be possible but easy, since constructors and destructors are
already handled similarly. They put pointers to themselves in special
sections (.ctor, .dtor), which djgpp.lnk and some code in crt0 handle
specially. ".lock" would want entire functions and every variable they
touched.

        Tom

- Raw text -


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