OK to push.
Thanks
Chris
On 12/8/21 7:09 am, Ryan Long wrote:
> Hi,
>
> In this series of patches, I just added ostream_guards where there were
> "Restore ostream format" errors. This won't make the error go away, but
> we're going to start ignoring those errors and just placing
> ostream_guards
CID 1505940: Not restoring ostream format
Closes #4472
---
tester/covoar/ReportsText.cc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tester/covoar/ReportsText.cc b/tester/covoar/ReportsText.cc
index 40558d8..edf7984 100644
--- a/tester/covoar/ReportsText.cc
+++ b/tester/covoar/ReportsTex
CID 1506205: Not restoring ostream format
Closes #4484
---
tester/covoar/GcovFunctionData.cc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tester/covoar/GcovFunctionData.cc
b/tester/covoar/GcovFunctionData.cc
index aec04ce..4db5eba 100644
--- a/tester/covoar/GcovFunctionData.cc
+++ b/te
CID 1506202: Not restoring ostream format
Closes #4483
---
tester/covoar/GcovData.cc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tester/covoar/GcovData.cc b/tester/covoar/GcovData.cc
index 02e7489..d4acfa4 100644
--- a/tester/covoar/GcovData.cc
+++ b/tester/covoar/GcovData.cc
@@ -16,6
Hi,
In this series of patches, I just added ostream_guards where there were
"Restore ostream format" errors. This won't make the error go away, but
we're going to start ignoring those errors and just placing
ostream_guards as was done here.
Thanks,
Ryan
Ryan Long (3):
GcovData.cc: Add ostream_
He passed me the correct one via Discord and I ran tests on leon3 and two
failed like his results.
On Wed, Aug 11, 2021, 12:09 PM Gedare Bloom wrote:
> this was the wrong patch version.
>
> On Wed, Aug 11, 2021 at 11:03 AM Joel Sherrill wrote:
> >
> > Module:rtems
> > Branch:master
> >
this was the wrong patch version.
On Wed, Aug 11, 2021 at 11:03 AM Joel Sherrill wrote:
>
> Module:rtems
> Branch:master
> Commit:8df57649b09f31a58660d9b3c2478195f15f40ce
> Changeset:
> http://git.rtems.org/rtems/commit/?id=8df57649b09f31a58660d9b3c2478195f15f40ce
>
> Author:Zacc
On 2021-August-11, at 01:06, Sebastian Huber
wrote:
>
> On 10/08/2021 23:48, Mr. Andrei Chichak wrote:
>> From what I can figure out, there seems to be a problem with the
>> out-of-the-box build of newly that the STM32F4 uses.
>> memset() goes for a few ARM instructions and then seems to intent
On Wed, Aug 11, 2021 at 8:06 AM Ryan Long wrote:
>
> Adjusted number of bytes to be read
>
> CID 1506208: Out-of-bounds access
> CID 1506209: Out-of-bounds access
>
> Closes #4485
> ---
> tester/covoar/GcovData.cc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/test
On Tue, Aug 10, 2021 at 3:21 PM Ida Delphine wrote:
>
> Hi everyone,
> I was able to successfully build LLVM from source using "ninja" instead of
> "make" after a couple of failed attempts because I kept running out of
> resources.
>
> Is there anything else I am supposed to do as far building L
I think this looks fine. Joel, can you check it in?
On Wed, Aug 11, 2021 at 10:01 AM Pranav Dangi wrote:
>
> ping
>
> On Mon, 9 Aug 2021, 16:43 pranav, wrote:
>>
>> The Pi firmware added a wfe(wait for event), the cores 1-3 wait
>> for the start address being written to the mailbox register, fol
ping
On Mon, 9 Aug 2021, 16:43 pranav, wrote:
> The Pi firmware added a wfe(wait for event), the cores 1-3 wait
> for the start address being written to the mailbox register, followed
> by a SEV poke to the mailbox that acts as a wfe wake-up event.
> ---
> bsps/arm/raspberrypi/start/bspsmp.c |
Adjusted number of bytes to be read
CID 1506208: Out-of-bounds access
CID 1506209: Out-of-bounds access
Closes #4485
---
tester/covoar/GcovData.cc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tester/covoar/GcovData.cc b/tester/covoar/GcovData.cc
index 02e7489..da0cc2
On Wed, Aug 11, 2021 at 2:18 AM Chris Johns wrote:
>
> On 11/8/21 3:21 pm, Sebastian Huber wrote:
> > On 10/08/2021 16:50, Sebastian Huber wrote:
> >> On 10/08/2021 16:46, Gedare Bloom wrote:
> >>> This is a good cleanup. The naming seems a bit off to me, but it's all
> >>> internal so we can alwa
Zack.. this doesn't apply for me.
Can you compress it and send it to me privately as an attachment? That will
eliminate the chance an email client AND the mail list archive have
corrupted it.
Thanks.
--joel
On Mon, Aug 9, 2021 at 5:04 PM Gedare Bloom wrote:
>
> Joel: This looks fine to me.
>
>
Hello Kevin,
I'm working on porting the CDC Serial device driver to beagle.
(RTEMS is the device and Linux as host)
I see you have ported USB Serial drivers some time back.
I hope that you can help me clear my doubts.
In your case how did you use a USB Serial adapter and how did you start a
shell
On 11/8/21 3:21 pm, Sebastian Huber wrote:
> On 10/08/2021 16:50, Sebastian Huber wrote:
>> On 10/08/2021 16:46, Gedare Bloom wrote:
>>> This is a good cleanup. The naming seems a bit off to me, but it's all
>>> internal so we can always adjust it later. (I think it should be
>>> singular "Priority
On 10/08/2021 23:48, Mr. Andrei Chichak wrote:
From what I can figure out, there seems to be a problem with the
out-of-the-box build of newly that the STM32F4 uses.
memset() goes for a few ARM instructions and then seems to intentionally
branch into, what the map file indicates is, the middle
18 matches
Mail list logo