This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/22371] C front-end produces mis-match types in MODIFY_EXPR
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Aug 2007 15:03:00 -0000
- Subject: [Bug c/22371] C front-end produces mis-match types in MODIFY_EXPR
- References: <bug-22371-6528@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #11 from rguenther at suse dot de 2007-08-22 15:03 -------
Subject: Re: C front-end produces mis-match types in MODIFY_EXPR
On Wed, 22 Aug 2007, joseph at codesourcery dot com wrote:
> Subject: Re: C front-end produces mis-match types in MODIFY_EXPR
>
> On Wed, 22 Aug 2007, rguenther at suse dot de wrote:
>
> > As far as I see we still need to re-instantiate transitiveness
> > of useless_type_converison_p somehow, by handling all of the
> > aggregate type compatibilities in the middle-end without dispatching
> > back to the frontends. Like with something like
>
> Arrays aren't the only case where C type compatibility isn't transitive.
> For example, two enums compatible with the same integer type aren't
> compatible with each other.
They are as far as the middle-end is concerned, so this is a non-issue
there. The issue is really that for all aggregate types we still ask
the frontend via the langhook for middle-end type compatibility.
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22371