Re: [Monotone-devel] Problems after building monotone

[Justin Patrin]

On 7/19/06, Zack Weinberg <address@hidden> wrote:
> See if you can reproduce at -O0.  -O3 most definitely *is* an extreme
> optimization setting[1], and I'm pretty sure we have
> -fno-strict-aliasing in the default CFLAGS for a reason.  [I don't
> know what it is, though, and I was wondering if it could be taken out
> myself...]

The manual compile I did most certainly didn't have anything but the
default optimization in monotone's build scripts. I've tried both 0.25
and 0.27 at -O0 and it made no difference. -O3 worked fine before for
0.25. Could it be my boost or gcc versions? They were both likely
updated since I originally installed monotone.

> zw
>
> [1] Anything other than -O0 or -O2 (and more recently -Os) is tested
> orders of magnitude less thoroughly than those few modes.  Also, as a
> general piece of advice, -O3 almost always produces code that is both
> larger and slower than what you get at -O2, especially with gcc 3.x.


--
Justin Patrin