This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rahulrajaram
Recipients rahulrajaram, vstinner
Date 2017-11-28.23:04:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPcYN-=QBC50m-Vvo2m2-LKf-2ZWJt1pfk8bNobvwTLKRhQZTQ@mail.gmail.com>
In-reply-to <1511909292.97.0.213398074469.issue32161@psf.upfronthosting.co.za>
Content
Thanks for your response. I'll follow up with GCC.

On Nov 28, 2017 14:48, "STINNER Victor" <report@bugs.python.org> wrote:

>
> STINNER Victor <victor.stinner@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 <report@bugs.python.org>
> <https://bugs.python.org/issue32161>
> _______________________________________
>
History
Date User Action Args
2017-11-28 23:04:25rahulrajaramsetrecipients: + rahulrajaram, vstinner
2017-11-28 23:04:25rahulrajaramlinkissue32161 messages
2017-11-28 23:04:25rahulrajaramcreate