[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: GCC var-tracking-assignments: testing and bug reports appreciated



On 09/11/2009 12:03 PM, Alexandre Oliva wrote:
On Sep 11, 2009, John Reiser<jreiser bitwagon com>  wrote:
  <<snip>>
    https://bugzilla.redhat.com/show_bug.cgi?id=521322

This bug was opened before the new GCC.  Exactly *one* kernel build
failed because of the new GCC feature.  I can't find any evidence that
this bug is in any way related with VTA or with the new GCC.

Even though there is no known technical connection between 521322 and the
hiccup with the new GCC, the hiccup got in the way of communicating
and disseminating the work on 521322, by interfering with the normal
process of daily rawhide.


So how do you get from “GCC debug info was fixed, with one kernel build
and a few hours as casualty” to “two-day slip in rawhide kernels”?

Yes, 521322 was opened before the new GCC.  But fully fixing 521322 (making
the software work for my card) has been delayed because the new GCC
disrupted the process despite not being an immediate impediment.

The first part of 521322 was essentially the same as 520766, and it was
marked as duplicate in https://bugzilla.redhat.com/show_bug.cgi?id=521322#c7
with the fix https://bugzilla.redhat.com/show_bug.cgi?id=520766#c4.

So I tried to test the fix immediately, by retrieving it directly from Koji
late Wednesday afternoon (PDT).  That build kernel-2.6.31-0.218.rc9.git2.fc12
failed.  The build of the next kernel-2.6.31-0.219.rc9.git2.fc12 succeeded.
Yes it did fix the 520766-like problem for me, but it revealed the next
bug https://bugzilla.redhat.com/show_bug.cgi?id=521322#c8.  That was early
evening PDT on Wednesday.  There had been no Rawhide report that day,
and there was no Rawhide report on Thursday, either, until 2100 PDT,
which is 12 to 16 hours later than expected.  Today's rawhide
still does not fix it: https://bugzilla.redhat.com/show_bug.cgi?id=521322#c13.

The "no external progress" [still broken even though the internal cause
has advanced] from the fix for 520766 on Wednesday until today (Friday)
overlaps closely with "two-day slip in rawhide kernels" from Tuesday morning
until Thursday evening.  To the extent that the GCC hiccup contributed to
the lack of a Rawhide report kernel in that interval, then GCC is a direct cause.
If I had relied solely on Rawhide report, then there would have been
no progress from Tuesday morning to Thursday evening.

--


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]