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 lto/95362] [11 regression] pr34457-1.c and pr92088-1.c fail on arm and aarch64 since g:a746f952abb78af9db28a7f3bce442e113877c9c
Date: Fri, 14 Aug 2020 11:37:48 +0000	[thread overview]
Message-ID: <bug-95362-4-BekMMlYuCG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95362-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:630474c8904cf797d0ee022d2ab177e25932c1d7

commit r10-8629-g630474c8904cf797d0ee022d2ab177e25932c1d7
Author: Jan Hubicka <jh@suse.cz>
Date:   Fri May 29 12:25:48 2020 +0200

    Fix streamer desynchornization caused by streamer debugging patch

    it turns out I lost one hunk in the patch disabling extra streaming
    which causes streamer to go out of sync in the case non-trivial scc
    containing the node being streamed appears in local stream (which seems
    quite rare since it does not happen during bootstrap).

    2020-05-29  Jan Hubicka  <hubicka@ucw.cz>

            PR lto/95362
            * lto-streamer-out.c (lto_output_tree): Disable redundant
streaming.

    (cherry picked from commit 11041c3151e30d197d1c2774721db24332eeccef)

  parent reply	other threads:[~2020-08-14 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 11:32 [Bug other/95362] New: [11 regression] pr34457-1.c fails on arm since ga746f952abb78af9db28a7f3bce442e113877c9c clyon at gcc dot gnu.org
2020-05-27 11:34 ` [Bug other/95362] [11 regression] pr34457-1.c and pr92088-1.c fail on arm and aarch64 " clyon at gcc dot gnu.org
2020-05-27 11:43 ` [Bug lto/95362] [11 regression] pr34457-1.c and pr92088-1.c fail on arm and aarch64 since g:a746f952abb78af9db28a7f3bce442e113877c9c marxin at gcc dot gnu.org
2020-05-27 12:52 ` marxin at gcc dot gnu.org
2020-05-28  7:32 ` rguenth at gcc dot gnu.org
2020-05-29 10:26 ` cvs-commit at gcc dot gnu.org
2020-08-14 11:37 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-16 11:47 ` rguenth at gcc dot gnu.org
2020-10-16 11:47 ` rguenth 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-95362-4-BekMMlYuCG@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).