| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 447.1 | moved to C7Bugs 1341 | DECWET::BERG | | Tue Jan 28 1997 16:00 | 0 |
| 447.2 | 6 minutes to compile on DPW200i, where is C7Bugs? | AXPBIZ::bpda02::PHEBERT | Mr. Knobby rides again. and again and again... | Thu Feb 06 1997 09:42 | 19 |
| The following reflects compile time for current_entity.cpp observed on
Digital'd DPW200i in San Rafael. This shows a compile time of 6 minutes,
significantly different from what was seen at DECWEST on a P6 200 system
(~30 minutes) and wildly less than an Alpha 266 station, which takes over
an hour. What could account for such a broad variance in the compile times
we are seeing?
>Fixmake Studio callup parameters: PATHS
>
>Thu Jan 30 16:19:03 1997
>Target: HEIDI_whip, @G:\CoolWhip\whip\source\whip.mak.
>current_entity.cpp
> Creating library G:\CoolWhip\heidi\lib\i386\Debug\dswhip.lib and object
>G:\CoolWhip\heidi\lib\i386\Debug\dswhip.exp
>Target: HEIDI_whip, Result: SUCCESS.
>
>Thu Jan 30 16:25:19 1997
Also, where is C7Bugs?
|
| 447.3 | | DECWET::THOMAS | Bug-for-bug compatible with Intel | Tue Feb 11 1997 09:00 | 16 |
| +++ Also, where is C7Bugs?
It's a member-only notesfile for the compiler team. What Mike meant was
that he has reported the problem there. He thinks it's a memory leak in
c2.exe, and they are investigating it.
+++ The following reflects compile time for current_entity.cpp observed on
+++ Digital'd DPW200i in San Rafael. This shows a compile time of 6 minutes,
+++ significantly different from what was seen at DECWEST on a P6 200 system
+++ (~30 minutes) and wildly less than an Alpha 266 station, which takes over
+++ an hour. What could account for such a broad variance in the compile times
+++ we are seeing?
Is this still an Internal Error? If not, can you move it to a new note
so we can keep track of it? Or let me know by mail and I'll do it.
Thanks ... Mike
|
| 447.2 | | DECWET::THOMAS | Bug-for-bug compatible with Intel | Wed Feb 12 1997 15:50 | 8 |
| >>> Also, where is C7Bugs?
It's a member-only notesfile for the compiler team. What Mike meant was
that he has reported the problem there. He thinks it's a memory leak in
c2.exe, and they are investigating it.
Since .2 is a new problem, I've moved it to 464.
Thanks ... Mike
|