This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: New GCC Runtime Library Exception

From: Joe Buck <Joe dot Buck at synopsys dot COM>
To: Mark Mitchell <mark at codesourcery dot com>
Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, David Edelsohn <edelsohn at gnu dot org>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Wed, 28 Jan 2009 20:05:03 -0800
Subject: Re: New GCC Runtime Library Exception
References: <E1LRsu8-0002FN-4G@fencepost.gnu.org> <Pine.LNX.4.64.0901272241380.1184@digraph.polyomino.org.uk> <4980AF47.3000900@codesourcery.com>

On Wed, Jan 28, 2009 at 11:17:27AM -0800, Mark Mitchell wrote:

> > lines long) distributed by GCC that go into runtime libraries used by
> > GCC-compiled code, except those shared with outside projects such as glibc
> > and Classpath (but including e.g. the non-Classpath files in libjava, and
> > those files in libiberty that presently have license exceptions), should
> > use the new wording?
> 
> I don't know about libjava, but certainly libstdc++, libgcc, libgomp,
> and so forth should get the new exception.

I think we need FSF guidance on how to handle "the non-Classpath files in
libjava", given that they wanted to handle Classpath differently.

References:
- New GCC Runtime Library Exception
  - From: David Edelsohn
- Re: New GCC Runtime Library Exception
  - From: Joseph S. Myers
- Re: New GCC Runtime Library Exception
  - From: Mark Mitchell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]