This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: genautomata progress bars tweak
- From: law at redhat dot com
- To: Vladimir Makarov <vmakarov at redhat dot com>
- Cc: Andreas Jaeger <aj at suse dot de>, Segher Boessenkool <segher at kernel dot crashing dot org>, Zack Weinberg <zack at codesourcery dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 12 Jan 2004 10:53:30 -0700
- Subject: Re: genautomata progress bars tweak
- Reply-to: law at redhat dot com
In message <4002D99B.FDD5E92C@redhat.com>, Vladimir Makarov writes:
>Andreas Jaeger wrote:
>>
>> Vladimir Makarov <vmakarov@redhat.com> writes:
>>
>> > Andreas Jaeger wrote:
>>
>> I think the point is to have this option off by default - and if you
>> develop it, you can enable it yourself. So, I would do:
>> o add an option to enable all output. By default no output is
>> printed.
>>
>
>Yes, that is better. I'll make it.
>
>Sorry, that I was too slow with my previous response which resulted that
>you already done the patch. I'd still prefer to have a progress bar for
>debugging. The progress bar was not my invention.
I wouldn't object if the progress bar was off by default, but could be
turned on by a switch or magic in the automata -- similarly for the
automata state information (which as I said it useful sometimes).
>It was a requirement from people who wrote DFA description.
Understood -- though that was probably due in part to the earlier versions
of genautomata being rather slow and the developers themselves not being
aware of the kinds constructs which would cause the automata to blow up.
genautomata is quite a bit faster now :-) Which reminds me, didn't Zdenek
have a change to speed up genautomata further (or was that genattrtab?)
jeff