Merge branch 'master' of https://git.overleaf.com/5f2d21b9b10d6c0001c164a4 into master

1 files changed, 2 insertions, 2 deletions

diff --git a/method-new.tex b/method-new.tex
index fe277cb..c985d59 100644
--- a/method-new.tex
+++ b/method-new.tex
@@ -164,7 +164,7 @@ Having generated HLS-friendly programs and automatically augmented them with dir
 For each HLS tool in turn, we compile the C program to RTL and then simulate the RTL. 
 Independently, we also compile the C program using GCC and execute it. 
 Additionally, to ensure that our testing is scalable for a large number of large, random programs, we also enforce several time-outs: we set a 5-minute time-out for C execution and a 2-hour time-out for RTL simulation.
-Whenever 
+We do not count time-outs as bugs, but we record them.
 
 \paragraph{Types of bugs}
 There two types of bugs that we can encounter in this testing setup: programs that cause the HLS tool to crash during compilation (e.g. an unhandled assertion violation or a segmentation fault), and programs where the software execution and the RTL simulation do not return the same value.
@@ -175,7 +175,7 @@ Programs that cause either type of error are given to the reduction stage, which
 We were only able to test one version of LegUp HLS (version 4.0). 
 LegUp 7.5 is GUI-based and not suitable for scripting. 
 %For all tools, we set a 5-minute and 2-hour for C simulation and RTL simulation respectively. 
-In cases where simulation takes longer, we do not consider them as failures or crashes and we record them. 
+%In cases where simulation takes longer, we do not consider them as failures or crashes and we record them. 
 % When testing Intel HLS, we place three time-outs since its execution is generally slower than other HLS tools: a \ref{XX}-minute time-out for C compilation, a \ref{XX}-hour time out for HLS compilation and a \ref{XX}-hour time-out for co-simulation. 
 
 %  And the number of timeouts placed has increased to 4. The first timeout sets when compiling the C++ program to CPU and returning an executable once finished. The second timeout is placed when running the executable to get the C++ result. The third timeout, which been given the most extended period, is at synthesizing the design and generating the co-simulation executable. Finally, running the co-simulation executable requires the fourth timeout. The test case can be dumped at any timeout period if the task is not finished within the limited time.