[PATCH] posix: Remove unused OBJECTS_POSIX_INTERRUPTS

[Joel Sherrill]

On Mon, May 20, 2019 at 1:31 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> On 17/05/2019 21:38, Joel Sherrill wrote:
> >
> > I assume you intentionally left the gap in numbering of POSIX API
> > classes for historical consistency. But it does leave a gap in the
> > _Objects_Information_Table and wastes a tiny bit of RAM.
>
> Yes, there are already gaps in the POSIX API classes. Why were explicit
> numbers assigned to the classes?
>

I honestly don't remember beyond 0 never being used for any field
related to an object id. And 1 always being a thread object. Ensuring
that 0 is not used would be my guess.

We have never made any guarantees about the ID values not changing
over time. If we want to eliminate the gaps we can. That would save some
space.

And I have no idea where POSIX Interrupts came from. It doesn't
sound like anything that I have ever heard of.

--joel

>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190521/cbbfcdc7/attachment-0002.html>