NVIDIA / NVIDIA/cutlass

[BUG]The results from different print statements are jumbled together and messy.

Open
#1,752 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

? - Needs Triage bug inactive-30d inactive-90d
Dominant language
C++
Stars
10.5k
Forks
2.1k
Avg merge
3d 11h
Merged PRs (30d)
7

Description

    if(blockIdx.x==0&&blockIdx.y==1&&threadIdx.x==0&&threadIdx.y==0){
      printf("enter tail-365\n");
    } // ----------> This is in one file

    if(blockIdx.x==0&&blockIdx.y==1&&threadIdx.x==383&&threadIdx.y==0){
        print(tCrA);
        printf("    after --- tCrA\n");
      printf("colle 932\n");
    } // ----------> This is in another file

As shown below, the printed results are mess tegether.... Is it a bug? Or my mis-usage?

Image

Image

By the way, "print" does not contain \n, which is not very convenient, and it doesnot contain any word...if we can use "print(trcA, "trcA")", would be more convenient.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing the output using the two conditional print blocks shown in the issue, including the calls from separate files. Inspect how these device-side print statements are ordered and how the custom print output is formatted. Done means determining whether the interleaving is expected misuse or a CUTLASS bug, and documenting or resolving the behavior accordingly.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
hpc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.