Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: when enable arg.print() got print errors #1438

Open
ZJLi2013 opened this issue Aug 4, 2024 · 1 comment
Open

[BUG]: when enable arg.print() got print errors #1438

ZJLi2013 opened this issue Aug 4, 2024 · 1 comment
Assignees

Comments

@ZJLi2013
Copy link

ZJLi2013 commented Aug 4, 2024

Problem Description

to debug 02_gemm_add_add_fastgelu with client api, I tried to enable arg.Print() under Invoker:;Run() as following:

    // Invoker
    struct Invoker : public BaseInvoker
    {
        using Argument = DeviceOp::Argument;

        float Run(const Argument& arg, const StreamConfig& stream_config = StreamConfig{})
        {
            // Fix ME 
            arg.Print();
...

and the original Print()

while during building, these TensorDescriptor , a_grid_desc_m_k_, b_grid_desc_n_k_, ds_grid_desc_m_n_, e_grid_desc_m_n_ doesn't support << operation, give building errrors.

as TensorDescriptor class has its own Print() , looks the following way works:

        void Print() const
        {
            std::cout << "{ \n" ;
                a_grid_desc_m_k_.Print() ;
                b_grid_desc_n_k_.Print(); 
                static_for<0, NumDTensor, 1>{}(
                [&](auto i) { ds_grid_desc_m_n_[i].Print(); });
                e_grid_desc_m_n_.Print();
            std::cout >> "} \n" ; 
        }

Thanks for clarifying this

David

Operating System

ubuntu 20.04

CPU

Ryzen

GPU

AMD Instinct MI300

Other

rocm 6.1.3

ROCm Version

ROCm 6.0.0

ROCm Component

No response

Steps to Reproduce

No response

(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support

No response

Additional Information

No response

@ZJLi2013
Copy link
Author

ZJLi2013 commented Aug 4, 2024

related to #419 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants