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]

how well does gcc support type-specific pointer formats?


Does gcc allow backends to have a say in how pointers are represented
(bits beyond the address), what happens in conversions between pointer
types, and what happens in conversions between pointers and uintptr_t?

The target in question has:
- one pointer format and set of load/store instructions for pointers to int/long
- another format and set of load/store instructions for pointers to char
- pointers to short use a third format in general, but can use the int/long
  format IF you know which half of the word you're going to access

What mechanisms, if any, are present in gcc to deal with this?


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