Update on Overleaf.

1 files changed, 2 insertions, 1 deletions

diff --git a/method-new.tex b/method-new.tex
index d420ab2..fe277cb 100644
--- a/method-new.tex
+++ b/method-new.tex
@@ -164,6 +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 
 
 \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.
@@ -173,7 +174,7 @@ Programs that cause either type of error are given to the reduction stage, which
 %Vivado HLS implement C and RTL simulation by default.
 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. 
+%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. 
 % 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.