public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/105210] gcc/auto-profile.cc:391:11: warning: variable 'level' set but not used
Date: Tue, 12 Apr 2022 17:56:16 +0000	[thread overview]
Message-ID: <bug-105210-4-zsjkss8xh8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105210-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Martin Liška from comment #6)
> I'm going to prepare a patch for next stage 1.

Do you mean the smaller patch to fix the problems I reported,
or a larger patch to have gcc duplicate the behaviour of clang ?

I checked the assembly language output from the code in comment 2
and AFAIK the optimiser removes the pointless increment at level -O1
and above.

  parent reply	other threads:[~2022-04-12 17:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10 19:54 [Bug c/105210] New: " dcb314 at hotmail dot com
2022-04-10 20:04 ` [Bug c/105210] " dcb314 at hotmail dot com
2022-04-10 20:12 ` dcb314 at hotmail dot com
2022-04-10 21:58 ` [Bug gcov-profile/105210] " pinskia at gcc dot gnu.org
2022-04-10 22:10 ` egallager at gcc dot gnu.org
2022-04-10 22:29 ` pinskia at gcc dot gnu.org
2022-04-11  8:13 ` marxin at gcc dot gnu.org
2022-04-11 14:24 ` marxin at gcc dot gnu.org
2022-04-12 17:56 ` dcb314 at hotmail dot com [this message]
2022-04-12 18:45 ` marxin at gcc dot gnu.org
2022-05-05 13:05 ` marxin at gcc dot gnu.org
2022-05-05 15:43 ` dcb314 at hotmail dot com
2022-05-05 18:31 ` marxin 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-105210-4-zsjkss8xh8@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).