ia64 libjava java-signal.h build failure

Mark Mitchell mark@codesourcery.com
Mon Apr 23 10:13:00 GMT 2001


>>>>> "Alexandre" == Alexandre Oliva <aoliva@redhat.com> writes:

    Alexandre> Also, it bothers me that what seems to me like the
    Alexandre> obvious course of action doesn't even seem right to you
    Alexandre> :-)

Well, even reasonable people sometimes disagree.

The basic core of our disagreement is this philosophy:

    Alexandre> timing; the earlier we enable it, the earlier we'll get
    Alexandre> reports in case of failure and the earlier we'll get

Your approach is aggressive -- assume it works, and then disable it
where it doesn't.  Mine is conservative -- assume it's broken, and
enable it where it's known to work.

In my my opinion, your approach is sensible for the mainline -- but
mine is sensible for the branch.

You can rest assured that, based on my experience, if we were building
a compiler for HP or Microsoft or some such -- instead of the FSF --
we wouldn't be having this conversation.  Nothing like this would even
be considered at this late a date.  

We are only waiting for Richard/Benjamin's merge, a few bug fixes, and
final testing; there is nothing major between us and and the release.

I do not want to take any unncessary risks at this point.

One of the reasons is that I am running out of time to work on this
release -- although I can work on the next one when this one is done.
That means that we need to ship relatively quickly, or I will turn
into a pumpkin, which I am egotistical enough to think is probably not
a good thing at this point.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com



More information about the Gcc-bugs mailing list