avr-libc-dev
[Top][All Lists]
Advanced

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

[avr-libc-dev] [patch #6500] Reentrant code faq


From: Mark Litwack
Subject: [avr-libc-dev] [patch #6500] Reentrant code faq
Date: Wed, 30 Apr 2008 22:56:20 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080416 Fedora/2.0.0.14-1.fc8 Firefox/2.0.0.14

URL:
  <http://savannah.nongnu.org/patch/?6500>

                 Summary: Reentrant code faq
                 Project: AVR C Runtime Library
            Submitted by: mlitwack
            Submitted on: Wednesday 04/30/2008 at 22:56
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Date: Mon, 7 Apr 2008 08:56:59 -0600
Message-ID:
<address@hidden>
In-Reply-To: <address@hidden>
Thread-Topic: AW: [avr-gcc-list] reentrant interrupt service routine
Thread-Index: AciYu0Kz/U2G9VocRI+0Qcm5/ksRvwAA+KbQ
References:
<address@hidden><address@hidden><address@hidden>
<address@hidden>
From: "Weddington, Eric" <address@hidden>
To: "Mark Litwack" <address@hidden>,
 <address@hidden>
Status: R

=20

> -----Original Message-----
> From:=20
> 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
>=20
> 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.
>  =20

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




    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Wednesday 04/30/2008 at 22:56  Name: avr-doc-reentrant.diff  Size: 5kB 
 By: mlitwack

<http://savannah.nongnu.org/patch/download.php?file_id=15568>

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/patch/?6500>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/





reply via email to

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