Skip to content

cmrt_dump.txt generated #5379

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

Closed
zjin-lcf opened this issue Jan 24, 2022 · 10 comments
Closed

cmrt_dump.txt generated #5379

zjin-lcf opened this issue Jan 24, 2022 · 10 comments
Labels
cuda CUDA back-end enhancement New feature or request

Comments

@zjin-lcf
Copy link
Contributor

I find that cmrt_dump.txt is generated after running a SYCL program with CUDA support. The file is empty.

@zjin-lcf zjin-lcf added the enhancement New feature or request label Jan 24, 2022
@AlexeySachkov
Copy link
Contributor

@zjin-lcf, am I right the request here is to explain why that file is being generated and moreover, avoid generating it, right?

@AlexeySachkov AlexeySachkov added the cuda CUDA back-end label Jan 25, 2022
@zjin-lcf
Copy link
Contributor Author

Yes. You are right. Thanks.

@romanovvlad
Copy link
Contributor

@zjin-lcf
Could you please provide all the information asked in the template so we can analyze the issue.
Template:

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Please describe the steps to reproduce the behavior:

  1. Include code snippet as short as possible
  2. Specify the command which should be used to compile the program
  3. Specify the comment which should be used to launch the program
  4. Indicate what is wrong and what was expected

Environment (please complete the following information):

  • OS: [e.g Windows/Linux]
  • Target device and vendor: [e.g. Intel GPU]
  • DPC++ version: [e.g. commit hash or output of clang++ --version]
  • Dependencies version: [e.g. low-level runtime versions (like NEO 20.04)]

Additional context
Add any other context about the problem here.

@zjin-lcf
Copy link
Contributor Author

zjin-lcf commented Feb 1, 2022

Sorry. Could the developers of CM explain when this file is generated ?

@bader
Copy link
Contributor

bader commented Feb 1, 2022

I bet it was caused by ESIMD emulator, which build was enabled for a few days. @dongkyunahn-intel, does it seem like a possible cause?
@zjin-lcf, could you make a clean build of a new compiler and check if this file is still generated, please?

@AlexeySachkov, I don't think it's related to CUDA.

@zjin-lcf
Copy link
Contributor Author

zjin-lcf commented Feb 1, 2022

Yes, I built the compiler with CUDA support today.

configure.py --no-werror --cuda --shared-libs -t release -o build_dir
compile.py -o build_dir 

The file is generated. Can you reproduce that ? Thanks.

@dongkyunahn-intel
Copy link
Contributor

dongkyunahn-intel commented Feb 2, 2022

cmrt_dump.txt is generated by CM - https://github.com/intel/cm-cpu-emulation/blob/3c9eb58b06b72d28de3015d23243f0fa594cdb31/libcmrt/cm_statistics.cpp#L95.

However, ESIMD_EMULATOR using CM is enabled only with --enable-esimd-emulator option in origin/sycl branch (#5366). I would suggest pulling up-to-date origin/sycl branch to local working branch and doing clean build after cleaning $BUILD directory. (rm -rf $BUILD/*)

I did clean build using origin/sycl without ESIMD_EMULATOR support. I cannot find any file related to CM in $BUILD/install directory.

@zjin-lcf
Copy link
Contributor Author

zjin-lcf commented Feb 2, 2022

Thank you for your suggestions!

@zjin-lcf zjin-lcf closed this as completed Feb 2, 2022
@lsatanov
Copy link
Contributor

lsatanov commented Feb 3, 2022

@zjin-lcf, am I right the request here is to explain why that file is being generated and moreover, avoid generating it, right?

Hi. I'll get rid of it in the next CM EMU opensource release.

@zjin-lcf
Copy link
Contributor Author

zjin-lcf commented Feb 3, 2022

Okay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cuda CUDA back-end enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants