<?xml version="1.0" encoding="UTF-8"?>
<!-- IMPORTANT: This is an internal file that has been generated
     by the Xilinx ISE software.  Any direct editing or
     changes made to this file may result in unpredictable
     behavior or data corruption.  It is strongly advised that
     users do not edit the contents of this file. -->
<messages>
<msg type="info" file="Par" num="282" delta="unknown" >No user timing constraints were detected or you have set the option to ignore timing constraints (&quot;par -x&quot;). Place and Route will run in &quot;Performance Evaluation Mode&quot; to automatically improve the performance of all internal clocks in this design. The PAR timing summary will list the performance achieved for each clock. Note: For the fastest runtime, set the effort level to &quot;std&quot;.  For best performance, set the effort level to &quot;high&quot;. For a balance between the fastest runtime and best performance, set the effort level to &quot;med&quot;.
</msg>

<msg type="warning" file="Place" num="414" delta="unknown" >The input design contains local clock signal(s). To get a better result, we recommend users run map with the &quot;-timing&quot; option set before starting the placement.
</msg>

<msg type="warning" file="Place" num="1019" delta="unknown" >A clock IOB / clock component pair have been found that are not placed at an optimal clock IOB / clock site pair. The clock component &lt;<arg fmt="%s" index="1">F_SCK_BUFGP/BUFG</arg>&gt; is placed at site &lt;<arg fmt="%s" index="2">BUFGMUX1</arg>&gt;. The IO component &lt;<arg fmt="%s" index="3">F_SCK</arg>&gt; is placed at site &lt;<arg fmt="%s" index="4">P70</arg>&gt;.  This will not allow the use of the fast path between the IO and the Clock buffer. This is normally an ERROR but the CLOCK_DEDICATED_ROUTE constraint was applied on COMP.PIN &lt;<arg fmt="%s" index="5">F_SCK.PAD</arg>&gt; allowing your design to continue. This constraint disables all clock placer rules related to the specified COMP.PIN. The use of this override is highly discouraged as it may lead to very poor timing results. It is recommended that this error condition be corrected in the design.
</msg>

<msg type="info" file="Timing" num="2761" delta="unknown" >N/A entries in the Constraints list may indicate that the constraint does not cover any paths or that it has no requested value.</msg>

<msg type="warning" file="Route" num="0" delta="unknown" >CLK Net:<arg fmt="%s" index="1">XLXI_984/CPU_DATAo_not0007</arg> is being routed on general routing resources. If you are trying to use local clocking techniques, evaluate the placement of the clock&apos;s source and loads to ensure it meets the guidelines for local clocking. Otherwise, consider placing this clock on a dedicated clock routing resource. For more information on clock routing resources, see the target architecture&apos;s user guide.
</msg>

<msg type="warning" file="Route" num="0" delta="unknown" >CLK Net:<arg fmt="%s" index="1">XLXI_1000/XLXI_1086/frame_intern</arg> is being routed on general routing resources. If you are trying to use local clocking techniques, evaluate the placement of the clock&apos;s source and loads to ensure it meets the guidelines for local clocking. Otherwise, consider placing this clock on a dedicated clock routing resource. For more information on clock routing resources, see the target architecture&apos;s user guide.
</msg>

<msg type="warning" file="Route" num="0" delta="unknown" >CLK Net:<arg fmt="%s" index="1">XLXI_1011/ena_count&lt;1&gt;</arg> may have excessive skew because <arg fmt="%d" index="2">1</arg> CLK pins and <arg fmt="%d" index="3">16</arg> NON_CLK pins failed to route using a CLK template.
</msg>

<msg type="warning" file="Route" num="0" delta="unknown" >CLK Net:<arg fmt="%s" index="1">XLXI_1000/XLXI_1135/yvalid</arg> may have excessive skew because <arg fmt="%d" index="2">1</arg> CLK pins and <arg fmt="%d" index="3">8</arg> NON_CLK pins failed to route using a CLK template.
</msg>

<msg type="info" file="Timing" num="2761" delta="unknown" >N/A entries in the Constraints list may indicate that the constraint does not cover any paths or that it has no requested value.</msg>

</messages>

