Analysis for developers vs torch.compile

[PaliC]

A nice quality of life feature for researchers would be to provide a nice way to view the torch.compile outputs. This can be done by adding functionality to create what's effectively a directorybackend where the files are cleaned TORCH_LOGS="output_code" logs (with comments intact). Just be sure to append "compile_output" or something to the beginning of the file as this isn't meant to create a backend but an easy way to compare one's directorybackend to the torch.compile implementation.

One implementation of this could be

• Create a "torch.compile" backend
• Use torch._logging.set_logs(output_code=True) + this tool to get a cleaned triton implementation. You can reference the implementation of our logger as well
• Dump the cleaned triton implementation into a directoryBackend directory

[msaroufim]

we likely would need to share machinery to pass in large shapes to torch.compile