public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arojas at archlinux dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114872] [13/14/15 Regression] Miscompilation with -O2 after commit r13-8037 Date: Mon, 29 Apr 2024 20:05:52 +0000 [thread overview] Message-ID: <bug-114872-4-5tTXP23NOY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114872-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872 --- Comment #7 from Antonio Rojas <arojas at archlinux dot org> --- (In reply to Sam James from comment #5) > Some ideas: > * Could you maybe give a reproducer for the runtime crash? In sage, calling any libgap function in exactly 3 parameters triggers this. For instance: sage: libgap.AbelianGroup(0,0,0) Note that you need Python 3.12 to get the crash (which happens when trying to derefence the null pointer in the newly introduced _Py_IsImmortal function) > * Any chance you'd be willing to try bisect element.i with pragmas to > disable/enable optimisation for chunks of it, to find the miscompiled > function? I have done that. As expected, the problem is in Py_XDECREF. This makes the problem disappear: #pragma GCC push_options #pragma GCC optimize ("O0") static inline void Py_XDECREF(PyObject *op) { if (op != # 797 "/usr/include/python3.12/object.h" 3 4 ((void *)0) # 797 "/usr/include/python3.12/object.h" ) { Py_DECREF(((PyObject*)((op)))); } } #pragma GCC pop_options
next prev parent reply other threads:[~2024-04-29 20:05 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-27 18:57 [Bug c/114872] New: Miscompilation with -O2 after commit 049ec9b981d1f4f97736061d5cf7d0ae990b57d7 arojas at archlinux dot org 2024-04-27 18:59 ` [Bug c/114872] " arojas at archlinux dot org 2024-04-27 19:03 ` pinskia at gcc dot gnu.org 2024-04-27 19:05 ` pinskia at gcc dot gnu.org 2024-04-27 19:06 ` arojas at archlinux dot org 2024-04-27 20:00 ` [Bug tree-optimization/114872] [13/14/15 Regression] Miscompilation with -O2 after commit r13-8037 pinskia at gcc dot gnu.org 2024-04-29 15:53 ` sjames at gcc dot gnu.org 2024-04-29 16:00 ` jakub at gcc dot gnu.org 2024-04-29 20:05 ` arojas at archlinux dot org [this message] 2024-05-01 1:00 ` sjames at gcc dot gnu.org 2024-05-01 1:01 ` sjames at gcc dot gnu.org 2024-05-01 1:01 ` sjames at gcc dot gnu.org 2024-05-01 1:03 ` sjames at gcc dot gnu.org 2024-05-03 11:07 ` dima.pasechnik at cs dot ox.ac.uk 2024-05-03 11:26 ` dima.pasechnik at cs dot ox.ac.uk 2024-05-06 13:53 ` slyfox at gcc dot gnu.org 2024-05-06 17:29 ` jakub at gcc dot gnu.org 2024-05-06 17:59 ` jakub at gcc dot gnu.org 2024-05-06 21:41 ` slyfox at gcc dot gnu.org 2024-05-06 22:08 ` slyfox at gcc dot gnu.org 2024-05-06 22:45 ` dima.pasechnik at cs dot ox.ac.uk 2024-05-07 10:45 ` jakub at gcc dot gnu.org 2024-05-07 11:05 ` slyfox at gcc dot gnu.org 2024-05-07 22:13 ` slyfox at gcc dot gnu.org 2024-05-08 8:18 ` slyfox at gcc dot gnu.org 2024-05-08 8:27 ` rguenth at gcc dot gnu.org 2024-05-08 18:10 ` slyfox at gcc dot gnu.org 2024-05-08 19:17 ` dima.pasechnik at cs dot ox.ac.uk 2024-05-08 19:35 ` pinskia at gcc dot gnu.org 2024-05-08 19:58 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114872-4-5tTXP23NOY@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).