From: Andreas Jaeger <aj@suse.de>
To: Ritu Sabharwal <ritu@csa.iisc.ernet.in>
Cc: gcc@gcc.gnu.org, scox@redhat.com
Subject: Re: Loop dependence analysis!!
Date: Wed, 16 Oct 2002 02:55:00 -0000 [thread overview]
Message-ID: <u8k7ki6fc5.fsf@gromit.moeb> (raw)
In-Reply-To: <Pine.LNX.4.44.0210161133060.15844-100000@opal.csa.iisc.ernet.in> (Ritu Sabharwal's message of "Wed, 16 Oct 2002 12:09:54 +0530 (IST)")
Ritu Sabharwal <ritu@csa.iisc.ernet.in> writes:
> We are using gcc-3.0 for modulo scheduling, the loop dependence
> analysis is done in dependene.c file. This file is not used anywhere in
> the source code but we need to use it to find the distance and direction
> vectors for finding dependencies for finding II(initiation interval).
> We have used the functions from this file but this is not working
> properly, giving segmentation fault. Is something missing in that file?
It seems that this file is nowhere used in any GCC version. Since
it's not used anywhere, I'm not surprised that you get problems using
it.
It was added with this ChangeLog and afterwards nothing happened:
2000-08-22 Stan Cox <scox@redhat.com>
* Makefile.in (OBJS): Add dependence.o.
* dependence.c: New file.
Looking at the gcc-patches archive, the patch contains a follow-on
patch that was never committed:
http://gcc.gnu.org/ml/gcc-patches/2000-07/msg00788.html
http://gcc.gnu.org/ml/gcc-patches/2000-08/msg00117.html
http://gcc.gnu.org/ml/gcc-patches/2000-08/msg00187.html
Stan, what's going on here? Should we remove dependence.c completly?
Or will the rest get added at some point?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-10-16 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 2:40 Ritu Sabharwal
2002-10-16 2:55 ` Andreas Jaeger [this message]
2002-10-17 14:55 ` Ritu Sabharwal
2002-10-16 9:43 scox
2002-10-16 13:16 ` Andreas Jaeger
2002-10-16 13:23 ` Diego Novillo
2002-10-16 13:53 ` Pop Sébastian
2002-10-16 13:58 ` Diego Novillo
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=u8k7ki6fc5.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=ritu@csa.iisc.ernet.in \
--cc=scox@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).