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

[hutchinsonandy]

A list would be a good idea.


As hardware is inherrently not re-entrant I personally am not to 
worried about printf (spriint is another matter).

It is  possible somebody may have two or more i/o channels - but I take 
it that would be ok as the file structures would then be separate?


Andy



-----Original Message-----
From: Weddington, Eric <address@hidden>
To: Mark Litwack <address@hidden>; address@hidden
Sent: Mon, 7 Apr 2008 10:56 am
Subject: RE: AW: [avr-gcc-list] reentrant interrupt service routine





> -----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


_______________________________________________
AVR-GCC-list mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list