On Sat, 2008-10-11 at 23:19 +0200, Richard Guenther wrote:
> On Sat, Oct 11, 2008 at 11:13 PM, Sebastian Pop <[EMAIL PROTECTED]> wrote:
> > On Sat, Oct 11, 2008 at 6:46 AM, Richard Guenther
> > <[EMAIL PROTECTED]> wrote:
> >> Note that we cannot really remove switches from the user, but we have to at
> >> least keep them as no-op for backward compatibility. Which is why I would
> >> like you to think twice at least as to what options you want to add for
> >> 4.4.
> >> As a rule of thumb, do not add (or at least document) options that are not
> >> useful for users of GCC but only developers of GCC. Maybe you can add a
> >> glob for debugging options with -fdebug-graphite-XXX instead?
> >>
> >
> > We can enable the -fgraphite-* flags only when ENABLE_CHECKING is defined,
> > such that these are disabled in the released compilers.
>
> I think that you can keep them enabled without ENABLE_CHECKING. But I suggest
> to remove user-level documentation of them (documentation in common.opt
> comments
> should be enough).
Hi,
another patch. It contains:
- Removal of documentation outside of common.opts for (-fgraphite,
-floop-block, -floop-interchange, -floop-strip-mine)
This means doc/invoke.texi.
(Proposed by Richi)
- Removal of flag "-floop-strip-mine", as it never will improve
performance and so there will be no use for it.
(Proposed by Harsha)
- Rename of -floop-block to -fgraphite-block and -floop-interchange to
-fgraphite-interchange.
(Proposed by Albert)
- Add of -fgraphite-identity.
(Proposed by Tobias (me), solution 2 selected by Harsha y Sebastian)
- Add warning as -fgraphite-interchange is not yet implemented.
(Tobias (me))
So the graphite command line flags are not available any more in the
user documentation, but can be used to test/debug the graphite code.
What flags exist?
-fgraphite: Graphite without code generation.
Useful for frontend testing.
-fgraphite-identity: The identity transformation.
Useful for backend testing without
transformation.
-fgraphite-block: Loop blocking.
Useful for checking available performance
improvements with loop blocking
-fgraphite-interchange: Loop interchange (unimplemented).
Useful for checking available performance
improvements with loop interchange.
Later I would like to be -fgraphite the automatic optimizer.
See you
Tobi
