← Back to events
ActiveAIRelease

viable/strict/1789924990: [inductor] Route compile options through backend registrations (#194998)

What happened

Motivation Inductor backends can register a backend-owned ConfigModule through register_backend_for_device(device_custom_config=...) , but values from that module cannot currently be supplied through torch.compile(options=...) . Proposal Allow backend config values to be addressed as " . " compile options: register_backend_for_device ( "my_device" , MyScheduling , MyWrapperCodegen , MyCppWrapperCodegen , device_cust…

Summary assembled by rule from the sources below

Why it's spreading

Sources