Date: Sun, 23 May 1999 16:17:46 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp-workers AT delorie DOT com
cc: Andris Pavenis <pavenis AT lanet DOT lv>,
        Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Subject: Re: gcc 3.0
In-Reply-To: <199905170522.BAA06889@envy.delorie.com>
Message-ID: <Pine.SUN.3.91.990523160841.16545A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


I hear that latest versions of GCC/EGCS support #pragma interrupt, 
but only for a couple of specific CPUs.  I understand that x86 isn't
one of these CPUs.

How hard would it be to add such support for the DJGPP configuration?
I'd guess that we just need to tell GCC to emit the same prologue and
epilogue code that the wrappers do, right?

WIBNI we had such a feature?  Maybe GCC could even be convinced to reveal 
the size of generated code for an interrupt function, so that people who 
lock code could stop using the kludges they do now?

Perhaps someone would like to work on adding that for GCC 3.0?