https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #59 from John Paul Adrian Glaubitz ---
(In reply to John Paul Adrian Glaubitz from comment #58)
> Oh, and according to the Debian changelog, it must be a regression that was
> introduced somewhere between r218987 and r222750 of the gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #58 from John Paul Adrian Glaubitz ---
Oh, and according to the Debian changelog, it must be a regression that was
introduced somewhere between r218987 and r222750 of the gcc-4.9 branch.
Currently, the buildds did not build any snaps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
Oleg Endo changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #56 from John Paul Adrian Glaubitz ---
(In reply to Oleg Endo from comment #55)
> Can we close this as fixed?
Yes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #55 from Oleg Endo ---
Can we close this as fixed?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #54 from John Paul Adrian Glaubitz ---
(In reply to Kazumoto Kojima from comment #53)
> (In reply to Kazumoto Kojima from comment #52)
> We are lucky:-) The test for backport of PR66780 patch for gcc-5 was done
> and we get a chance
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #53 from Kazumoto Kojima ---
(In reply to Kazumoto Kojima from comment #52)
We are lucky:-) The test for backport of PR66780 patch for gcc-5 was done
and we get a chance to commit it:
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg008
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #52 from Kazumoto Kojima ---
(In reply to Kazumoto Kojima from comment #51)
BTW, I've already committed the patch in c#37 for gcc-5 for this PR.
The backport patch for PR/66780 is still in test for gcc-5.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #51 from Kazumoto Kojima ---
(In reply to Matthias Klose from comment #49)
> Kaz, please could you propose these patches for 5.2 too, even if the branch
> is currently frozen?
It's too late, I think.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #50 from John Paul Adrian Glaubitz ---
(In reply to Matthias Klose from comment #49)
> Kaz, please could you propose these patches for 5.2 too, even if the branch
> is currently frozen?
Btw, the main reason for most of these segfault
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #49 from Matthias Klose ---
Kaz, please could you propose these patches for 5.2 too, even if the branch is
currently frozen?
11 matches
Mail list logo