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/100520] [11 Regression] ‘-fcompare-debug’ failure with -fprofile-generate since r11-627-g1dedc12d186a1108
Date: Mon, 08 Nov 2021 12:27:38 +0000	[thread overview]
Message-ID: <bug-100520-4-4nZYt2ggVK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100520-4@http.gcc.gnu.org/bugzilla/>

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #11 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed.

      parent reply	other threads:[~2021-11-08 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 13:52 [Bug debug/100520] New: [11/12 Regression] aarch64: ‘-fcompare-debug’ failure with -fprofile-generate acoplan at gcc dot gnu.org
2021-05-12  6:36 ` [Bug debug/100520] " rguenth at gcc dot gnu.org
2021-07-28  7:06 ` rguenth at gcc dot gnu.org
2021-09-20  7:00 ` [Bug debug/100520] [11/12 Regression] " pinskia at gcc dot gnu.org
2021-09-20  7:05 ` pinskia at gcc dot gnu.org
2021-09-20  7:12 ` [Bug gcov-profile/100520] " pinskia at gcc dot gnu.org
2021-09-27 11:54 ` marxin at gcc dot gnu.org
2021-11-05 15:01 ` [Bug gcov-profile/100520] [11/12 Regression] ‘-fcompare-debug’ failure with -fprofile-generate since r11-627-g1dedc12d186a1108 marxin at gcc dot gnu.org
2021-11-05 15:15 ` marxin at gcc dot gnu.org
2021-11-08 11:52 ` cvs-commit at gcc dot gnu.org
2021-11-08 11:54 ` [Bug gcov-profile/100520] [11 " marxin at gcc dot gnu.org
2021-11-08 12:26 ` cvs-commit at gcc dot gnu.org
2021-11-08 12:27 ` marxin at gcc dot gnu.org [this message]

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-100520-4-4nZYt2ggVK@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).