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/103209] [12 Regression] wrong code at -O1 on x86_64-linux-gnu since r12-4324-g008e7397dad971c0
Date: Fri, 12 Nov 2021 22:56:28 +0000	[thread overview]
Message-ID: <bug-103209-4-yyCDHk6H5f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103209-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103209

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jan Hubicka <hubicka@gcc.gnu.org>:

https://gcc.gnu.org/g:4d2d5565a0953eaa829d10006baf007cf33bab89

commit r12-5217-g4d2d5565a0953eaa829d10006baf007cf33bab89
Author: Jan Hubicka <jh@suse.cz>
Date:   Fri Nov 12 23:55:50 2021 +0100

    Fix wrong code with pure functions

    I introduced bug into find_func_aliases_for_call in handling pure
functions.
    Instead of reading global memory pure functions are believed to write
global
    memory.  This results in misoptimization of the testcase at -O1.

    The change to pta-callused.c updates the template for new behaviour of the
    constraint generation. We copy nonlocal memory to calluse which is correct
but
    also not strictly necessary because later we take care to add nonlocal_p
flag
    manually.

    gcc/ChangeLog:

            PR tree-optimization/103209
            * tree-ssa-structalias.c (find_func_aliases_for_call): Fix
            use of handle_rhs_call

    gcc/testsuite/ChangeLog:

            PR tree-optimization/103209
            * gcc.dg/tree-ssa/pta-callused.c: Update template.
            * gcc.c-torture/execute/pr103209.c: New test.

  parent reply	other threads:[~2021-11-12 22:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 12:17 [Bug tree-optimization/103209] New: [12 Regression] wrong code at -O1 on x86_64-linux-gnu haoxintu at gmail dot com
2021-11-12 13:13 ` [Bug tree-optimization/103209] [12 Regression] wrong code at -O1 on x86_64-linux-gnu since r12-4324-g008e7397dad971c0 marxin at gcc dot gnu.org
2021-11-12 13:17 ` rguenth at gcc dot gnu.org
2021-11-12 13:51 ` hubicka at gcc dot gnu.org
2021-11-12 20:55 ` hubicka at gcc dot gnu.org
2021-11-12 21:03 ` marxin at gcc dot gnu.org
2021-11-12 22:56 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-12 22:58 ` hubicka 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-103209-4-yyCDHk6H5f@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: link
Be 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).