mirror of
https://github.com/deepseek-ai/DeepGEMM.git
synced 2026-11-05 00:47:26 +00:00
[PR #390] Don't enable the assertion check for release build #410
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepGEMM#410
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/deepseek-ai/DeepGEMM/pull/390
Author: @zhangqingshan373
Created: 7/22/2026
Status: 🔄 Open
Base:
main← Head:qshanz/assert📝 Commits (3)
bfed394Don't enable the assertion check for release build7aff304Address comments0907d31Still evaluate the cond and let the compiler to optimize it out📊 Changes
2 files changed (+7 additions, -0 deletions)
View changed files
📝
csrc/utils/exception.hpp(+4 -0)📝
setup.py(+3 -0)📄 Description
There are lots of DG_HOST_ASSERT before lauch the kernel. For example,
github.com/deepseek-ai/DeepGEMM@559d79fb69/csrc/apis/mega.hppFor now, DG_HOST_ASSERT always do the runtime check which will hurt the performance. Only enable the assertion check when DG_DEBUG is set.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.