A question about Corbit version engines

[Al Levine]

Geschrieben von: / Posted by: Al Levine at 14 June 2000 15:40:36:
Dann,
I was just curious what you add or remove from the authors versions of the different engines you have compiled to gain the speed increases you obtain. What exactly are you changing? I am not a programmer so be as simple in your explanation as you can.
Thanks,
Al

[Dann Corbit]

Geschrieben von: / Posted by: Dann Corbit at 14 June 2000 19:47:34:
Als Antwort auf: / As an answer to: A question about Corbit version engines geschrieben von: / posted by: Al Levine at 14 June 2000 15:40:36:

Dann,
I was just curious what you add or remove from the authors versions of the different engines you have compiled to gain the speed increases you obtain. What exactly are you changing? I am not a programmer so be as simple in your explanation as you can.

Many of the changes I tend to make are not for performance. If Lint squeaks about something I try to fix it. Lint is a static code analysis tool that will find many minor problems. Some of them are probably not really a problem, but if the cost is small, I fix them anyway.
I use BoundsChecker to ensure that all objects are properly initialized with a sensible value when used and that array bounds are obeyed.
I run profile sessions with TrueTime to look for slow spots.
I target special combinations of optimization flags for modern processors.
I try to make non ANSI/ISO C code conform to the standard if it still is equally functional.
I tend to make pathnames larger (to FILENAME_MAX as described in stdlib.h).
A bunch of odds and ends like that. Really, I can't produce an accurate list, since I do different things every time.


My FTP site

[Al Levine]

Geschrieben von: / Posted by: Al Levine at 14 June 2000 20:37:03:
Als Antwort auf: / As an answer to: Re: A question about Corbit version engines geschrieben von: / posted by: Dann Corbit at 14 June 2000 19:47:34:

Dann,
I was just curious what you add or remove from the authors versions of the different engines you have compiled to gain the speed increases you obtain. What exactly are you changing? I am not a programmer so be as simple in your explanation as you can.

Many of the changes I tend to make are not for performance. If Lint squeaks about something I try to fix it. Lint is a static code analysis tool that will find many minor problems. Some of them are probably not really a problem, but if the cost is small, I fix them anyway.
I use BoundsChecker to ensure that all objects are properly initialized with a sensible value when used and that array bounds are obeyed.
I run profile sessions with TrueTime to look for slow spots.
I target special combinations of optimization flags for modern processors.
I try to make non ANSI/ISO C code conform to the standard if it still is equally functional.
I tend to make pathnames larger (to FILENAME_MAX as described in stdlib.h).
A bunch of odds and ends like that. Really, I can't produce an accurate list, since I do different things every time.