Thanks for the fix, Gabriel. I had located the bug, but I just didn't
understand enough about what
was going on in the match expression to fix things.
On 05/26/2011 10:52 AM, Gabriel Kerneis wrote:
> This should be fixed in latest svn revision (r12172). It wasn't that
> hard to fix after all.
>
On Wed, May 25, 2011 at 02:18:33PM -0400, Jesse M Draper wrote:
> CIL issues an "Error: Unexpected operand for addrof" message when it
> encounters &"stringliteral"
This should be fixed in latest svn revision (r12172). It wasn't that
hard to fix after all.
Thank you for the report,
--
Gabriel
On Wed, May 25, 2011 at 02:18:33PM -0400, Jesse M Draper wrote:
> CIL issues an "Error: Unexpected operand for addrof" message when it
> encounters &"stringliteral"
> even though GCC will compile this expression even with -ansi and/or -pedantic
> flags. Although the
> construct is a little odd,
CIL issues an "Error: Unexpected operand for addrof" message when it encounters
&"stringliteral"
even though GCC will compile this expression even with -ansi and/or -pedantic
flags. Although the
construct is a little odd, I think that it is ANSI compliant. I include a
sample file below that
w
