-
Notifications
You must be signed in to change notification settings - Fork 7
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
"ST.E.SYS" is not available in SASS instructions table #1
Comments
Hi, (2) If you are trying to get the PTX traces, please compile with -03 and run the application. You should have the ptx_traces folder after the application finishes running. It looks like you have only compiled without actually running it. If you are want to work on the SASS, you can skip the LLVM step. (3) The memory traces extraction takes some time, depending on the size of the problem. We haven't reported the time taken by each application for trace extraction. The time noted in the paper is for the predictions. (4) ST.E.SYS is a generic memory. I think convolution 2d from Polybench shouldn't have a generic memory operation. How are you building the application? |
Thanks for your reply. (2) I redo the step (2) above by adding (3) Solved. (4) Solved. The text below records the situation when I redo step (2):
|
Looks like the llvm tool has not been installed correctly. Because there should be more files other than the ones you are showing here. We are working on providing a docker file that has everything installed already. We do that very soon |
Got it. I guess it's due to my llvm tool, too. Thank you very much again. I'm very interested in your work, looking forward to your docker file! :-) |
In order to repeat the result of the paper(SC'21), I make following operations at polybenchGpu/CUDA/2DCONV:
module load cuda_flux
.Now the cuda, llvm/11.0 and cuda_flux have been loaded in module.
clang_cf++ --cuda-gpu-arch=sm_70 -std=c++11 -lcudart 2DConvolution.cu -o 2DConvolution
.There are some warnings such as
implicit conversion from 'int' to 'float'
, but the compilation also completes. After compilation, there are 4 new files, they are2DConvolution
,2DConvolution.cu_fc8b3d24.bc
,2DConvolution.cu_fc8b3d24.out
, and2DConvolution.cu_fc8b3d24.ptx
.There is the first question: I have no idea how to generate the
ptx_trace/
. We have the single*.ptx
, butptx_trace/
was not found, and I didn't find any direction at README.LD_PRELOAD=/home/PPT-GPU/tracing_tool/tracer.so ./2DConvolution
After this we can get
app_config.py
,PTX_Analysis.yml
,bbc.txt
,memory_traces/
andsass_traces/
. This step is much slower than the result in paper, I use more than 8 minites to gain the sass traces.python3 /home/PPT-GPU/ppt.py --app /home/polybench/polybenchGpu-master/CUDA/2DCONV/ --sass --config TITANV --granularity 2
There is the second quetion: when I excute this command, I receive an error
"ST.E.SYS" is not available in SASS instructions table
and then the program exits.I look up the PPT-GPU source code and find that there is no process code for
ST.E.SYS
, I don't know how to figure it out. Actually, when I profile my own applition, the sass_trace also containsST.E.SYS
.The hardware I used is Tesla V100.
The text was updated successfully, but these errors were encountered: