https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|4.9.2 |4.8.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
--- Comment #9 from Jonathan Wakely ---
Author: redi
Date: Thu Aug 28 16:22:21 2014
New Revision: 214682
URL: https://gcc.gnu.org/viewcvs?rev=214682&root=gcc&view=rev
Log:
2014-08-28 Samuel Bronson
Backport r212453 from trunk
2014-07
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|4.10.0 |4.9.2
--- Comment #8 from Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
--- Comment #7 from Jonathan Wakely ---
Author: redi
Date: Mon Aug 4 18:50:30 2014
New Revision: 213604
URL: https://gcc.gnu.org/viewcvs?rev=213604&root=gcc&view=rev
Log:
2014-08-04 Samuel Bronson
Backport r212453 from trunk
2014-07
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
--- Comment #5 from Jonathan Wakely ---
Author: redi
Date: Fri Jul 11 13:43:07 2014
New Revision: 212453
URL: https://gcc.gnu.org/viewcvs?rev=212453&root=gcc&view=rev
Log:
2014-07-11 Samuel Bronson
Matthias Klose
PR libstdc++/5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
--- Comment #4 from Bruce Merry ---
Incidentally, the workaround I have been using is to just run the script
through 2to3. Since Python only tells you things have gone wrong when you
execute the code I can't guarantee that this fixes everything,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
--- Comment #3 from Daniel Gutson
---
Please do not close this issue.(In reply to Bruce Merry from comment #1)
> I've now realised that this is actually just the tip of the iceberg - I
> suspect that libstdc++'s pretty printers aren't Python 3 r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
GonzaloBonigo changed:
What|Removed |Added
CC||gonzalo.bonigo@tallertechno
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
--- Comment #1 from Bruce Merry ---
I've now realised that this is actually just the tip of the iceberg - I suspect
that libstdc++'s pretty printers aren't Python 3 ready, while Ubuntu is
shipping a gdb linked to libython 3.3. Feel free to close i
10 matches
Mail list logo