Re: After GIMPLE...

2007-02-07 Thread Paulo J. Matos
On 2/6/07, Diego Novillo <[EMAIL PROTECTED]> wrote: Paulo J. Matos wrote on 02/06/07 14:19: > Why before pass_build_ssa? (version 4.1.1) > It depends on the properties your pass requires. If you ask for PROP_cfg and PROP_gimple_any then you should schedule it after the CFG has been built, but i

Re: After GIMPLE...

2007-02-06 Thread Diego Novillo
Paulo J. Matos wrote on 02/06/07 14:19: Why before pass_build_ssa? (version 4.1.1) It depends on the properties your pass requires. If you ask for PROP_cfg and PROP_gimple_any then you should schedule it after the CFG has been built, but if you need PROP_ssa, then you must be after pass_bui

Re: After GIMPLE...

2007-02-06 Thread Paulo J. Matos
On 1/31/07, Diego Novillo <[EMAIL PROTECTED]> wrote: Paulo J. Matos wrote on 01/31/07 11:26: > So, ideally, I would like just the gcc part until the first part of > the middleend where you have a 'no optimizations', language > independent AST of the source file. > OK, so you probably want to inj

Re: After GIMPLE...

2007-02-01 Thread Paulo J. Matos
On 2/1/07, Diego Novillo <[EMAIL PROTECTED]> 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 invol

Re: After GIMPLE...

2007-02-01 Thread Diego Novillo
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 poin

Re: After GIMPLE...

2007-02-01 Thread Paulo J. Matos
On 1/31/07, Diego Novillo <[EMAIL PROTECTED]> wrote: Paulo J. Matos wrote on 01/31/07 11:26: > So, ideally, I would like just the gcc part until the first part of > the middleend where you have a 'no optimizations', language > independent AST of the source file. > OK, so you probably want to inj

Re: After GIMPLE...

2007-01-31 Thread Diego Novillo
Paulo J. Matos wrote on 01/31/07 11:26: So, ideally, I would like just the gcc part until the first part of the middleend where you have a 'no optimizations', language independent AST of the source file. OK, so you probably want to inject your pass right before pass_build_ssa (in init_optimiza

Re: After GIMPLE...

2007-01-31 Thread Paulo J. Matos
On 1/31/07, Diego Novillo <[EMAIL PROTECTED]> wrote: Paulo J. Matos wrote on 01/30/07 10:11: > Well, I spent the morning looking at the code and since what I need is > only the flow of gcc up until I have the GIMPLE tree, I could add a > pass after the pass which generates the gimple tree, in th

Re: After GIMPLE...

2007-01-31 Thread Diego Novillo
Paulo J. Matos wrote on 01/30/07 10:11: Well, I spent the morning looking at the code and since what I need is only the flow of gcc up until I have the GIMPLE tree, I could add a pass after the pass which generates the gimple tree, in that pass I do what I need with the gimple tree and then call

Re: After GIMPLE...

2007-01-30 Thread Paulo J. Matos
On 29 Jan 2007 11:38:15 -0800, Ian Lance Taylor <[EMAIL PROTECTED]> wrote: I don't see why you would have to modify any code in the frontend. You would modify the middle-end code. Rebuilding the compiler would rebuild cc1, cc1plus, etc. Well, I spent the morning looking at the code and since

Re: After GIMPLE...

2007-01-30 Thread Paulo J. Matos
On 29 Jan 2007 11:38:15 -0800, Ian Lance Taylor <[EMAIL PROTECTED]> wrote: "Paulo J. Matos" <[EMAIL PROTECTED]> writes: > I've been looking into the gcc sources and I'm somewhat confused. > Are gcc/g++ comepletely independent programs or do they share a backend? In the source code, they share a

Re: After GIMPLE...

2007-01-29 Thread Ian Lance Taylor
"Paulo J. Matos" <[EMAIL PROTECTED]> writes: > I've been looking into the gcc sources and I'm somewhat confused. > Are gcc/g++ comepletely independent programs or do they share a backend? In the source code, they share a backend. As executables, they are different programs: cc1 and cc1plus. > T