" /> Status for Andrew DeFaria: January 30, 2005 - February 5, 2005 Archives

« January 23, 2005 - January 29, 2005 | Main | February 6, 2005 - February 12, 2005 »

February 3, 2005

Finishing build note

  • Finished build note for 012405
  • Experimented more with VCG

Posted by at 4:44 PM |

February 2, 2005

cvs_report updates/common build

  • Changed cvs_report.pl to better handle branches
  • Build common for 012405

cvs_report.pl changes

The changes to cvs_report.pl involved changing ProcessECRs to look for the start and stop revision numbers in the log. The CVS log has entries like the following:

$ cvs log Makefile | grep ^revision
revision 1.9
revision 1.8
revision 1.7
revision 1.6
revision 1.5
revision 1.4
revision 1.3
revision 1.2
revision 1.1
revision 1.1.2.4
revision 1.1.2.3
revision 1.1.2.2
revision 1.1.2.1
revision 1.3.4.1
revision 1.3.2.2
revision 1.3.2.1

Thus if the from tag is pointing to revision 1.1.2.1 and the to_tag is pointing to revision 1.1.2.4 cvs_report.pl now skips all versions until 1.1.2.4 then picks up ECR numbers from there.

Building common

First check out the top of trunk of ats:

  1. cd <build_area>/LYNXOS_500/work_area/tst
  2. export CVSROOT=:pserver:int@t3.lynx.com:/cvs/tst-cvs
  3. cvs login (Enter the password)
  4. Check out the top of trunk of ats (cvs checkout ats)
  5. Set a tag for ats (e.g. Lion_common_<mmddyy>). sually we will tag the ATS as the same date as LynxOS build.
  6. Change directory to your build tree - int_tools area and modify the __profile.exp to set the correcty ATS tag that just tagged if it is not the same as lynxos build as defined.
  7. Modify the START for ATS process. 
    steps_com=" 1 2    3";
echo "=== Starting common ==="
startit.exp common dummy     $steps_com  >> LOGS/common.log 2>&1 &
  8. Run the ./START

Posted by at 4:49 PM |

February 1, 2005

CVSR/Toolchain

  • Worked on CVS Report section of web site
  • Attempting to determine what ECRs were picked up for the toolchain. Found what I think might be a CVS tagging issue

Either I really just don't understand CVS branching or perhaps we have an error in tagging. I have written a Perl script that will report the ECRs involved between two different CVS tags. When I run this script on the toolchain, comparing tags Lion_com3_2_2_120204 -> Lion_com3_2_2_121604 I see odd results. I believe that the only real ECR involved here is ECR #23084. The following appears in Quintus for that ECR:

/cvs/gcc-cvs/toolchain/src/ChangeLog.lynx,v  <--  ChangeLog.lynx
new revision: 1.25.2.31; previous revision: 1.25.2.30

/cvs/gcc-cvs/toolchain/src/gcc/config/lynx.c,v  <--  lynx.c
new revision: 1.2.2.1; previous revision: 1.2

[Check-ins] on trunk

/cvs/gcc-cvs/toolchain/src/gcc/ChangeLog.lynx,v  <--  ChangeLog.lynx
new revision: 1.7; previous revision: 1.6

/cvs/gcc-cvs/toolchain/src/gcc/config/lynx.c,v  <--  lynx.c
new revision: 1.3; previous revision: 1.2

However I also notice the following WRT the file src/ChangeLog.lynx:

$ cvs log toolchain/src/ChangeLog.lynx
...
    Lion_com3_2_2_121604: 1.25.2.31
...
    Lion_com3_2_2_120604: 1.25.3.28
...
revision 1.25.2.31
date: 2004/12/15 23:48:49;  author: anemet;  state: Exp;  lines: +6 -0
        ECR 23084
...
revision 1.25.2.30
date: 2004/12/14 15:28:22;  author: orepin;  state: Exp;  lines: +17 -0
        ECR 22875
...
revision 1.25.2.29
date: 2004/12/14 09:26:25;  author: orepin;  state: Exp;  lines: +8 -0
        ECR 22805
...
revision 1.25.2.28
date: 2004/11/23 15:35:16;  author: aneyman;  state: Exp;  lines: +8 -0
        ECR 22989
...
$

So, to me, the ECRs that changed between the CVS tags of Lion_com3_2_2_120204 and Lion_com3_2_2_121604 WRT src/ChangeLog.lynx would be

  1. 23084
  2. 22875
  3. 22805

(I assume that ECR #22989 was included with the previous toolchain).

Or am I just looking at this the wrong way?

Futhermore, the other files associated with, for example, ECR #22875, are:

  • toolchain.cvsr/src/gdb/gdbtypes.h: 1.2.4.1
  • toolchain.cvsr/src/ChangeLog.lynx: 1.25.2.30
  • toolchain.cvsr/src/gdb/gdbtypes.c: 1.2.4.1
  • toolchain.cvsr/src/gdb/config/i386/tm-i386lynx.h: 1.2.4.3

Yet, other than ChangeLog.lynx, all other files have tags that suggest that nothing else changed! For example, gdbtypes.h has Lion_com3_2_2_120204 pointing to revision 1.2 and Lion_com3_2_2_121604 also pointing to 1.2! Likewise for gdbtypes.c and config/i386/tm-i386lynx.h. Is this a tagging error?

Posted by at 4:48 PM |

January 31, 2005

1/31

  • Added html capability to cvs_report.pl

Posted by at 4:48 PM |