search for: origvt

Is there a way to force llvm to promote all smaller types to i32 instead of i16? Thanks, Micah Villmow Systems Engineer Advanced Technology & Performance Advanced Micro Devices Inc. S1-609 One AMD Place Sunnyvale, CA. 94085 P: 408-749-3966 -------------- next part -------------- An HTML attachment was scrubbed... URL:

...couple of options: 1) Creating a new virtual method in GISel CallLowering that creates and initialises a CCState or custom subclass. Use that to support target-specific CCStates. 2) Try to remove the need for custom CCState altogether. In <https://reviews.llvm.org/D38894>, Shiva Chen adds an OrigVT field to ISD::ArgFlagsTy which seems much cleaner. It's not immediately obvious to me if the in-tree users that currently track Type rather than EVT could always make do with an EVT instead. [Input welcome!]. * Do any out-of-tree backends have custom calling convention code that requires more...

...1) Creating a new virtual method in GISel CallLowering that creates and > initialises a CCState or custom subclass. Use that to support target-specific > CCStates. > 2) Try to remove the need for custom CCState altogether. In > <https://reviews.llvm.org/D38894>, Shiva Chen adds an OrigVT field to > ISD::ArgFlagsTy which seems much cleaner. It's not immediately obvious to me > if the in-tree users that currently track Type rather than EVT could always > make do with an EVT instead. [Input welcome!]. > * Do any out-of-tree backends have custom calling convention co...

...w virtual method in GISel CallLowering that creates and >> initialises a CCState or custom subclass. Use that to support target-specific >> CCStates. >> 2) Try to remove the need for custom CCState altogether. In >> <https://reviews.llvm.org/D38894>, Shiva Chen adds an OrigVT field to >> ISD::ArgFlagsTy which seems much cleaner. It's not immediately obvious to me >> if the in-tree users that currently track Type rather than EVT could always >> make do with an EVT instead. [Input welcome!]. > > Unfortunately, this solution wouldn't work fo...

...in GISel CallLowering that creates and >>> initialises a CCState or custom subclass. Use that to support target-specific >>> CCStates. >>> 2) Try to remove the need for custom CCState altogether. In >>> <https://reviews.llvm.org/D38894>, Shiva Chen adds an OrigVT field to >>> ISD::ArgFlagsTy which seems much cleaner. It's not immediately obvious to me >>> if the in-tree users that currently track Type rather than EVT could always >>> make do with an EVT instead. [Input welcome!]. >> >> Unfortunately, this solution...

...1) Creating a new virtual method in GISel CallLowering that creates and > initialises a CCState or custom subclass. Use that to support target-specific > CCStates. > 2) Try to remove the need for custom CCState altogether. In > <https://reviews.llvm.org/D38894>, Shiva Chen adds an OrigVT field to > ISD::ArgFlagsTy which seems much cleaner. It's not immediately obvious to me > if the in-tree users that currently track Type rather than EVT could always > make do with an EVT instead. [Input welcome!]. Unfortunately, this solution wouldn't work for Mips since the '...

...method in GISel CallLowering that creates and >> initialises a CCState or custom subclass. Use that to support >> target-specific >> CCStates. >> 2) Try to remove the need for custom CCState altogether. In >> <https://reviews.llvm.org/D38894>, Shiva Chen adds an OrigVT field to >> ISD::ArgFlagsTy which seems much cleaner. It's not immediately >> obvious to me >> if the in-tree users that currently track Type rather than EVT could >> always >> make do with an EVT instead. [Input welcome!]. >>    * Do any out-of-tree backen...