search for: liegal

...ce there is no way to specify the LLVMTy manually, there is no way to fix this without finding all of the locations that use this and disabling them. I'm disabling via VT.isPow2VectorType() because an extra check, but it seems like this isn't preferable. So should I conditionalize the pre-liegalized check, or allow a backend to set the LLVMTy of newly created MVT types. So, is the design to disallow backends to set this broken, or what is expected? Let me know what you think is the best way forward. Thanks, Micah -------------- next part -------------- An HTML attachment was scrubbed......

...ce there is no way to specify the LLVMTy manually, there is no way to fix this without finding all of the locations that use this and disabling them. I'm disabling via VT.isPow2VectorType() because an extra check, but it seems like this isn't preferable. So should I conditionalize the pre-liegalized check, or allow a backend to set the LLVMTy of newly created MVT types. So, is the design to disallow backends to set this broken, or what is expected? Let me know what you think is the best way forward. Thanks, Micah --------------------------------------------------------------------- Intel...

...ce there is no way to specify the LLVMTy manually, there is no way to fix this without finding all of the locations that use this and disabling them. I'm disabling via VT.isPow2VectorType() because an extra check, but it seems like this isn't preferable. So should I conditionalize the pre-liegalized check, or allow a backend to set the LLVMTy of newly created MVT types. So, is the design to disallow backends to set this broken, or what is expected? Let me know what you think is the best way forward. Thanks, Micah --------------------------------------------------------------------- Intel...

...ce there is no way to specify the LLVMTy manually, there is no way to fix this without finding all of the locations that use this and disabling them. I'm disabling via VT.isPow2VectorType() because an extra check, but it seems like this isn't preferable. So should I conditionalize the pre-liegalized check, or allow a backend to set the LLVMTy of newly created MVT types. So, is the design to disallow backends to set this broken, or what is expected? Let me know what you think is the best way forward. Thanks, Micah --------------------------------------------------------------------- Intel...