--------------------------------------------------------------------------------
Release 14.7 Trace  (lin64)
Copyright (c) 1995-2013 Xilinx, Inc.  All rights reserved.
 
/mnt/data/opt/Xilinx/ISE/14.7/ISE_DS/ISE/bin/lin64/unwrapped/trce -v 3
-fastpaths -u 25 -intstyle xflow -xml sys_w11a_n2.twx -tsi sys_w11a_n2.tsi
sys_w11a_n2.ncd sys_w11a_n2.pcf


Design file:              sys_w11a_n2.ncd
Physical constraint file: sys_w11a_n2.pcf
Report level:             timespec interaction report
--------------------------------------------------------------------------------
********************************************************************************
*                                                                              *
* This timing constraint interaction report can be used to understand which    *
* timing constraints take precedence when two or more timing constraints cover *
* a common set of timing paths.                                                *
*                                                                              *
* Constraint coverage over a set of paths is based on the following precedence *
* order (lowest to highest precedence):                                        *
*                                                                              *
*   Unconstrained path analysis                                                *
*   PERIOD or FREQUENCY, allclocknets                                          *
*   PERIOD or FREQUENCY, time group                                            *
*   PERIOD or FREQUENCY, net                                                   *
*   OFFSET IN/OUT, global                                                      *
*   OFFSET IN/OUT, time group                                                  *
*   OFFSET IN/OUT, pad                                                         *
*   MAXDELAY path, with pre-defined FROM and TO groups                         *
*   MAXDELAY path, with user-defined FROM or TO group                          *
*   MAXDELAY path, with user-defined FROM and TO groups                        *
*   MAXDELAY path, with intermediate (THRU) points                             *
*   PATH definition                                                            *
*   TIG path                                                                   *
*                                                                              *
* When two or more timing constraints have the same precedence, an optional    *
* PRIORITY qualifier can be used to identify the constraint that should take   *
* precedence for path coverage. If no PRIORITY qualifier exists, the last      *
* constraint encountered in the constraint file will take precedence.          *
*                                                                              *
* The following report lists constraints interactions, where lower-priority    *
* constraints had paths removed due to higher-priority constraints. For each   *
* interaction, the higher-priority constraint and number of paths removed are  *
* listed.                                                                      *
*                                                                              *
* In addition, if two or more interacting constraints have a similar type, a   *
* set of potential constraint consolidations may be reported. It may be        *
* possible to reduce the memory and runtime required for timing analysis by    *
* combining similar constraints.                                               *
*                                                                              *
* A clock domain overlap report will be produced when multiple                 *
* period/frequency constraints are defined to cover the same synchronous       *
* destination elements. This overlap report displays the set of overlapping    *
* constraints in precedence order (lowest to highest precedence) along with    *
* the list of synchronous destination elements shared by those constraints.    *
* The destination elements are listed using their logical resource name        *
* followed parenthetically by their physical resource name and physical clock  *
* pin name.                                                                    *
*                                                                              *
* The clock domain overlap report can be used to detect and correct            *
* overlapping constraint specifications that may be unintentionally altering   *
* the desired clock domain membership and resultant timing analysis of a       *
* design.                                                                      *
*                                                                              *
********************************************************************************

Constraint Interaction Report
=============================

Constraint interactions for Unconstrained path analysis 
         31 paths removed by OFFSET = IN 10 ns BEFORE COMP "I_CLK50";
         11 paths removed by OFFSET = IN 2.5 ns VALID 33 ns BEFORE COMP "I_FX2_IFCLK";
         22 paths removed by OFFSET = OUT 10 ns VALID 33 ns AFTER COMP "I_FX2_IFCLK";
         81 paths removed by OFFSET = OUT 20 ns AFTER COMP "I_CLK50";
    3146957 paths removed by TS_CLK1 = PERIOD TIMEGRP "CLK1" TS_I_CLK50 / 1.04 HIGH 50%;
       1699 paths removed by TS_I_FX2_IFCLK = PERIOD TIMEGRP "I_FX2_IFCLK" 33.34 ns HIGH 50%;
       3365 paths removed by TS_PAD_CLK = MAXDELAY FROM TIMEGRP "PADS(I_CLK50)" TO TIMEGRP "TNM_CLK" 10 ns;

  Consolidating the following similar constraints may reduce the memory and runtime required for timing analysis:
    OFFSET = IN 10 ns BEFORE COMP "I_CLK50";
    OFFSET = OUT 10 ns VALID 33 ns AFTER COMP "I_FX2_IFCLK";


Clock Domain Overlap Report
===========================

No overlap to report.


Timespec interaction analysis completed Sat Mar 19 14:47:49 2016
--------------------------------------------------------------------------------

