public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94809] [8/9 Regression] Different results between gcc-9 and gcc-6 Date: Wed, 16 Sep 2020 19:21:14 +0000 [thread overview] Message-ID: <bug-94809-4-emfhgDsFag@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94809-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94809 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:522022361984407ebc84cde22bdbd199261d0443 commit r9-8888-g522022361984407ebc84cde22bdbd199261d0443 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 28 11:26:56 2020 +0200 tree: Fix up TREE_SIDE_EFFECTS on internal calls [PR94809] On the following testcase, match.pd during GENERIC folding changes the -1U / x < y into __imag__ .MUL_OVERFLOW (x, y), but unfortunately unlike for normal calls nothing sets TREE_SIDE_EFFECTS on the call. There is the process_call_operands function that non-internal call creation calls and it is usable for internal calls too, e.g. TREE_SIDE_EFFECTS is derived from checking whether the call has side-effects (non-ECF_{CONST,PURE}; we have those for internal calls) and from whether any of the arguments has TREE_SIDE_EFFECTS. 2020-04-28 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/94809 * tree.c (build_call_expr_internal_loc_array): Call process_call_operands. * gcc.c-torture/execute/pr94809.c: New test. (cherry picked from commit 34f6b14ff33e0c64b3a4a1a2cd871df715d69151)
next prev parent reply other threads:[~2020-09-16 19:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-27 20:54 [Bug c/94809] New: " k.even-mendoza at imperial dot ac.uk 2020-04-27 21:03 ` [Bug c/94809] [8/9/10 Regression] " redi at gcc dot gnu.org 2020-04-27 21:03 ` redi at gcc dot gnu.org 2020-04-27 21:06 ` redi at gcc dot gnu.org 2020-04-27 22:24 ` jakub at gcc dot gnu.org 2020-04-27 22:31 ` [Bug tree-optimization/94809] " jakub at gcc dot gnu.org 2020-04-28 7:50 ` rguenth at gcc dot gnu.org 2020-04-28 7:50 ` rguenth at gcc dot gnu.org 2020-04-28 9:28 ` cvs-commit at gcc dot gnu.org 2020-04-28 9:29 ` [Bug tree-optimization/94809] [8/9 " jakub at gcc dot gnu.org 2020-09-16 19:21 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-17 17:38 ` jakub at gcc dot gnu.org 2022-03-19 4:16 ` pinskia 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-94809-4-emfhgDsFag@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).