Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Question] Clarification on FP8 Micro-block Scaling and FP4 Support Timeline

Open
#47 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
compilers

Research direction

Review the current cuTile Python documentation and samples for fp8, bf16, and ct.matmul, then compare them with the issue's questions about Micro-block Scaling and NVFP4. Done means documenting whether scaling is automatic, how scale-factor tiles are supplied if not, and the expected timeline for FP4 tile support.

Written by the indexing model from the issue text.

Description

status: resolved

Hi cuTile team,

I have two specific questions regarding the support for Blackwell-specific hardware features:

  1. Automatic Micro-block Scaling for FP8
    When using fp8 with ct.matmul, how is the Micro-block Scaling (1x16) handled?

Automation: Does the tileiras compiler automatically handle the scaling logic and hardware invocation (5th-gen Tensor Core) under the hood?

Explicit Scaling: If it is not fully automatic, how should we provide the scale-factor tiles to the ct.matmul operator? Currently, the ct.matmul(A, B) signature seems to only accept data tiles. Is there a plan for a signature like ct.matmul(A, B, A_scale, B_scale)?

  1. NVFP4 (FP4) Support Roadmap
    The current documentation and samples focus on fp8 and bf16. Since Blackwell's throughput peak is tied to NVFP4:
    When can we expect the support for 4-bit narrow-precision tiles in cuTile Python?

Thanks for this great library!

Dominant language
Python
Stars
2.2k
Forks
155
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/cutile-python

All issues in NVIDIA/cutile-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.