This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: After GIMPLE...

From: Diego Novillo <dnovillo at redhat dot com>
To: "Paulo J. Matos" <pocm at soton dot ac dot uk>
Cc: Ian Lance Taylor <iant at google dot com>, gcc at gcc dot gnu dot org
Date: Thu, 01 Feb 2007 09:26:29 -0500
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>

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.

Follow-Ups:
- Re: After GIMPLE...
  - From: Paulo J. Matos

References:
- Re: After GIMPLE...
  - From: Paulo J. Matos

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]