This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: After GIMPLE...
- From: "Paulo J. Matos" <pocm at soton dot ac dot uk>
- To: "Diego Novillo" <dnovillo at redhat dot com>
- Cc: "Ian Lance Taylor" <iant at google dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 1 Feb 2007 14:42:29 +0000
- Subject: Re: After GIMPLE...
- References: <11b141710701290917p102e7126qf791ceebadae4382@mail.gmail.com> <m3veip62u0.fsf@localhost.localdomain> <11b141710701300711i599ba481ke97c2e36f4ae9c6e@mail.gmail.com> <45C0A33D.5040802@redhat.com> <11b141710701310826s7e49cc1bt982f4487c1a1d45f@mail.gmail.com> <45C10460.9050203@redhat.com> <11b141710702010137l34cf2c6fjb74b6418241ad9bf@mail.gmail.com> <45C1F895.7070602@redhat.com>
On 2/1/07, Diego Novillo <dnovillo@redhat.com> wrote:
Paulo J. Matos wrote on 02/01/07 04:37:
> What can I do then to stop gcc to further process things? After
> informing the user there's no more reason on my site to continue.
>
Stop gracefully or just stop? The latter is easy. The former involves
writing code to skip all passes after a certain point, or just don't
schedule the passes don't want to run. See init_optimization_passes.
Well, I guessed the answer would be something like that... :)
I've already started working on it and everything seems ok up until
now so I'm on the right track. :)
Regards and thanks very much,
--
Paulo Jorge Matos - pocm at soton.ac.uk
http://www.personal.soton.ac.uk/pocm
PhD Student @ ECS
University of Southampton, UK