This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Design Considerations of GIMPLE Front End


On Tue, May 18, 2010 at 09:59, Michael Matz <matz@suse.de> wrote:

> I don't see how that is much easier to parse compared to
> Âi_1 = k_1 + m_1
> Âj_1 = func (arg1, arg2)

Well, it would make the parser almost trivial to implement.  But you
have a point, the only structurally complex objects we need to parse
are type declarations.  Everything else should have very uniform
syntax.

> The nice thing with tuples is that there's always only one operator, and
> hence no ambiguity in precedence that needs to be resolved or explicitely
> encoded via a list structure.

That's true.

> Or is the format also intended to be able to represent GENERIC, i.e.
> deeply nested structures?

No, just gimple.


Diego.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]