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

hbpintool returning 0.0 J inside docker container #3

Open
eafurst opened this issue Jun 1, 2019 · 7 comments
Open

hbpintool returning 0.0 J inside docker container #3

eafurst opened this issue Jun 1, 2019 · 7 comments
Assignees

Comments

@eafurst
Copy link

eafurst commented Jun 1, 2019

When running the hbpintool on a compiled version on /graphit/test/input/cc.gt, the tool always returns

HammerBlade Energy Cost: 0.000000e+00 J
Xeon E7-8894 v4 Energy Cost: 0.000000e+00 J

I've added __attribute__((noinline)) and this doesn't seem to fix the issue.
When I've run the hbpintool on this same file outside of the docker container, it does return nonzero estimates.

@mrutt92
Copy link
Contributor

mrutt92 commented Jun 1, 2019

this sounds like it's being caused by #4 ?

@eafurst
Copy link
Author

eafurst commented Jun 1, 2019

The compiled cc.gt file runs as expected inside the container. I only have gotten the issue from #4 with bfs_benchmark.gt (so far, these are the only two graphit programs I've tried compiling and running).

@mrutt92
Copy link
Contributor

mrutt92 commented Jun 1, 2019

how are you running bfs_benchmark?

@eafurst
Copy link
Author

eafurst commented Jun 1, 2019

I believe I have how I'm running bfs_benchmark in the body of issue #4.

One thing to note for #4 might be that cc.gt has the default schedule assigned to it and bfs_benchmark.gt has a written schedule.

@eafurst
Copy link
Author

eafurst commented Jun 1, 2019

I am now getting nonzero values when running the hbpintool with the compiled /graphit/test/input/bfs_with_inputfilename_arg.gt and a modified /graphit/test/input/cc.gt that takes a graph filename as an arg (instead of hardcoding in the graph file). I think the issue might be related to having the input graph filename hardcoded into the program (for whatever reason).

@mrutt92
Copy link
Contributor

mrutt92 commented Jun 1, 2019

Oh. It's probably because the working directory is in /hbpintool/ and that path is almost certainly a relative one.

@eafurst
Copy link
Author

eafurst commented Jun 1, 2019

Oh sorry, to clarify #4 was caused just by trying to run the compiled program. I hadn't even gotten to trying to run bfs_benchmark with hbpintool at that point. I was running ./bfs.o ../../test/graphs/4.el from the /graphit/build/bin directory.

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

No branches or pull requests

2 participants