This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Just some thoughts about interrupts on the PowerPC. Interrupt handling is very different for 68K and PPC. 68K uses vectorized (in HW) interrupts. Exceptions are handled the same way as interrupts. PowerPC has one exception for all interrupts (external exception). The vectorization has to be done in SW if at all (for a simple static design it might not be needed). How meaningful would an interrupt keyword in gcc be? How interrupt routines are called are not specified by the PowerPC architecture but by a custom SW architecture. -- Ola Liljedahl olli@enea.se Enea OSE Systems John Breen wrote: > > From: Brendan Simon <brendan@dgs.monash.edu.au> > >How do if the interrupt keyword exists for a particular target. I am > >interested in 68k and powerpc. > > I started working on adding the interrupt attribute for the m68k in > egcs, but I didn't get very far. If you're interested in continuing > with it, I could send you my notes. > > >What is the syntax to the attribute ? Is it the same for all supported > >targets or is it target dependent ? > > Some use __interrupt__. At least one uses __interrupt_handler__. Jeff > told me to use __interrupt__. > > >I couldn't find any info in the general gcc/egcs docs. Are there > target > >specific docs which give answers to my questions or do I have to hunt > >through all the source code ? > > I pretty much had to hunt through the source code (what I did was grep > "interrupt" in the machine-dependent source files; I can't remember all > the ones that supported it, except for the c4x). > -- > John A. Breen > jab3@hotmail.com > > Get Your Private, Free Email at http://www.hotmail.com > _______________________________________________ > New CrossGCC FAQ: http://www.objsw.com/CrossGCC > _______________________________________________ > To remove yourself from the crossgcc list, send > mail to crossgcc-request@cygnus.com with the > text 'unsubscribe' (without the quotes) in the > body of the message. _______________________________________________ New CrossGCC FAQ: http://www.objsw.com/CrossGCC _______________________________________________ To remove yourself from the crossgcc list, send mail to crossgcc-request@cygnus.com with the text 'unsubscribe' (without the quotes) in the body of the message.