search for: codegeny

...to think it is > better than MachineInstrs because of developer friendliness, but it isn't > clear to me that LLVM IR with the additions you're talking about would > actually be friendly anymore :-) > As I see it, people working in codegen are going to have to deal with lots of codegeny instructions regardless of whether we call them instructions or intrinsics. Is it really better one way or the other? > Personally, I think that the right representation for legalization is > MachineInstrs supplemented with a type system that allows MVTs as well as > register classes. I...

...tter than MachineInstrs because of developer friendliness, but > it isn't clear to me that LLVM IR with the additions you're talking > about would actually be friendly anymore :-) > > > As I see it, people working in codegen are going to have to deal with > lots of codegeny instructions regardless of whether we call them > instructions or intrinsics. Is it really better one way or the other? > > Personally, I think that the right representation for legalization > is MachineInstrs supplemented with a type system that allows MVTs as > well as...

On Apr 24, 2013, at 5:01 PM, Dan Gohman <dan433584 at gmail.com> wrote: > In the spirit of the (long-term) intent to migrate away from the SelectionDAG framework, it is desirable to implement legalization passes as discrete passes. Attached is a patch which implements the beginning of a new type legalization pass, to help motivate discussion. This is a great discussion to have. > Is

In the spirit of the (long-term) intent to migrate away from the SelectionDAG framework, it is desirable to implement legalization passes as discrete passes. Attached is a patch which implements the beginning of a new type legalization pass, to help motivate discussion. Is LLVM IR the right level for this? The main alternative approach that's been discussed is to do FastISel to a