sing code, we're
> > not running into any issues with the OpenACC Fortran front end test
> > cases?
> I think, this is OK, since this is an !$ACC END _smth_ statement and it
> shall not present in the AST. So, it is abandoned later anyway ;) (if I
> remember correctly, d
nt in the AST. So, it is abandoned later anyway ;) (if I
remember correctly, during gfc_clear_new_st call). Although the bug does
not affect the logic, it is still a bug.
OK for trunk?
From my point of view, OK.
commit 068eebfa63b2b4c8849ed5fd2c9d0a130586dfb0
Author: Thomas Schw
ove -- I would guess for the reason to get a
better error message? (Tobias, should this thus also be done for OpenMP,
and/or extend unexpected_statement accordingly?)
And then, I'm a bit confused: is it "OK" that despite this presumed logic
error, which affects all (?) valid executions
