[Bug libgcc/61152] New: Missing GCC Runtime Library Exception in some files that are included in libgcc

["gjl at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61152

            Bug ID: 61152
           Summary: Missing GCC Runtime Library Exception in some files
                    that are included in libgcc
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: trivial
          Priority: P3
         Component: libgcc
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gjl at gcc dot gnu.org

libgcc sources are not yet separated completey from the compiler, i.e. it
includes tm.h which in turn will include files from the compiler backend like
arm.h.

As such files go into libgcc, they should contain the GCC Runtime Library
Exception (RLE) in their license headers.

I know that these files actually don't add executable code to libgcc and that
the FSF is fine without RLE in these files, yet there are potential users of
GCC that are very concerned about linking their code against libgcc and about
the non-RLE files that are part of the libgcc sources: as soon as a single file
that goes into libgcc (e.g. by include) is GPL but does not contain the RLE,
they won't use GCC as a whole.

Thus, adding RLE to these files can greatly increase acceptance of GCC/libgcc.