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/105739] [10 Regression] Miscompilation of Linux kernel update.c
Date: Mon, 20 Jun 2022 06:38:12 +0000	[thread overview]
Message-ID: <bug-105739-4-MGZiVSHjKZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105739-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:62148f13c6427edd256072b3196a01b3d5ed2805

commit r10-10856-g62148f13c6427edd256072b3196a01b3d5ed2805
Author: Jan Hubicka <jh@suse.cz>
Date:   Tue Jun 14 14:05:53 2022 +0200

    Fix ipa-cp wrt volatile loads

    Check for volatile flag to ipa_load_from_parm_agg.

    gcc/ChangeLog:

    2022-06-10  Jan Hubicka  <hubicka@ucw.cz>

            PR ipa/105739
            * ipa-prop.c (ipa_load_from_parm_agg): Punt on volatile loads.

    gcc/testsuite/ChangeLog:

    2022-06-10  Jan Hubicka  <hubicka@ucw.cz>

            * gcc.dg/ipa/pr105739.c: New test.

    (cherry picked from commit 8f6c317b3a16350698f3c9e0accb43a9b4acb4ae)

  parent reply	other threads:[~2022-06-20  6:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 11:22 [Bug tree-optimization/105739] New: [9/10 " jakub at gcc dot gnu.org
2022-05-26 11:23 ` [Bug tree-optimization/105739] " jakub at gcc dot gnu.org
2022-05-26 11:23 ` jakub at gcc dot gnu.org
2022-05-26 11:28 ` jakub at gcc dot gnu.org
2022-05-26 13:51 ` hubicka at gcc dot gnu.org
2022-05-27  9:48 ` [Bug tree-optimization/105739] [10 " rguenth at gcc dot gnu.org
2022-06-02 10:11 ` jakub at gcc dot gnu.org
2022-06-04 16:07 ` hubicka at kam dot mff.cuni.cz
2022-06-09 11:21 ` hubicka at gcc dot gnu.org
2022-06-10 10:47 ` hubicka at gcc dot gnu.org
2022-06-10 10:56 ` hubicka at gcc dot gnu.org
2022-06-14 12:07 ` cvs-commit at gcc dot gnu.org
2022-06-14 12:23 ` jakub at gcc dot gnu.org
2022-06-19 10:08 ` cvs-commit at gcc dot gnu.org
2022-06-20  6:37 ` cvs-commit at gcc dot gnu.org
2022-06-20  6:38 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-20  9:56 ` jakub at gcc dot gnu.org
2022-06-20 10:42 ` hubicka at kam dot mff.cuni.cz

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-105739-4-MGZiVSHjKZ@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).