This is the mail archive of the
mailing list for the GCC project.
Re: what about a compiler probe?
- From: Mike Stump <mrs at apple dot com>
- To: Basile STARYNKEVITCH <basile at starynkevitch dot net>
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 26 Nov 2006 16:35:46 -0800
- Subject: Re: what about a compiler probe?
- References: <20061126232039.GA27148@ours.starynkevitch.net>
On Nov 26, 2006, at 3:20 PM, Basile STARYNKEVITCH wrote:
The textual protcol should permit to examine, but not change, the
Sounds like a bad idea. I agree with the debugger comment. You're
free to start up the compilation process with ptrace from your GUI
and query/display/modify the state in whatever way you like. The
problems I see are that any internal details that are exposed to the
protocol fixes those details forever, or, should they not be fixed,
breaks the stability of the protocol.
Another suggestion would be to, if you want just a few status bits,
add them to -Q and just read those bits on the output.