Pavel Roskin <pro...@gnu.org> writes:
> Quoting David Kastrup <d...@gnu.org>:
>
>> 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
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
