On 28/06/2024 09:44, Werner Pamler via fpc-devel wrote:
I having the same experience as Laz-dev: I see a report which looks
interesting, but cannot address it at the moment. Not sure whether I
really can fix the issue I do not assign it to myself at this moment.
And later, when I could have a c
Fixed 2 and 3.
- 2 was due to not handling block nodes properly when they didn't have
any statements (data-flow analysis stripped the procedure completely
clean since no result was set), hence an access violation occurred while
accessing a node that was nil.
- 3 was a two-fold problem:
1. T
