This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: lto gimple types and debug info
- From: Arnaud Charlet <charlet at adacore dot com>
- To: Kenneth Zadeck <zadeck at naturalbridge dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, Diego Novillo <dnovillo at google dot com>, "Hubicha, Jan" <jh at suse dot cz>, Richard Guenther <richard dot guenther at gmail dot com>, "Taylor, Ian Lance" <iant at google dot com>, Ollie Wild <aaw at google dot com>, "Maddox, Bill" <maddox at google dot com>, jason at redhat dot com, Rafael Espindola <espindola at google dot com>, Arnaud Charlet <charlet at adacore dot com>
- Date: Thu, 24 Jul 2008 18:38:27 +0200
- Subject: Re: lto gimple types and debug info
- References: <4888AD1F.7080007@naturalbridge.com>
> In this same vein, I am very interested in using the gimple type
> system as a way to start moving gcc from being a C compiler that
> accommodates other languages to a compiler that handles different
> languages on an equal footing. The freedom that C and C++ "enjoy" to
> basically take a pointer to one type and convert it to a pointer to
> almost any other type is not something that is allowed by the other
> languages that gcc supports. Fortran seems to require (and this
> should be confirmed by a fortran expert) a very disciplined use of
> pointers, even restricting pointers to only being able to point to
> variables that are declared to be targets of pointers.
I do not know Fortran, but from the description above, this is similar in Ada:
you cannot freely mix different pointers, and you cannot make a pointer out
of any variable, unless variables are marked 'aliased'. This semantic is
already expressed today in GCC trees, so I'm not sure what more/different
you're suggesting though.
Arno