"Zach N. Heilig" <[EMAIL PROTECTED]> wrote: > The application for the tests is mpg123. > test mp3 playing time: 373 seconds. [ ... ] > 1) No Optimization > 225.08 real 224.30 user 0.23 sys [ ... ] > 2) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fschedule-insns > -fschedule-insns2 > 141.92 real 141.43 user 0.10 sys What do these timings represent? As you say the mp3 playing time is 373 seconds, but the "real" times vary, the timings don't appear to be the playing/processing of the mp3 file. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- gcc optimizer in -current system ... The Hermit Hacker
- Re: gcc optimizer in -current system ... Sheldon Hearn
- Re: gcc optimizer in -current system ... The Hermit Hacker
- Re: gcc optimizer in -current system ... Sheldon Hearn
- Re: gcc optimizer in -current system ... Alexander Leidinger
- Re: gcc optimizer in -current system ... Sheldon Hearn
- Re: gcc optimizer in -current sy... Luke
- Re: gcc optimizer in -curren... Zach N. Heilig
- Re: gcc optimizer in -cu... Darryl Okahata
- Re: gcc optimizer in -cu... Zach N. Heilig
- Re: gcc optimizer in -current system ... The Hermit Hacker
- Re: gcc optimizer in -current system ... Kris Kennaway
- Re: gcc optimizer in -current system ... Matthew Dillon
- Re: gcc optimizer in -current system ... bsd
- Re: gcc optimizer in -current system ... Dan Nelson
- Re: gcc optimizer in -current system ... bsd
- Re: gcc optimizer in -current system ... Matthew Dillon