diff options
author | Michael Abed <michaelabed@gmail.com> | 2012-02-17 12:08:05 -0500 |
---|---|---|
committer | Michael Abed <michaelabed@gmail.com> | 2012-02-17 12:08:05 -0500 |
commit | 70b77304f37d9681aa3bfa0eb57df0bcfd1aef81 (patch) | |
tree | 48ab397b4072275dbc5a6b2f92a54d3c79e1fdea /_xmsgs/trce.xmsgs | |
parent | 57738e75e221fe61a8f87270b430c0f1c0b8ead5 (diff) | |
download | ec311-lab1-70b77304f37d9681aa3bfa0e.tar.gz ec311-lab1-70b77304f37d9681aa3bfa0e.tar.bz2 ec311-lab1-70b77304f37d9681aa3bfa0e.zip |
Diffstat (limited to '_xmsgs/trce.xmsgs')
-rwxr-xr-x | _xmsgs/trce.xmsgs | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/_xmsgs/trce.xmsgs b/_xmsgs/trce.xmsgs index 120dfa1..80cb2e4 100755 --- a/_xmsgs/trce.xmsgs +++ b/_xmsgs/trce.xmsgs @@ -5,11 +5,11 @@ behavior or data corruption. It is strongly advised that
users do not edit the contents of this file. -->
<messages> -<msg type="info" file="Timing" num="2698" delta="new" >No timing constraints found, doing default enumeration.</msg>
+<msg type="info" file="Timing" num="2698" delta="old" >No timing constraints found, doing default enumeration.</msg>
-<msg type="info" file="Timing" num="2752" delta="new" >To get complete path coverage, use the unconstrained paths option. All paths that are not constrained will be reported in the unconstrained paths section(s) of the report.</msg>
+<msg type="info" file="Timing" num="2752" delta="old" >To get complete path coverage, use the unconstrained paths option. All paths that are not constrained will be reported in the unconstrained paths section(s) of the report.</msg>
-<msg type="info" file="Timing" num="3339" delta="new" >The clock-to-out numbers in this timing report are based on a 50 Ohm transmission line loading model. For the details of this model, and for more information on accounting for different loading conditions, please see the device datasheet.</msg>
+<msg type="info" file="Timing" num="3339" delta="old" >The clock-to-out numbers in this timing report are based on a 50 Ohm transmission line loading model. For the details of this model, and for more information on accounting for different loading conditions, please see the device datasheet.</msg>
</messages> |