Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
xilinx:par [2014/06/13 13:50]
mcmaster-guest [3]
xilinx:par [2014/07/16 20:38] (current)
mcmaster-guest
Line 9: Line 9:
  
 On Linux, par seems to trap ^C.  For example, I tried to kill my make job and it appeared to stop.  However, par had trapped the ^C and continued to run.  Once PAR finally finished it received the signal leading to a "​Ctrl-C interrupt detected."​ message far after the make job had ended. ​ This can be especially bad if you run a second par job and they interleave. On Linux, par seems to trap ^C.  For example, I tried to kill my make job and it appeared to stop.  However, par had trapped the ^C and continued to run.  Once PAR finally finished it received the signal leading to a "​Ctrl-C interrupt detected."​ message far after the make job had ended. ​ This can be especially bad if you run a second par job and they interleave.
 +
 +Sometimes I get slow builds (unsure if this was par component or not) because a signal wasn't on combinatorial logic sensitivity list
  
  
 ====== Phases ====== ====== Phases ======
  
-Don't believe there is any documentation on what the phases actually mean+Don't believe there is any documentation on what the phases actually mean
 ===== 1 ===== ===== 1 =====
  
 
xilinx/par.txt · Last modified: 2014/07/16 20:38 by mcmaster-guest
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki