On Fri, Oct 30, 2020 at 8:54 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 30/10/2020 14:51, Joel Sherrill wrote:
>
> > No one has commented on switching Coverity runs to
> > the master with gcc 9. If we stick with rtems5 for Coverity,
> I received a "Upcoming Coverity
On 30/10/2020 14:51, Joel Sherrill wrote:
No one has commented on switching Coverity runs to
the master with gcc 9. If we stick with rtems5 for Coverity,
I received a "Upcoming Coverity Scan upgrade to Coverity 2020.09"
message today. Maybe the problems evaporate with this upgrade.
--
Thanks. That did the trick. I will ask about committing it to the branch.
No one has commented on switching Coverity runs to
the master with gcc 9. If we stick with rtems5 for Coverity,
I just don't think it has much value.
Any thoughts?
--joel
On Fri, Oct 30, 2020 at 2:58 AM Sebastian Huber
On 29/10/2020 22:15, Joel Sherrill wrote:
When I build RTEMS with GCC 9 (sparc/leon3) to get Coverity results, I
get this error linking tests that I don't get with gcc 10. I am using
the same newlib and binutils-gdb source so I am a bit confused. Are
there patches in GCC 10 that I need on GCC
Hi
When I build RTEMS with GCC 9 (sparc/leon3) to get Coverity results, I get
this error linking tests that I don't get with gcc 10. I am using the same
newlib and binutils-gdb source so I am a bit confused. Are there patches in
GCC 10 that I need on GCC 9?
[1520/1548] Linking
