Covid Code-In Update (27 March 2020)

[Joel Sherrill]

Hi

I hope this email finds you and your loved ones all well.  Thanks to
everyone who has submitted patches or helped potential GSoC students the
past couple of weeks. Here are some updates on potential small tasks to
pass time. Although I must admit that Tiger King on Netflix has been
entertaining so far as well. :)

First, I have added some more small tasks. You can view them at
https://devel.rtems.org/wiki/SmallTasks. If you think of more, please let
me know or file them yourself with the tag "small, tasks"

Second, I have generated a new warnings report and placed it at
https://ftp.rtems.org/pub/rtems/people/joel/warnings/warnings-5-20200326/.
Below my signature is the summary from the run. When I work warnings, I
tend to take one of two approaches. I call one vertical and one horizontal.

The vertical approach is to address as many as possible in a single BSP
family. This has the advantage that you only need one target toolset and
can just do "make >/dev/null" to see if you fixed a warning when you edit a
file. The disadvantage is that you may end up analyzing the same class of
warning again when you switch BSPs.

The horizontal approach is to look at the warnings per class and pick a
class of warnings and start to sweep across BSPs with them. They tend to
need the same type of fix so there is less repeated analysis of individual
cases required. The file warnings-all-5-20200326.txt lists the entire set
of warnings and which BSP they were found in.

Which approach I take depends on my mood. If I have time, I will tend to
focus on a single BSP and then overnight do a build of all BSPs to get a
broader report. If I am doing a "drive by", I might fix a few warnings that
are common across a lot of BSPs and then start an overnight build sweep.

It is probably easier for most users to take a vertical focus on a single
BSP family and let me generate new reports when the patches are merged.

Follow medical expert advice and stay healthy.

Thanks.

--joel

====================================================
Unique Warnings         :  355
BSPs                    :  134
BSPs with Zero          :  0
BSPs with only in shared:  73

====================================
         Warnings by Class
====================================
      1 address-of-packed-member
      1 array-bounds
      4 char-subscripts
      1 cpp
     96 format=
     56 implicit-function-declaration
     60 incompatible-pointer-types
      4 int-conversion
      4 int-to-pointer-cast
      3 maybe-uninitialized
      1 misleading-indentation
      3 missing-prototypes
      1 nested-externs
      1 register
      1 restrict
      1 shift-count-overflow
      4 strict-aliasing
      2 strict-prototypes
      1 stringop-truncation
      1 unused-const-variable=
      4 unused-function
     14 unused-variable

====================================
     Top Ten BSPs with Warnings
====================================
42 powerpc-qemuprep-altivec  (inBSP=17 inLibCPU=0)
42 powerpc-qemuprep  (inBSP=17 inLibCPU=0)
37 powerpc-beatnik  (inBSP=18 inLibCPU=0)
42 powerpc-mvme5500  (inBSP=19 inLibCPU=0)
154 i386-pc386  (inBSP=26 inLibCPU=0)
154 i386-pc486  (inBSP=26 inLibCPU=0)
154 i386-pc586  (inBSP=26 inLibCPU=0)
154 i386-pc586-sse  (inBSP=26 inLibCPU=0)
154 i386-pc686  (inBSP=26 inLibCPU=0)
154 i386-pcp4  (inBSP=26 inLibCPU=0)
====================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200327/22fa0b3e/attachment-0001.html>