This is the mail archive of the cgen@sources.redhat.com mailing list for the CGEN 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: Use of DI mode on 32-bit hosts


Michael Meissner writes:
 > Something like c99's inttypes.h (which has types for give me an integer that is
 > exactly 32-bit longs, and give me an integer that is at least 32-bits long, but
 > could be larger depending on the local conditions).

Something along those lines, though I try to approach these things
by only adding as warranted.

 > > 4) This doesn't address INT/UINT.  Ideally it would remain 32 bits
 > >    (i.e. a portable int).
 > 
 > Or maybe they should be slated to be removed.

Except that I missed the part about them also being used to represent
arbitrary width types.

 > I dunno what we should do about the SIMD vector types (ie, V2QI, V8DI, etc.).
 > Most machines these days do have MMX/VIS/SSE/SSE2/etc. type instructions.  The
 > machine I'm targetting has a rather complete set of these instructions.

Well, a minimalist approach could be taken and say they aren't needed
(and neither is SF/DF/etc. btw), the argument being the same as for the
(intended) absence of USI in .cpu files: it's the operation that specified the
type, not the data.
OTOH, they can simplify things downstream ....


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