Re: Lilypond miscompiled on Fedora 17

[David Kastrup]

Pavel Roskin <address@hidden> writes:

> Quoting David Kastrup <address@hidden>:
>
>> That would have been my most likely guess.  Probably the "min" function
>> call.
>
> You are absolultely right!  I was able to work around the gcc bug by
> making a separate function for Moment comparison and using it instead
> of min():
>
> Moment
> min_moment (Moment m1, Moment m2)
> {
>   return min (m1, m2);
> }

What happens if you declare this

(Moment const &m1, Moment const &m2)

...


-- 
David Kastrup