Re: [graphite] Cleanup of command line parameters [PATCH]

2008-10-12 Thread Tobias Burnus
Hi, Tobias Grosser wrote: 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) While I agree that -fgraphite does not make sense as user

Re: [graphite] Cleanup of command line parameters [PATCH]

2008-10-12 Thread Tobias Grosser
Hi, On Sun, 2008-10-12 at 13:19 +0200, Tobias Burnus wrote: Hi, Tobias Grosser wrote: 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

Re: [graphite] Cleanup of command line parameters

2008-10-11 Thread Richard Guenther
On Fri, Oct 10, 2008 at 8:54 PM, Tobias Grosser [EMAIL PROTECTED] wrote: On Fri, 2008-10-10 at 20:35 +0200, Manuel López-Ibáñez wrote: 2008/10/10 Tobias Grosser [EMAIL PROTECTED]: Now: -fgraphite: Do nothing. -floop-block, -floop-interchange, -floop-stripmine: Try these

Re: [graphite] Cleanup of command line parameters

2008-10-11 Thread Richard Guenther
On Fri, Oct 10, 2008 at 11:31 PM, Albert Cohen [EMAIL PROTECTED] wrote: Tobias Grosser wrote Hi graphities, graphite consists of four flags -floop-block, -floop-interchange, -floop-stripmine and -fgraphite. If any of these flags is set, we enable the graphite pass and we search for SCoPs.

Re: [graphite] Cleanup of command line parameters

2008-10-11 Thread Sebastian Pop
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

Re: [graphite] Cleanup of command line parameters

2008-10-11 Thread Richard Guenther
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

Re: [graphite] Cleanup of command line parameters

2008-10-11 Thread Tobias Grosser
Hi, On Fri, 2008-10-10 at 23:31 +0200, Albert Cohen wrote: Tobias Grosser wrote Hi graphities, graphite consists of four flags -floop-block, -floop-interchange, -floop-stripmine and -fgraphite. If any of these flags is set, we enable the graphite pass and we search for SCoPs.

Re: [graphite] Cleanup of command line parameters [PATCH]

2008-10-11 Thread Tobias Grosser
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

Re: [graphite] Cleanup of command line parameters [PATCH]

2008-10-11 Thread Tobias Grosser
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

Re: [graphite] Cleanup of command line parameters

2008-10-10 Thread Manuel López-Ibáñez
2008/10/10 Tobias Grosser [EMAIL PROTECTED]: Now: -fgraphite: Do nothing. -floop-block, -floop-interchange, -floop-stripmine: Try these transformations. This only applies to the branch, does it? There is no do-nothing command-line option in trunk, is there? Cheers, Manuel.

RE: [graphite] Cleanup of command line parameters

2008-10-10 Thread Jagasia, Harsha
Hi Tobias, graphite consists of four flags -floop-block, -floop-interchange, -floop-stripmine and -fgraphite. If any of these flags is set, we enable the graphite pass and we search for SCoPs. For every SCoP we try to apply transformations specified with -floop-block, -floop-interchange or

RE: [graphite] Cleanup of command line parameters

2008-10-10 Thread Jagasia, Harsha
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. Thanks, Harsha

Re: [graphite] Cleanup of command line parameters

2008-10-10 Thread Tobias Grosser
On Fri, 2008-10-10 at 20:35 +0200, Manuel López-Ibáñez wrote: 2008/10/10 Tobias Grosser [EMAIL PROTECTED]: Now: -fgraphite: Do nothing. -floop-block, -floop-interchange, -floop-stripmine: Try these transformations. This only applies to the branch, does it? There is no

RE: [graphite] Cleanup of command line parameters

2008-10-10 Thread Tobias Grosser
On Fri, 2008-10-10 at 13:49 -0500, Jagasia, Harsha wrote: Hi Tobias, graphite consists of four flags -floop-block, -floop-interchange, -floop-stripmine and -fgraphite. If any of these flags is set, we enable the graphite pass and we search for SCoPs. For every SCoP we try to apply

Re: [graphite] Cleanup of command line parameters

2008-10-10 Thread Albert Cohen
Tobias Grosser wrote Hi graphities, graphite consists of four flags -floop-block, -floop-interchange, -floop-stripmine and -fgraphite. If any of these flags is set, we enable the graphite pass and we search for SCoPs. For every SCoP we try to apply transformations specified with -floop-block,