[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AW: [avr-gcc-list] reentrant interrupt service routine

From: Mark Litwack
Subject: Re: AW: [avr-gcc-list] reentrant interrupt service routine
Date: Mon, 7 Apr 2008 12:25:39 -0400
User-agent: KMail/1.9.9

Ok, that sounds like a plan.

I'll collect whatever wisdom is posted and put together a
short blurb, maybe for the FAQ section.

Post or send me your re-entrant issues, folks!

And I'll open up some wish bugs.  You think one big wish
bug, or multiple bite-size bugs grouped by function?



On Monday 07 April 2008 10:56:59 am Weddington, Eric wrote:
> > -----Original Message-----
> > From:
> > address@hidden
> > [mailto:address@hidden
> > org] On Behalf Of Mark Litwack
> > Sent: Monday, April 07, 2008 8:23 AM
> > To: address@hidden
> > Subject: Re: AW: [avr-gcc-list] reentrant interrupt service routine
> >
> > I don't mean to carry on a conversation with myself, so if
> > no one else is interested in reentrant/non-reentrant I'll be
> > quiet now, but I would appreciate any other non-reentrant
> > issues that people know about.  It's hard to find these
> > things when they happen.
> Yes, I think other are interested (I'm interested at least), but it's
> just that other developers haven't had the time to look into it.
> Since you're going through this, what would be extremely helpful is if
> you could do these things:
> - Create a list of functions that are known re-entrant, and not
> re-entrant. This could be put into the avr-libc user manual for other
> users. Better to put it in the docs, then left to rot in an email
> archive.
> - For those functions that are not re-entrant open up a bug report, set
> it the Priority (I think it's that field) to "1-Wish". That way it's on
> a list to add such re-entrant functions (where possible) at some point,
> but at least it's in the system.
> Thanks,
> Eric Weddington

reply via email to

[Prev in Thread] Current Thread [Next in Thread]