Rahul <rahulrajaram2...@gmail.com> added the comment: Thanks for your response. I'll follow up with GCC.
On Nov 28, 2017 14:48, "STINNER Victor" <rep...@bugs.python.org> wrote: > > STINNER Victor <victor.stin...@gmail.com> added the comment: > > "internal compiler error" is a bug in GCC, not in Python. Please follow > instructions in the error message: > > Please submit a full bug report, > with preprocessed source if appropriate. > See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions. > > See https://gcc.gnu.org/bugs/ and https://gcc.gnu.org/ > > It would help if you can simplify the code to reproduce the bug without > Python. > > I close the issue since it's a bug in GCC, not in Python. > > ---------- > nosy: +vstinner > resolution: -> third party > stage: -> resolved > status: open -> closed > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue32161> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32161> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
