public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44011] missed optimization of  min/max_expr or strict overflow warnings for intended code.
Date: Thu, 06 May 2010 11:27:00 -0000	[thread overview]
Message-ID: <20100506112708.8075.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44011-7667@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pluto at agmk dot net  2010-05-06 11:27 -------
(In reply to comment #1)
> Place the pragma outside of the function (though it'll probably not help
> due to the inlining).

with new function attribute "warning(string...)" similary to existing
"target" and "optimize" atributtes/pragmas it would be possible to manage
warnings for intended parts of code. currently diagnostic system reports
the location of strict-overflow, so i suppose it's able to check a function
attributes and skip some warnings. am i right?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44011


  parent reply	other threads:[~2010-05-06 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  9:36 [Bug other/44011] New: " pluto at agmk dot net
2010-05-06 10:14 ` [Bug tree-optimization/44011] " rguenth at gcc dot gnu dot org
2010-05-06 11:27 ` pluto at agmk dot net [this message]
2010-05-06 11:30 ` rguenth at gcc dot gnu dot org
     [not found] <bug-44011-4@http.gcc.gnu.org/bugzilla/>
2021-11-25  6:54 ` 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=20100506112708.8075.qmail@sourceware.org \
    --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).