> Thanks to a few clues from Marek, this is now working well. The syntax
> is:
>
> void MyInt(void) __attribute__ ((signal(xx), __INTR_ATTRS));
I would like to update Marek's RFC on this subject. Are there any
instructions somewhere on what is required?
Ron
__
Thanks to a few clues from Marek, this is now working well. The syntax is:
void MyInt(void) __attribute__ ((signal(xx), __INTR_ATTRS));
where xx is a number within the range of AVR interrupts and MyInt can be any
name.
Although not part of the patch, some thought should be given to the C user
ma
> > Where the number in the last case is, of course, taken
> > directly from the
> > Atmel vector table in the specification for the respective
> > processor and
> > adjusted as necessary by the compiler.
> >
>
> My only objection is that the number vector correspond to normal
> avr-libc usage and
> -Original Message-
> From:
> [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> org] On Behalf Of Ron Kreymborg
> Sent: Monday, March 24, 2008 2:28 PM
> To: 'Marek Michalkiewicz'
> Cc: 'Joerg Wunsch'; avr-gcc-list@nongnu.org
> Subject: RE:
> The idea was not mine - based on msp430-gcc where the "interrupt"
> function attribute expects the vector number as argument.
>
> Hope this helps,
> Marek
Therefore as a specification then: The intent of this patch is so an
interrupt function for, say, a mega8 timer0 overflow can be declared as
On Mon, Mar 24, 2008 at 12:53:01AM +1100, Ron Kreymborg wrote:
> So a method that does away with the __vector_XX construct to produce the
> jump to an arbitrary name would be very welcome, as the compiler could then
> detect any spelling error. Darned if I can see how it could be done though.
htt
> As Ron Kreymborg wrote:
>
> > I have had a look at the avr.c file and a fairly simple fix that
bypasses
> > the warning in avr_handle_fndecl_attribute is to add another attribute
to
> > the avr_attribute_table with identical parameters to "signal". For want
of
> > something better I used "cppsig
