public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/64636] LTO PGO bootstrap fails on linux-sparc64 in stream_out_histogram_value Date: Fri, 25 Sep 2020 14:27:58 +0000 [thread overview] Message-ID: <bug-64636-4-yDev2f3jg9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64636-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64636 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|11.0 | Known to work| |11.0 --- Comment #16 from Martin Liška <marxin at gcc dot gnu.org> --- Fixed on master so far.
next prev parent reply other threads:[~2020-09-25 14:27 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-16 21:57 [Bug lto/64636] New: Bootstrapping gcc-4.9.2 fails if lto is enabled carson at taltos dot org 2015-01-17 0:44 ` [Bug lto/64636] " carson at taltos dot org 2015-01-17 0:46 ` carson at taltos dot org 2020-05-13 20:21 ` [Bug lto/64636] LTO PGO bootstrap fails on linux-sparc64 in stream_out_histogram_value ostash at ostash dot kiev.ua 2020-06-16 20:06 ` grgoffe at yahoo dot com 2020-06-16 20:09 ` grgoffe at yahoo dot com 2020-06-16 20:13 ` grgoffe at yahoo dot com 2020-09-25 14:21 ` [Bug gcov-profile/64636] " marxin at gcc dot gnu.org 2020-09-25 14:21 ` marxin at gcc dot gnu.org 2020-09-25 14:26 ` cvs-commit at gcc dot gnu.org 2020-09-25 14:27 ` marxin at gcc dot gnu.org [this message] 2020-10-01 19:20 ` cvs-commit at gcc dot gnu.org 2020-10-02 10:06 ` cvs-commit at gcc dot gnu.org 2020-10-02 10:07 ` marxin at gcc dot gnu.org 2021-10-02 7:59 ` pinskia at gcc dot gnu.org 2021-10-02 8:00 ` 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-64636-4-yDev2f3jg9@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).