---
cpukit/include/rtems/libcsupport.h| 5 ++-
cpukit/libcsupport/src/mallocusablesize.c | 47 +++
spec/build/cpukit/librtemscpu.yml | 1 +
testsuites/libtests/malloctest/init.c | 13 +++
4 files changed, 65 insertions(+), 1 deletion(-)
create mode 10
On 18/2/22 8:58 am, Kinsey Moore wrote:
> On 2/17/2022 15:31, Chris Johns wrote:
>> On 18/2/22 7:12 am, Kinsey Moore wrote:
>>> On 2/17/2022 13:53, Chris Johns wrote:
On 16/2/22 7:38 am, Kinsey Moore wrote:
> Add hooks for manipulating system state before and after interrupts are
> run
On 2/17/2022 15:31, Chris Johns wrote:
On 18/2/22 7:12 am, Kinsey Moore wrote:
On 2/17/2022 13:53, Chris Johns wrote:
On 16/2/22 7:38 am, Kinsey Moore wrote:
Add hooks for manipulating system state before and after interrupts are
run. These hooks serve primarily to allow the MicroBlaze libdebu
On 18/2/22 7:12 am, Kinsey Moore wrote:
> On 2/17/2022 13:53, Chris Johns wrote:
>> On 16/2/22 7:38 am, Kinsey Moore wrote:
>>> Add hooks for manipulating system state before and after interrupts are
>>> run. These hooks serve primarily to allow the MicroBlaze libdebugger
>>> backend to prevent sof
On 2/17/2022 13:53, Chris Johns wrote:
On 16/2/22 7:38 am, Kinsey Moore wrote:
Add hooks for manipulating system state before and after interrupts are
run. These hooks serve primarily to allow the MicroBlaze libdebugger
backend to prevent software breaks from occurring in interrupt context.
I a
On 2/17/2022 13:17, Chris Johns wrote:
On 16/2/22 7:38 am, Kinsey Moore wrote:
It is possible to remove software breaks without actually restoring the
original instruction to memory. When this happens, the original
instruction is lost.
Should this
This ensures that when a software break i
On 16/2/22 7:38 am, Kinsey Moore wrote:
> Add hooks for manipulating system state before and after interrupts are
> run. These hooks serve primarily to allow the MicroBlaze libdebugger
> backend to prevent software breaks from occurring in interrupt context.
I am unsure what problem this is resolv
On 16/2/22 7:38 am, Kinsey Moore wrote:
> It is possible to remove software breaks without actually restoring the
> original instruction to memory. When this happens, the original
> instruction is lost.
Should this
> This ensures that when a software break is removed,
> its original instruct
On 17/2/22 4:45 pm, Sebastian Huber wrote:
> Hello Chris,
>
> On 17/02/2022 04:11, Chris Johns wrote:
>> I would like to approve all commits to this repo.
>>
>> Why have you made this change?
>
> I tried to run the scripts on my Linux machine and this fixed one of the
> issues
> that occurred.
On 17/2/22 5:47 pm, Sebastian Huber wrote:
> On 17/02/2022 06:11, Chris Johns wrote:
>> On 15/2/22 7:48 pm, Sebastian Huber wrote:
>>> On 15/02/2022 02:16, Chris Johns wrote:
On 15/2/22 12:43 am, Sebastian Huber wrote:
> On 03/02/2022 09:09, Sebastian Huber wrote:
>> On 30/01/2022 23:2
10 matches
Mail list logo