Skip to content

Fix inaccuracies in Readme.md and add description of mem-mode.#16

Open
Mittagskogel wants to merge 1 commit into
developfrom
feature/describe-mem-mode
Open

Fix inaccuracies in Readme.md and add description of mem-mode.#16
Mittagskogel wants to merge 1 commit into
developfrom
feature/describe-mem-mode

Conversation

@Mittagskogel

Copy link
Copy Markdown
Collaborator
  • Use double-precision in op-mode code examples.
  • Describe mem-mode with examples. Explain why only double precision works for now.

@lucasmnd

Copy link
Copy Markdown

Hi everyone, thanks for updating the documentation!

Since this PR aims to add a description of mem-mode, I wanted to ask about its current state in the codebase, since I've run into some issues. I'm currently researching mixed-precision in HPC and I'm very interested in using the mem-mode to generate the error heatmap described in Section 6.3 of the paper.

Will this PR also address how to properly build and invoke this error sensitivity tracking? Is the heatmap feature functional in this current branch, or is it maintained somewhere else? Any guidance would be incredibly helpful for our research!

@Mittagskogel Mittagskogel force-pushed the feature/describe-mem-mode branch from dc3edde to 097fc7d Compare June 21, 2026 21:49
@Mittagskogel

Copy link
Copy Markdown
Collaborator Author

Hi @lucasmnd, thank you for reaching out! Take a look here: #18 (comment)

@Mittagskogel Mittagskogel linked an issue Jun 23, 2026 that may be closed by this pull request
@Mittagskogel Mittagskogel requested a review from MinliLiao June 24, 2026 07:04

@MinliLiao MinliLiao left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The C++ part of mem-mode is missing the information on declaring the __raptor_truncate_mem_func, __raptor_truncate_mem_value and __raptor_expand_mem_value in text.
The C++ code example has errors: 1) truncation of b is not stored back in b. 2) there's an extra ); for the truncation of foo.

I'm not familiar with fortran code, but it doesn't seem to have the same problem, so I assume it's good?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing documentation on mem-mode

3 participants