On Sat, Aug 06, 2005 at 09:27:06PM -0700, Seth Brutzman wrote:
i spent quite a while searching through lists and bug reports, trying to find another instance of this problem, both to find a solution and to ensure that i won't be duping a bug. haven't come across one yet.
Very good, thanks.
i went ahead and compiled with --disable-mmx as Alexandre suggested, and it built flawlessly. this, however, seems a poor workaround as i'm running a p4, rather than an amd, so mmx should be a given.
Cool. Yeah like I mentioned, we have control code to disable the mmx in cases where it causes problems. It's unusual for there be problems with this - your case is the first I've personally heard about. You've got a good point that it's unusual. I (and of course many others) have compiled on p4s, so you've got an "interesting" case as they say.
here's my new question: how much of a performance difference is there between mmx enabled and disabled builds? and, should i report this as a genuine bug, or let it go since it's an isolated compile error rather than a program error?
This is a good question. My guess is that it makes a difference, but I think this is definitely worth testing; I've been curious about it myself.
It would be definitely be worth listing in the bug tracker, including your work-around, both for people who might run into it in the future, and for establishing a thread in which the root cause can be explored.
either way, i'm still going to try and find the problem.
Excellent, thanks. Build issues are annoying and the fewer of them (even unusual corner cases), the better off we'll all be in the long haul.
Bryce