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]

the loss of SET_TYPE


Hi,

I'm trying to port bring the GNU Modula-2 front end up to gcc-4.1.0
and have found out that SET_TYPE has been removed :-)

I see the patch from Dec 2004:

http://gcc.gnu.org/ml/gcc-patches/2004-12/msg00670.html

and understand the reason (no front ends in gcc tree use SET_TYPE
etc). I suppose I'd just like to flag that Modula-2 utilises this type
during the generation of BITSET types and also large sets (built
internally from multiple int length SET_TYPEs). But I totally
understand it might be difficult to justify code which is never run
(and difficult to test) in the main gcc tree..

Pragmatically I guess it is best for me to maintain a reversed patch
which can be applied to a gcc-4.1.0 tar ball which reintroduces this
TYPE. Any thoughts?

Many thanks,
Gaius


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