llvm/llvm-project

[NVPTX] Implement `TLI.isTruncateFree(EVT, EVT)` and `TLI.isZExtFree()`

Open

#114,339 opened on Oct 31, 2024

View on GitHub
 (11 comments) (0 reactions) (2 assignees)C++ (10,782 forks)batch import
backend:NVPTXgood first issue

Repository metrics

Stars
 (26,378 stars)
PR merge metrics
 (Avg merge 1d 2h) (1,000 merged PRs in 30d)

Description

NVPTX currently does not override TLI.isTruncateFree(EVT, EVT) and TLI.isZExtFree(), and it probably should.

zext/truncate between i32/i64 can probably be considered free, as the values already live in separate 32-bit registers in hardware.

Originally posted by @Artem-B in https://github.com/llvm/llvm-project/pull/98666#discussion_r1681805956

Contributor guide

Research direction
Examine NVPTX target's default implementation of isTruncateFree and isZExtFree; study how other backends (e.g., X86) handle these for i32/i64 conversions; implement overrides in NVPTXTargetLowering.cpp.
Tech stack
cpp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70