This is the mail archive of the
mailing list for the GCC project.
Re: Re: Why not implementation of interrupt attribute on IA32/x86-64
- From: David Fernandez <david dot fernandez dot work at googlemail dot com>
- To: Andi Kleen <andi at firstfloor dot org>, Didier Garcin <didier dot garcin at club-internet dot fr>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 13 Mar 2015 20:45:34 +0000
- Subject: Re: Re: Why not implementation of interrupt attribute on IA32/x86-64
- Authentication-results: sourceware.org; auth=none
- References: <878uf1dm72 dot fsf at tassilo dot jf dot intel dot com>
This is slightly off-topic, but there seems to be lots of different
interrupt attributes in gcc, one for each different processor, which, in
many instances, seem almost the same with different names. also, gcc
could decide on the attribute behaviour depending on the target it
I wonder if there are plans to revise and clean them, or, as there might
be code already using them that should not be broken, define some
unified ones that make more sense.
Just mentioning, as I've programmed for several hardware platforms and
is the kind of thing that looks really ugly in gcc.
On 13/03/15 14:08, Andi Kleen wrote:
Didier Garcin<email@example.com> writes:
many OS hobbyist developpers would be pleased GCC implements the
interrupt or interrupt_handler attribute for Intel architecture.
Would it be so difficult to implement for this architecture ?
There are lots of different ways to implement interrupts on x86
(e.g. what state to save, what registers to set up). It would
be unlikely that gcc would select a subset that worked for most
You're better off with a assembler wrapper that does exactly the
setup you want.