This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: [graphite] Cleanup of command line parameters
- From: Tobias Grosser <grosser at fim dot uni-passau dot de>
- To: "Jagasia, Harsha" <harsha dot jagasia at amd dot com>
- Cc: GCC <gcc at gcc dot gnu dot org>
- Date: Fri, 10 Oct 2008 17:28:27 -0200
- Subject: RE: [graphite] Cleanup of command line parameters
- References: <D5B24B5251882048AD03DDFA431BB790035F1CE3@SAUSEXMB3.amd.com>
On Fri, 2008-10-10 at 13:51 -0500, Jagasia, Harsha wrote:
> >
> >Hi Tobias,
> >>
> >>graphite consists of four flags "-floop-block", "-floop-interchange",
> >>"-floop-stripmine" and "-fgraphite".
>
> In fact I also think that we should not expose "-floop-stripmine" as a
> flag because by itself it is never profitable.
Yes, you may be right. The only reason for -floop-stripmine would be
functional testing of the loop strip mining pass, but it will never give
a performance improvement.
-floop-stripmine and -floop-interchange are not implemented at the
moment, but I did not want to remove them, as they may be implemented
later. I thought I could implement them over a weekend, but I could not
test them because of other bugs. So I thought the time is better spend
in fixing remaining graphite bugs.
But maybe we should print some error messages, if s.o. uses these flags.
See you
Tobias