public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sabrinadfs at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61980] ICE: in compute_affine_dependence, at tree-data-ref.c:4233 with -fcheck-data-deps
Date: Fri, 01 Aug 2014 11:21:00 -0000 [thread overview]
Message-ID: <bug-61980-4-nl9bL3WuDI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61980-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61980
--- Comment #4 from Sabrina Souto <sabrinadfs at gmail dot com> ---
I don't have much experience with GCC, so I'm a bit confused with your 2
answers, please help me understanding what is happening: Based both on the
documentation and the results, I understood that the result from the dependency
analysis (Banerjee dist vectors: 0 1 , Omega dist vectors: 0) is wrong or not
expected, but this is due to the "unreliably" work of -fcheck-data-deps or,
since -fcheck-data-deps is used for debug, it is working well and this result
must be investigated?
(In reply to Richard Biener from comment #3)
> It's intended for debugging only:
>
> @item -fcheck-data-deps
> @opindex fcheck-data-deps
> Compare the results of several data dependence analyzers. This option
> is used for debugging the data dependence analyzers.
next prev parent reply other threads:[~2014-08-01 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 17:15 [Bug c/61980] New: [GCC-4.9.1] ICE: in compute_affine_dependence, at tree-data-ref.c:4233 sabrinadfs at gmail dot com
2014-07-31 17:18 ` [Bug middle-end/61980] " mpolacek at gcc dot gnu.org
2014-08-01 8:26 ` [Bug tree-optimization/61980] ICE: in compute_affine_dependence, at tree-data-ref.c:4233 with -fcheck-data-deps rguenth at gcc dot gnu.org
2014-08-01 11:03 ` sabrinadfs at gmail dot com
2014-08-01 11:05 ` rguenth at gcc dot gnu.org
2014-08-01 11:21 ` sabrinadfs at gmail dot com [this message]
2014-08-01 11:26 ` rguenth at gcc dot gnu.org
2014-08-01 11:30 ` sabrinadfs at gmail dot com
2015-07-18 1:18 ` spop 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-61980-4-nl9bL3WuDI@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).