want higher optimization levels result in unsafer binaries).
Fix bug, that causes core dumps when using higher optimization levels
than -O2.
Results with dhrystone 2.1 (1000000 loops):
stock cc (2.7.2.1 from current) : 136k (136xxx)
pgcc-current with -O2 : 138k
pgcc-current with -O6 : 172k
And no coredump anymore. Reason for coredump:
With -O3 cc1 does an register-to-register-copy optimization and it tries
to write some debugging information about what it is doing into a file
that does not exist unless you have instructed cc1 to dump all its
information about its internal state. (From: Sascha Blank)
BTW: PLIST is really coming soon, it's on my todo list ;-)
BTW2: Is Sascha already in the contributors list ? Have to go to work now.
Submitted by: Sascha Blank <blank@sliphost37.uni-trier.de>
