This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

wrong-code regressions review


So, the bugs I worry about most are wrong-code regressions.  :-)

What strikes me most about these 25 bugs is the ones which appear
close to being fixed, but have sort of stalled.

Appear stalled (5):
17913:
  Patch available, needs global maintainer review
17053:
  Collect2 bug.  DJE said in August that he was developing a fix; no
  news since then.
18257:
  Tentative patch in October, no news since then
18191:
  Should default initializers be produced in the front end?  If so,
  this should have its component changed and be cloned.
18019:
  Pentium4.  Jan said he would write a patch "today" on the 2nd, no news
  since then
13300:
  "Withdrawn" patches, because of lack of review.  Still needed.  :-(

Appear in good shape (4):
15486:
  Fixed, fix being committed :-)
18666:
  Probably not-a-bug
18888:
  Jeff Law is actively working on it, I think.
18665:
  Patches in progress, should be fixed soon

Unknown (8):
17949:
  IVOPTS alignment bug.
18241:
  Not tracked down yet.
18628:
  Difficult interaction between passes, needs a CFG guru
18897:
  Analyzed, no patch yet
18785:
  Not much progress yet
17603:
  Not yet tracked down.
18916:
  No idea.
18987:
  New, no idea.

Don't look like anyone cares (7):
10692:
  Nobody's looking at it because nobody maintains m68k.  ;-/
14798:
  SH problems; SH maintainers have not looked at it, as far as I can see.
18701, 18330, 18346, 18329:
  MMIX problems, no analysis.
18170:
  No analysis.  m32r maintainer has not commented.

-- 
This space intentionally left blank.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]