From: "Tom St Denis" <tomstdenis AT yahoo DOT com>
Newsgroups: comp.os.msdos.djgpp
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010704095943 DOT 3231S-100000 AT is> <9i2m71$qlf$1 AT news DOT tpi DOT pl>
Subject: Re: Accessing registers from C
Lines: 27
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Message-ID: <mr517.101166$Mf5.28543090@news3.rdc1.on.home.com>
Date: Thu, 05 Jul 2001 21:59:46 GMT
NNTP-Posting-Host: 24.112.8.23
X-Complaints-To: abuse AT home DOT net
X-Trace: news3.rdc1.on.home.com 994370386 24.112.8.23 (Thu, 05 Jul 2001 14:59:46 PDT)
NNTP-Posting-Date: Thu, 05 Jul 2001 14:59:46 PDT
Organization: Excite AT Home - The Leader in Broadband http://home.com/faster
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


"Jacek K." <xos AT o2 DOT pl> wrote in message news:9i2m71$qlf$1 AT news DOT tpi DOT pl...
>
> > To call a procedure via a call gate, you will probably need either
> > inline assembly or an assembly wrapper anyway, right?  So why did you
> > specifically said you want something that isn't inline assembly?
>
> Because I don't want. Unfortunately gcc is very limited. If there was
> something like this:
>
> __attribute__ ((("far")))

Far?

>   and
> __attribute__ ((("interrupt")))          // for intel processors
>
> I wouldn't have a problem.

Typically you don't want interrupts in C, unless they are trivial like

flags |= SOME_INT;
return;

Tom