[issue225489] fpectl module is undocumented

Change by admin : -- github: None -> 33578 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue530163] fpectl build on solaris: -lsunmath

Change by admin : -- github: None -> 36264 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue401566] Add fpectl functionality patch for FreeBSD

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue214630] Add fpectl functionality patch for FreeBSD

Change by admin : -- github: None -> 33136 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue401566] Add fpectl functionality patch for FreeBSD

Change by admin : -- github: None -> 33147 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue438773] fpectl is not initiliazed on Windows

Change by admin : -- github: None -> 34703 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue214630] Add fpectl functionality patch for FreeBSD

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue225489] fpectl module is undocumented

Change by admin : -- github: None -> 33578 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29137] Fix fpectl-induced ABI breakage

STINNER Victor added the comment: I created bpo-43250: "[C API] Depreate or remove PyFPE_START_PROTECT() and PyFPE_END_PROTECT()". By the way, I close this issue: there is no activity since 2019. -- status: open -> closed ___ Python tracker

[issue15682] PEP 3121 refactoring applied to fpectl module

STINNER Victor added the comment: Module removed in Python 3.7: bpo-29137. -- nosy: +vstinner resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Fix fpectl-induced ABI breakage ___ Python tra

[issue29137] Fix fpectl-induced ABI breakage

STINNER Victor added the comment: I propose PR 17231: "PyFPE_START_PROTECT() and PyFPE_END_PROTECT() macros are empty: they do nothing for one year (since commit 735ae8d), stop using them." -- nosy: +vstinner ___ Python tracker

[issue29137] Fix fpectl-induced ABI breakage

Nathaniel Smith added the comment: Yes, they're intentionally retained as no-ops, so that it remains possible to load old extensions that were compiled against an fpe build and refer to those symbols. Is there a problem? -- ___

[issue29137] Fix fpectl-induced ABI breakage

Matthias Klose added the comment: reopening. this patch introduces two new symbols unconditionally, which were not defined for non-pyfpe builds before (PyFPE_counter and PyFPE_jbuf). -- nosy: +doko status: closed -> open ___ Python

[issue29137] Fix fpectl-induced ABI breakage

Change by Benjamin Peterson : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue29137] Fix fpectl-induced ABI breakage

Benjamin Peterson <benja...@python.org> added the comment: New changeset 735ae8d139a673b30b321dc10acfd3d14f0d633b by Benjamin Peterson (Nathaniel J. Smith) in branch 'master': bpo-29137: Remove fpectl module (#4789) https://github.com/python/cpython/

[issue29137] Fix fpectl-induced ABI breakage

Nathaniel Smith added the comment: Ping -- anyone up for reviewing PR 4789? https://github.com/python/cpython/pull/4789 It's pretty straightforward, and I figure better to ping now and beat the end-of-month rush :-). Also, it has an autoconf refresh in it, so it's likely to

[issue29137] Fix fpectl-induced ABI breakage

Change by Serhiy Storchaka : -- nosy: +rhettinger, stutzbach, twouters ___ Python tracker ___

[issue29137] Fix fpectl-induced ABI breakage

Change by Nathaniel Smith : -- keywords: +patch pull_requests: +4689 stage: -> patch review ___ Python tracker ___

[issue29137] Fix fpectl-induced ABI breakage

types (or directly in gdb), and then running the program under gdb to get a backtrace where the SIGFPE was delivered? Is that correct? Or did your debugging depend on the specific fpectl machinery for responding to that signal? > PS. I would volunteer to fix it and maintain it, assuming I have some

[issue29137] Fix fpectl-induced ABI breakage

Dima Pasechnik added the comment: PS. I would volunteer to fix it and maintain it, assuming I have some modest funding to support such an activity. (What precisely "it" should be, is another question). -- ___ Python tracker

[issue29137] Fix fpectl-induced ABI breakage

). (Without using it we were pulling out our hair for weeks over this) https://trac.sagemath.org/ticket/22799#comment:103 Thanks goodness that fpectl@FreeBSD is easy to fix by commenting out a couple of "fpresetsticky(fpgetsticky());" lines---fpresetsticky() is not available on 64-bit

[issue29137] Fix fpectl-induced ABI breakage

Nathaniel Smith added the comment: Another option you might want to consider is proposing to add a proper fpu control flag setting/checking API to the math module. -- ___ Python tracker

[issue29137] Fix fpectl-induced ABI breakage

Nathaniel Smith added the comment: Also fixing the abi issues that started this, and probably making an argument for why it makes sense for all of cpython's built-in float operations to check the fpu flags, and to do so using a weird longjmp-based mechanism that only some platforms support.

[issue29137] Fix fpectl-induced ABI breakage

Dima Pasechnik added the comment: @njs: Fixing this entails switching over from ieeefp to fenv, right? Looks doable, although not trivial. It might potentially be useful for various numerics, IMHO. -- ___ Python tracker

[issue29137] Fix fpectl-induced ABI breakage

Nathaniel Smith added the comment: @Dima: are you volunteering to fix and maintain it? I can see why it's useful to have some way to get at the fpu flags, but I don't see how fpectl specifically helps with that issue, and fpectl has always been broken on x86-64

[issue29137] Fix fpectl-induced ABI breakage

Dima Pasechnik added the comment: While fpectl might be a bit rusty, this is a priceless tool in debugging situations, where one needs to identify components that do something wrong to FPU, see e.g. https://github.com/numpy/numpy/issues/9007 and the related https://trac.sagemath.org/ticket

