Re: [PATCH] posix: Remove unused OBJECTS_POSIX_INTERRUPTS

2019-05-21 Thread Joel Sherrill
On Mon, May 20, 2019 at 1:31 AM Sebastian Huber < sebastian.hu...@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_Inf

Re: [PATCH] posix: Remove unused OBJECTS_POSIX_INTERRUPTS

2019-05-19 Thread Sebastian Huber
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 we

Re: [PATCH] posix: Remove unused OBJECTS_POSIX_INTERRUPTS

2019-05-17 Thread Joel Sherrill
Hi I have no idea where POSIX Interrupts came from. That doesn't match anything in the POSIX standard or any draft I have seen. 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 waste

[PATCH] posix: Remove unused OBJECTS_POSIX_INTERRUPTS

2019-05-17 Thread Sebastian Huber
--- cpukit/include/rtems/score/objectdata.h | 1 - cpukit/rtems/src/rtemsobjectgetapiclassname.c | 3 --- 2 files changed, 4 deletions(-) diff --git a/cpukit/include/rtems/score/objectdata.h b/cpukit/include/rtems/score/objectdata.h index f6ece16c0e..ce6e3c63a4 100644 --- a/cpukit/include/