So no one wastes time looking into this
On Wed, Aug 15, 2012 at 10:54 AM, Matt Davis wrote:
> Hello,
> In my compiler pass, I am inserting a new gimple call statement, and
> then replacing the next call. This usually works fine, and after I do
> this, the gimple dump looks as I expect. Howe
Hello,
In my compiler pass, I am inserting a new gimple call statement, and
then replacing the next call. This usually works fine, and after I do
this, the gimple dump looks as I expect. However, in one case, I
trigger gcc to abort in "remove_unreachable_handlers, at
tree-eh.c:3524" this is for
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
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
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
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
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
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
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
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
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
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
tree and do with it what ever
> I wished to, without modifying too many files but it seems that gcc,
> g++ and other frontends have different program flows and only share
> some data structures and backend sources. So probably I need to
> eliminate the backend call in every frontend a
ent program flows and only share
> some data structures and backend sources. So probably I need to
> eliminate the backend call in every frontend and after GIMPLE is
> created call my own functions which get the GIMPLE tree and then
> compile my files against every frontend. Right?
hat ever
I wished to, without modifying too many files but it seems that gcc,
g++ and other frontends have different program flows and only share
some data structures and backend sources. So probably I need to
eliminate the backend call in every frontend and after GIMPLE is
created call my own functions
15 matches
Mail list logo
