[patch, RFC] Add EXEC_COMPCALL to front end expression walker

[Thomas Koenig]

Hello world,

the attached patch adds handling for EXEC_COMPCALL to the front end
expression walker.

Based on resolve_ordinary_assign in resolve.c, I think think this is the
right thing to do. However...

I tried finding a use of EXEC_COMPCALL in the testsuite by placing a
gcc_assert((*c)->op != EXEC_COMPCALL) in the front end walker.  I then
ran the testsuite in the hope of ICEing on a dg-do run test, but I only
found EXEC_COMPCALL in dg-do compile tests with syntax errors this way.

When, exactly, is EXEC_COMPCALL used?  Maybe it would be a good idea to
add a test case for this to the testsuite.

No changelog entry (although that one would be obvious), because this is
still an RFC.  I also regression-tested this.

Comments?  Ideas?  Should I just commit this?

	Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p1.diff
Type: text/x-patch
Size: 517 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20110212/3a2e12b0/attachment.bin>