From: Daniel Berlin <dberlin@dberlin.org>
To: law@redhat.com
Cc: Falk Hueffner <falk@debian.org>, gcc@gcc.gnu.org
Subject: Re: Question about pointer arithmetics in GIMPLE
Date: Mon, 22 Aug 2005 23:35:00 -0000 [thread overview]
Message-ID: <1124750995.13671.18.camel@dyn9002219145> (raw)
In-Reply-To: <1124750356.4397.43.camel@localhost.localdomain>
> Warning for pointer generation is going to be a *lot* harder and I
> suspect will always result in more false positives.
In order to increase the accuracy of the data dependence analysis, i do,
at some point, plan on tracking the sizes of malloc sites, and giving an
upper bound on them (for cases of loops, etc) when possible
on an interprocedural basis, that should allow you to generate at least
"this is obviously wrong" warnings.
prev parent reply other threads:[~2005-08-22 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 18:32 Falk Hueffner
2005-08-22 22:50 ` Jeffrey A Law
2005-08-22 23:35 ` Daniel Berlin [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=1124750995.13671.18.camel@dyn9002219145 \
--to=dberlin@dberlin.org \
--cc=falk@debian.org \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
/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).