This is the mail archive of the gcc-patches@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: [RFC] First steps towards segregating types.

From: Andrew MacLeod <amacleod at redhat dot com>
To: Jeff Law <law at redhat dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Cc: Richard Biener <richard dot guenther at gmail dot com>
Date: Fri, 21 Nov 2014 17:52:47 -0500
Subject: Re: [RFC] First steps towards segregating types.
Authentication-results: sourceware.org; auth=none
References: <546F88E4 dot 1080502 at redhat dot com> <546FBF10 dot 20408 at redhat dot com>

On 11/21/2014 05:39 PM, Jeff Law wrote:

On 11/21/14 11:48, Andrew MacLeod wrote:
There are a few issues, of course :-)

The biggest issue is what to do with fields which can be either a type
or a tree...  ie   TREE_VALUE() of a TREE_LIST can be a type, as can  a
TREE_VEC element or a DECL_CONTEXT.  I think the DECL_INITIAL field is
overloaded and can sometimes be a type, and this was recently introduced
to TARGET_STATIC_CHAIN.  I suspect the compilation process will identify
others.
Well, we rip them apart, naturally :-) The exact mechanism may differfrom one instance to the next.
In the specific case of the TARGET_STATIC_CHAIN changes, I think wecan just split that into two parameters, one of which will be a DECL,the other a TYPE (and one of which will always be NULL).
I'd think these changes ought to move forward independently of yourwork as they're, IMHO independent cleanups.

They are, I was planning to maintain whatever I did as separate patcheson a/the branch


Andrew.

References:
- [RFC] First steps towards segregating types.
  - From: Andrew MacLeod
- Re: [RFC] First steps towards segregating types.
  - From: Jeff Law

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