This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: type consistency of gimple
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Kenneth Zadeck <zadeck at naturalbridge dot com>
- Cc: Nick Clifton <nickc at redhat dot com>, Daniel Berlin <dberlin at dberlin dot org>, Mark Mitchell <mark at codesourcery dot com>, Richard Guenther <richard dot guenther at gmail dot com>, GCC <gcc at gcc dot gnu dot org>, "Hubicha, Jan" <jh at suse dot cz>, "Edelsohn, David" <dje at watson dot ibm dot com>, Andrew Pinski <pinskia at physics dot uc dot edu>
- Date: Tue, 15 Aug 2006 12:07:28 -0400
- Subject: Re: type consistency of gimple
- References: <44DCEAAA.9000306@naturalbridge.com> <84fc9c000608111344l3cc4b9f0w97f104da6ed5b7ad@mail.gmail.com> <44DCEDF1.9010902@naturalbridge.com> <84fc9c000608111356n6bd522d5gd349007fdcb0cd1b@mail.gmail.com> <44DCF0A0.1060005@naturalbridge.com> <44DF6702.4060901@codesourcery.com> <44E074F4.3050402@dberlin.org> <44E08E4C.4060902@redhat.com> <44E1E12C.9080208@redhat.com> <44E1EF05.5070908@naturalbridge.com>
Kenneth Zadeck wrote on 08/15/06 11:57:
> We should be looking at the back end to see where it cannot see what it
> needs to see rather than trying to stop getting the middle end code into
> a reasonable form.
>
You're confused. This is a middle-end mis-optimization. However, it is
true that we should probably make the optimizers smarter.
First, though, we must define a GIMPLE type system.