> So, we agree on both core issues -- this is not an egcs bug and we should > not do anything to egcs to "fix" this problem. Well, we could add an explanation of the problem to the documentation.