Closed hyunsukimsokcho closed 4 years ago
Thanks for the good suggestion. It will be good to use such thing if you want to more generalize the tool.
TA will run your code under the same directory with each shell script. So do not worry about the evaluation.
I fixed README yesterday. So students who checkout after my fix will have the correct document.
Thanks for the confirm and prompt reply!
Reopen for other students.
Hi. I don't think I fully understand what's going on here. Since I checked out earlier than your update, may I ask for the correct fix?
Nothing serious but just a typo in README.
Function
-> Global
Hmm. The error in #33 still occurs even when I run ../debloater example1.sh example1.ll
in the test directory. Perhaps it's a different issue?
Perhaps,
../debloater ./example1.sh example1.ll
?
Oh, that works well. Thank you.
Good. Sorry I am not a human-friendly front-end programmer.
Haha no it's fine. I've never understood why the ./
is necessary though.
I see problematic dependency in given shell scripts. (
test/example*.sh
) These scripts assume that targetexample*.ll
file is located at the command execution path.My suggestion is adding
cd "{0%/*}"
at the beginning of each shell scripts. For example,example1.sh
will become:Then, the output (without implementation of
ddmin
) becomes:My idea is fixing shell scripts in a way that is agnostic to the path being executed (by forcing
cd
to desired working directory). refAlso, in README, I think
Function
is ratherGlobal
according to the code (src/debloat.ml
):