13 messages in com.perforce.jamming[jamming] compile.c: compile_on(): Wh...
FromSent OnAttachments
Ingo Weinhold18 Nov 2002 07:18 
Christopher Seiwald18 Nov 2002 12:28 
Matt Armstrong18 Nov 2002 13:04 
Craig McPheeters18 Nov 2002 13:09 
Matt Armstrong18 Nov 2002 13:44 
Ingo Weinhold18 Nov 2002 16:40 
Christopher Seiwald20 Nov 2002 14:48 
Arnt Gulbrandsen21 Nov 2002 01:27 
Jacob Gorm Hansen21 Nov 2002 01:52 
Ingo Weinhold21 Nov 2002 02:14 
Christopher Seiwald21 Nov 2002 22:30 
Robert Cowham22 Nov 2002 07:27 
Matt Armstrong23 Nov 2002 20:44 
Subject:[jamming] compile.c: compile_on(): Why search()?
From:Christopher Seiwald (seiw@perforce.com)
Date:11/18/2002 12:28:00 PM
List:com.perforce.jamming

| I'm currently doing a bit of profiling to optimize a rather large build | system. And while doing so, I stumbled over the following line in | compile_on(): | | t->boundname = search( t->name, &t->time );

Sure looks bogus to me. I'll tidy it up for jam 2.5. Thanks, and sorry.

I'd be interested in your profiling results. IIRC, the overwhelming time is spent compiling :-), next header file scanning, and then the hash code in hashitem().

Christopher