This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Runtime Library Exception in gcc/config/* files?
- From: "Ian Lance Taylor via gcc" <gcc at gcc dot gnu dot org>
- To: Sebastian Huber <sebastian dot huber at embedded-brains dot de>
- Cc: GCC <gcc at gcc dot gnu dot org>
- Date: Fri, 21 Jul 2017 06:50:56 -0700
- Subject: Re: GCC Runtime Library Exception in gcc/config/* files?
- Authentication-results: sourceware.org; auth=none
- References: <fb723cff-8db5-68bb-3f1b-fad8bfb82c5f@embedded-brains.de>
- Reply-to: Ian Lance Taylor <iant at google dot com>
On Fri, Jul 21, 2017 at 2:24 AM, Sebastian Huber
<sebastian.huber@embedded-brains.de> wrote:
>
> there are some files in gcc/config/* that contain the GCC Runtime Library
> Exception
>
> grep -r --include='*.[ch]' 'GCC Runtime Library Exception' -l gcc/config |
> wc
> 186 186 5361
>
> and some files that don't include it
>
> grep -r --include='*.[ch]' 'GCC Runtime Library Exception' -l gcc/config -v
> | wc
> 753 753 20927
>
> Does it matter? What should be used for new files?
I think that in general we should probably use the Runtime Library
Exception for header files that might need to be included by a plugin,
which means anything that might be included by tm.h. But I can't
think of any reason to use the Exception for .c files.
Ian