Kevin P. Fleming 187f6d485a the gcc optimizer frequently finds broken code (use of uninitalized variables, unreachable code, etc.), which is good. however, developers usually compile with the optimizer turned off, because if they need to debug the resulting code, optimized code makes that process very difficult. this means that we get code changes committed that weren't adequately checked over for these sorts of problems. ...

with this build system change, if (and only if) --enable-dev-mode was used and DONT_OPTIMIZE is turned on, when a source file is compiled it will actually be preprocessed (into a .i or .ii file), then compiled once with optimization (with the result sent to /dev/null) and again without optimization (but only if the first compile succeeded, of course).

while making these changes, i did some cleanup work in Makefile.rules to move commonly-used combinations of flag variables into their own variables, to make the file easier to read and maintain



git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@157859 65c4cc65-6c06-0410-ace0-fbb531ad65f3

2008-11-19 21:34:47 +00:00

..

localtime.c

improve header inclusion process in a few small ways:

2008-09-27 15:00:48 +00:00

Makefile

the gcc optimizer frequently finds broken code (use of uninitalized variables, unreachable code, etc.), which is good. however, developers usually compile with the optimizer turned off, because if they need to debug the resulting code, optimized code makes that process very difficult. this means that we get code changes committed that weren't adequately checked over for these sorts of problems.

2008-11-19 21:34:47 +00:00

private.h

Working on issue #10531 exposed a rather nasty 64-bit issue on ast_mktime, so we

2007-09-12 20:12:06 +00:00

test.c

merge new_loader_completion branch, including (at least):

2006-08-21 02:11:39 +00:00

tzfile.h

Oops, wrong location for FreeBSD zone files

2007-09-12 21:28:33 +00:00