public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at charter dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libmudflap/19319] Mudflap produce many violations on simple, correct c++ program
Date: Wed, 14 Dec 2005 17:46:00 -0000	[thread overview]
Message-ID: <20051214174629.4837.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19319-2476@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from ppluzhnikov at charter dot net  2005-12-14 17:46 -------
Same picture using gcc-4.1-20051209 for i686-pc-linux-gnu: 
7 bogus violations on original test, 1 on reduced test.

Here are other version results:
                                               original           reduced
gcc-4.1-20051209 i686-pc-linux-gnu               7                   1
gcc-4.2-20051210 i686-pc-linux-gnu               1                   1
gcc-4.2-20051210 x86_64-unknown-linux-gnu        0                   0
gcc-4.2-20051210 x86_64-unknown-linux-gnu -m32   1                   1

Encouraged by the absence of bogus warnings on x86_64 in 64-bit mode, I tried 
4.2-20051210 on my real code. This resulted in 100s of bogus violations,
though I have not been able to produce a reduced test case yet :-(

I then tried 4.2-20051210 i686 on "pure C" real code, and got 100s more
bogus violations.

IMHO, the -fmudflap either needs to be made to work correctly on real C/C++
programs, or it should be removed altogether (bogus reports lead to a lot
of wasted time, as each new user "discovers" the feature, and then finds out
it doesn't work).


-- 


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


  parent reply	other threads:[~2005-12-14 17:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19319-2476@http.gcc.gnu.org/bugzilla/>
2005-10-23 23:47 ` ppluzhnikov at charter dot net
2005-12-14 17:46 ` ppluzhnikov at charter dot net [this message]
2006-03-19  5:11 ` pinskia at gcc dot gnu dot org
2006-11-10  3:09 ` fche at redhat dot com
2006-11-10 16:34 ` p dot van-hoof at qub dot ac dot uk
2006-11-10 16:35 ` p dot van-hoof at qub dot ac dot uk
2006-11-10 23:00 ` ppluzhnikov at charter dot net
2006-11-10 23:31 ` ppluzhnikov at charter dot net
2006-11-14  3:53 ` fche at redhat dot com
2006-11-14  4:26 ` ppluzhnikov at charter dot net
2006-11-14 12:19 ` fche at redhat dot com
2006-11-15  1:22 ` ppluzhnikov at charter dot net
2007-06-10 19:32 ` awl03 at doc dot ic dot ac dot uk
2007-06-10 19:35 ` awl03 at doc dot ic dot ac dot uk
2007-06-20 19:37 ` fche at redhat dot com
2007-07-12 23:58 ` awl03 at doc dot ic dot ac dot uk
2007-08-27 18:41 ` jason at gcc dot gnu dot org
2008-04-09 19:15 ` fche at redhat dot com
2009-05-07 16:31 ` f dot knauf at mmkf dot de
     [not found] <bug-19319-4@http.gcc.gnu.org/bugzilla/>
2014-02-16  9:59 ` jackie.rosen at hushmail dot com
2005-01-07 22:31 [Bug libmudflap/19319] New: " bredelin at ucla dot edu
2005-01-07 22:42 ` [Bug libmudflap/19319] " fche at redhat dot com
2005-01-07 22:58 ` fche at redhat dot com
2005-01-08 20:03 ` bangerth at dealii dot org
2005-01-10 17:04 ` fche at redhat dot com
2005-01-18  9:35 ` bredelin at ucla dot edu
2005-02-13 18:35 ` cvs-commit at gcc dot gnu dot org
2005-02-13 20:08 ` cvs-commit at gcc dot gnu dot org
2005-02-13 20:09 ` fche at redhat dot com
2005-02-17 15:12 ` cvs-commit at gcc dot gnu dot org
2005-02-19 22:10 ` pinskia at gcc dot gnu dot org
2005-02-19 22:36 ` pinskia at gcc dot gnu dot org
2005-02-19 22:37 ` pinskia at gcc dot gnu dot org
2005-03-10 21:57 ` fche at redhat dot com
2005-04-20  2:36 ` pinskia at gcc dot gnu dot org
2005-08-18 20:05 ` gideon dot amos at canfieldsci dot com
2005-08-18 20:10 ` fche at redhat dot com
2005-08-18 22:36 ` pinskia at gcc dot gnu dot org
2005-09-23 21:35 ` cvs-commit at gcc dot gnu dot org
2005-09-23 21:35 ` fche at redhat dot com

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=20051214174629.4837.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).