search for: d43951

...n during its > analysis. You just made a very strong argument for building the MachineInstrs before running mca. So I wonder why you didn’t do that. > What to do next > --------------- > The source code has been uploaded for review on phabricator at this link: https://reviews.llvm.org/D43951 <https://reviews.llvm.org/D43951>. > > The review covers two patches: > A first (very small) patch that always enables the generation of processor > resource names in the SubtargetEmitter. Currently, the processor resource names > are only generated for debugging purposes, but...

...d 'MayLoad/MayStore/HasUnmodeledSideEffects' opcode properties still apply to MCInst. The tool knows about this, and uses that information during its analysis. What to do next --------------- The source code has been uploaded for review on phabricator at this link: https://reviews.llvm.org/D43951. The review covers two patches: A first (very small) patch that always enables the generation of processor resource names in the SubtargetEmitter. Currently, the processor resource names are only generated for debugging purposes, but are needed by the tool to generate user friendly reports, so we...

...ffects' opcode properties still > apply to > MCInst. The tool knows about this, and uses that information during its > analysis. > > What to do next > --------------- > The source code has been uploaded for review on phabricator at this > link: https://reviews.llvm.org/D43951. > > The review covers two patches: > A first (very small) patch that always enables the generation of processor > resource names in the SubtargetEmitter. Currently, the processor > resource names > are only generated for debugging purposes, but are needed by the tool to > gen...

...eEffects' opcode properties still > apply to > MCInst. The tool knows about this, and uses that information during its > analysis. > > What to do next > --------------- > The source code has been uploaded for review on phabricator at this link: > https://reviews.llvm.org/D43951. > > The review covers two patches: > A first (very small) patch that always enables the generation of processor > resource names in the SubtargetEmitter. Currently, the processor resource > names > are only generated for debugging purposes, but are needed by the tool to > gene...

...> > > You just made a very strong argument for building the MachineInstrs before > running mca. So I wonder why you didn’t do that. > > What to do next > --------------- > The source code has been uploaded for review on phabricator at this link: > https://reviews.llvm.org/D43951. > > The review covers two patches: > A first (very small) patch that always enables the generation of processor > resource names in the SubtargetEmitter. Currently, the processor resource > names > are only generated for debugging purposes, but are needed by the tool to > gene...