[issue29137] Fix fpectl-induced ABI breakage

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___

[issue29137] Fix fpectl-induced ABI breakage

Nick Coghlan added the comment: Ah, cool - I didn't know that Debian built with fpectl enabled by default. In that case, +1 for: - low maintenance ABI and API compatibility shims that are kept around indefinitely (since they leaked into the limited API/stable ABI) but don't actually do

[issue29137] Fix fpectl-induced ABI breakage

Nathaniel Smith added the comment: > At that point, does it actually make sense to provide the shims? Or should we > instead just add the deprecation warnings and say "Don't use the > --with-fpectl option, as it doesn't work properly, and breaks ABI > compatibility for extens

[issue29137] Fix fpectl-induced ABI breakage

and the next 2.7 release At that point, does it actually make sense to provide the shims? Or should we instead just add the deprecation warnings and say "Don't use the --with-fpectl option, as it doesn't work properly, and breaks ABI compatibility for extension modules built with that P

[issue29137] Fix fpectl-induced ABI breakage

Changes by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list

[issue29137] Fix fpectl-induced ABI breakage

New submission from Nathaniel Smith: It turns out that CPython built with --with-fpectl has a different ABI than CPython built without --with-fpectl (which is the default). Specifically, if you have an extension module built against a --with-fpectl CPython, and it uses the PyFPE_{START,END

[issue15682] PEP 3121 refactoring applied to fpectl module

Changes by Robin Schreiber robin.schrei...@me.com: -- keywords: +pep3121 -patch nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15682 ___

[issue15682] PEP 3121 refactoring applied to fpectl module

New submission from Robin Schreiber: Changes proposed in PEP3121 have now been applied to the fpectl module! -- components: Extension Modules files: fpectl_pep3121_v0.patch keywords: patch messages: 168355 nosy: Robin.Schreiber priority: normal severity: normal status: open title: PEP

[ python-Bugs-1556261 ] Move fpectl elsewhere in library reference

thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: Python 2.5 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Michael Hoffman (hoffmanm) Assigned to: Georg Brandl (gbrandl) Summary: Move fpectl elsewhere in library

[ python-Bugs-1556261 ] Move fpectl elsewhere in library reference

of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: Python 2.5 Status: Open Resolution: None Priority: 5 Submitted By: Michael Hoffman (hoffmanm) Assigned to: Nobody/Anonymous (nobody) Summary: Move fpectl elsewhere

[ python-Bugs-872265 ] fpectl module needs updating

thread, including the initial issue submission, for this request, not just the latest update. Category: Python Library Group: Python 2.3 Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: Steve Chaplin (stevech) Assigned to: Nobody/Anonymous (nobody) Summary: fpectl module needs updating

[ python-Bugs-872175 ] README build instructions for fpectl

, including the initial issue submission, for this request, not just the latest update. Category: Build Group: Feature Request Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: Steve Chaplin (stevech) Assigned to: Nobody/Anonymous (nobody) Summary: README build instructions for fpectl

[ python-Bugs-872175 ] README build instructions for fpectl

thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: Feature Request Status: Closed Resolution: Fixed Priority: 5 Submitted By: Steve Chaplin (stevech) Assigned to: Nobody/Anonymous (nobody) Summary: README build instructions for fpectl

Re: fpectl

Thanks for this answer. Did you forward this info to python-dev ? Cheers, SB -- http://mail.python.org/mailman/listinfo/python-list

Re: fpectl

On Tue, Apr 19, 2005 at 02:05:11AM -0700, Sébastien Boisgérault wrote: Thanks for this answer. Did you forward this info to python-dev ? I created a patch on the sf tracker. It's been responded to by several developers. You can read what they said there. http://python.org/sf/1185529 Jeff

Re: fpectl

Good ! And thanks for the link. I had not noticed the warning fpectl module is dangerous before. I am a bit sad that the floating-point issue is disappearing from the *active topics* list ... Cheers, SB -- http://mail.python.org/mailman/listinfo/python-list

fpectl

Hi all, Can anybody tell me why I can't load the fpectl module in my Python interpreter: import fpectl Traceback: ... ... ImportError: No module named fpectl My platform is Linux (Mandrake 10.x) + Python2.4, built from the (python.org) sources and configured with the --with-fpectl option. Any

Re: fpectl

Sébastien Boisgérault wrote: Hi all, Can anybody tell me why I can't load the fpectl module in my Python interpreter: import fpectl Traceback: ... ... ImportError: No module named fpectl My platform is Linux (Mandrake 10.x) + Python2.4, built from the (python.org) sources

Re: fpectl

Matt wrote: Sébastien Boisgérault wrote: My platform is Linux (Mandrake 10.x) I'm assuming that means you can't use it on a Windows platform It's harsh to say Mandrake is a Windows platform. ;o) -- http://mail.python.org/mailman/listinfo/python-list

Re: fpectl

It looks like the automatic build of the 'fpectl' module was broken somewhere along the line, perhaps when the transition from Modules/Setup to setup.py took place. Once I made the change below and rebuilt, I got the fpectl module. Furthermore, it appeared to do something on my Linux/x86 system

[ python-Bugs-530163 ] fpectl build on solaris: -lsunmath

Fix Priority: 5 Submitted By: Anthony Baxter (anthonybaxter) Assigned to: Nobody/Anonymous (nobody) Summary: fpectl build on solaris: -lsunmath Initial Comment: This is on Solaris 2.7, with gcc2.95.2 Observed on both the trunk and the release22 branch. By default, the configure/setup stuff isn't