➜
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.
Created on 2017-11-28 21:59 by rahulrajaram, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| python_2_7_14__configure_output | rahulrajaram, 2017-11-28 21:59 | Output of ./configure | ||
| Messages (4) | |||
|---|---|---|---|
| msg307176 - (view) | Author: Rahul (rahulrajaram) | Date: 2017-11-28 21:59 | |
Attempt to `make` Python 2.7.14 on Ubuntu 16.04/GCC 5.4 throws the following error: Objects/floatobject.c: In function ‘PyFloat_GetMax’: Objects/floatobject.c:59:5: internal compiler error: Illegal instruction return DBL_MAX; ^ Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions. Makefile:1359: recipe for target 'Objects/floatobject.o' failed make: *** [Objects/floatobject.o] Error 1 |
|||
| msg307184 - (view) | Author: STINNER Victor (vstinner) *  |
Date: 2017-11-28 22:48 | |
"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. |
|||
| msg307186 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2017-11-28 22:48 | |
Once you reported the bug to GCC, please add a link to your bug report here, please ;-) |
|||
| msg307188 - (view) | Author: Rahul (rahulrajaram) | Date: 2017-11-28 23:04 | |
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 |
| 2022-04-11 14:58:54 | admin | set | github: 76342 |
| 2017-11-28 23:04:25 | rahulrajaram | set | messages: + msg307188 |
| 2017-11-28 22:48:34 | vstinner | set | messages: + msg307186 |
| 2017-11-28 22:48:12 | vstinner | set | status: open -> closed nosy: + vstinner messages: + msg307184 resolution: third party stage: resolved |
| 2017-11-28 21:59:42 | rahulrajaram | create | |