Skip to content

quantized::conv2d and variants don't have explicit schema #36511

@ezyang

Description

@ezyang
    c10::RegisterOperators()
        .op("quantized::conv2d",
            c10::RegisterOperators::options().kernel<QConvInt8<2, false>>(
                DispatchKey::QuantizedCPU))
        .op("_quantized::conv2d",
            c10::RegisterOperators::options().kernel<QConvInt8<2, false>>(
                DispatchKey::QuantizedCPU))
        .op("quantized::conv2d_relu",
            c10::RegisterOperators::options().kernel<QConvInt8<2, true>>(
                DispatchKey::QuantizedCPU))
        .op("_quantized::conv2d_relu",
            c10::RegisterOperators::options().kernel<QConvInt8<2, true>>(
                DispatchKey::QuantizedCPU))
        .op("quantized::conv3d",
            c10::RegisterOperators::options().kernel<QConvInt8<3, false>>(
                DispatchKey::QuantizedCPU))
        .op("quantized::conv3d_relu",
            c10::RegisterOperators::options().kernel<QConvInt8<3, true>>(
                DispatchKey::QuantizedCPU));

While omitting the schema is a reasonable thing that can be done for user-defined operators, all operators in core PyTorch should have explicit schema.

cc @jerryzh168 @jianyuh @dzhulgakov @raghuramank100 @jamesr66a

Metadata

Metadata

Assignees

Labels

better-engineeringRelatively self-contained tasks for better engineering contributorsoncall: quantizationQuantization support in PyTorchtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions