On 30/3/2023 2:07 am, Sebastian Huber wrote:
> On 28.03.23 23:46, Chris Johns wrote:
>> On 29/3/2023 5:36 am, Sebastian Huber wrote:
>>> On 28.03.23 09:26, Chris Johns wrote:
On 28/3/2023 6:20 pm, Sebastian Huber wrote:
> On 28.03.23 09:03, Chris Johns wrote:
>> On 28/3/2023 5:48 pm, S
On 28.03.23 23:46, Chris Johns wrote:
On 29/3/2023 5:36 am, Sebastian Huber wrote:
On 28.03.23 09:26, Chris Johns wrote:
On 28/3/2023 6:20 pm, Sebastian Huber wrote:
On 28.03.23 09:03, Chris Johns wrote:
On 28/3/2023 5:48 pm, Sebastian Huber wrote:
On 25.03.23 00:39, Chris Johns wrote:
On 2
On 29/3/2023 5:36 am, Sebastian Huber wrote:
> On 28.03.23 09:26, Chris Johns wrote:
>> On 28/3/2023 6:20 pm, Sebastian Huber wrote:
>>> On 28.03.23 09:03, Chris Johns wrote:
On 28/3/2023 5:48 pm, Sebastian Huber wrote:
> On 25.03.23 00:39, Chris Johns wrote:
>> On 24/3/2023 7:32 pm, S
On 28.03.23 09:26, Chris Johns wrote:
On 28/3/2023 6:20 pm, Sebastian Huber wrote:
On 28.03.23 09:03, Chris Johns wrote:
On 28/3/2023 5:48 pm, Sebastian Huber wrote:
On 25.03.23 00:39, Chris Johns wrote:
On 24/3/2023 7:32 pm, Sebastian Huber wrote:
On 23.03.23 20:07, Chris Johns wrote:
On
On 28/3/2023 6:20 pm, Sebastian Huber wrote:
> On 28.03.23 09:03, Chris Johns wrote:
>> On 28/3/2023 5:48 pm, Sebastian Huber wrote:
>>> On 25.03.23 00:39, Chris Johns wrote:
On 24/3/2023 7:32 pm, Sebastian Huber wrote:
> On 23.03.23 20:07, Chris Johns wrote:
>> On 24/3/2023 3:57 am, S
On 28.03.23 09:03, Chris Johns wrote:
On 28/3/2023 5:48 pm, Sebastian Huber wrote:
On 25.03.23 00:39, Chris Johns wrote:
On 24/3/2023 7:32 pm, Sebastian Huber wrote:
On 23.03.23 20:07, Chris Johns wrote:
On 24/3/2023 3:57 am, Sebastian Huber wrote:
On 23.03.23 17:52, Will wrote:
Great ide
On 28/3/2023 5:48 pm, Sebastian Huber wrote:
> On 25.03.23 00:39, Chris Johns wrote:
>> On 24/3/2023 7:32 pm, Sebastian Huber wrote:
>>> On 23.03.23 20:07, Chris Johns wrote:
On 24/3/2023 3:57 am, Sebastian Huber wrote:
> On 23.03.23 17:52, Will wrote:
>> Great idea to store this infor
On 25.03.23 00:39, Chris Johns wrote:
On 24/3/2023 7:32 pm, Sebastian Huber wrote:
On 23.03.23 20:07, Chris Johns wrote:
On 24/3/2023 3:57 am, Sebastian Huber wrote:
On 23.03.23 17:52, Will wrote:
Great idea to store this information in the executable itself. Does this need
a RTEMS_TEST_STA
On 24/3/2023 7:32 pm, Sebastian Huber wrote:
> On 23.03.23 20:07, Chris Johns wrote:
>> On 24/3/2023 3:57 am, Sebastian Huber wrote:
>>> On 23.03.23 17:52, Will wrote:
Great idea to store this information in the executable itself. Does this
need
a RTEMS_TEST_STATE_LINK_ONLY test sta
On 23.03.23 20:07, Chris Johns wrote:
On 24/3/2023 3:57 am, Sebastian Huber wrote:
On 23.03.23 17:52, Will wrote:
Great idea to store this information in the executable itself. Does this need
a RTEMS_TEST_STATE_LINK_ONLY test state or something similar for minimum.exe?
With the notes you can
On 23.03.23 20:09, Joel Sherrill wrote:
Happy to see this but a bit concerned that there is only one
architecture's BSPs addressed. What about the other architectures?
This patch is just a proof of concept. I can add it to the other BSPs
and tests if we want to support ELF notes.
--
embedded
On 24/3/2023 6:09 am, Joel Sherrill wrote:
> Happy to see this but a bit concerned that there is only one architecture's
> BSPs
> addressed. What about the other architectures?
Yes good question. I read the patch as generic with just enough support to show
how it works.
Chris
___
Happy to see this but a bit concerned that there is only one architecture's
BSPs addressed. What about the other architectures?
--joel
On Thu, Mar 23, 2023, 12:07 PM Chris Johns wrote:
> On 24/3/2023 3:57 am, Sebastian Huber wrote:
> > On 23.03.23 17:52, Will wrote:
> >> Great idea to store thi
On 24/3/2023 3:57 am, Sebastian Huber wrote:
> On 23.03.23 17:52, Will wrote:
>> Great idea to store this information in the executable itself. Does this need
>> a RTEMS_TEST_STATE_LINK_ONLY test state or something similar for minimum.exe?
>
> With the notes you can build the test. The test runner
On 23.03.23 17:52, Will wrote:
Great idea to store this information in the executable itself. Does this
need a RTEMS_TEST_STATE_LINK_ONLY test state or something similar for
minimum.exe?
With the notes you can build the test. The test runner would look at the
notes and then decide if it makes
This is a prototype patch for adding ELF notes.
ELF notes can be used to attach domain-specific data to ELF files. This could
be used to store for example the RTEMS version, Git commit, configuration
options, expected test state, etc. in the executable ELF file.
Example:
readelf -n build/arm/xi
16 matches
Mail list logo