Comment 2 for bug 1616992

Revision history for this message
Andre Vieira (andre-simoesdiasvieira) wrote :

Hi Andrew,

Sorry for the delay, I can confirm this. This also reveals another issue, the value that is in r3 (if we ignore the pop) is the address to callback4. This seems to originate from the middle end and I have confirmed it on both ARM and AARCH64, might be an issue with other targets too.

I am working on a bug report for the latter issue. As for the issue you reported, it seems to be working on trunk, so I will have a look at whether that is just coincidence or whether it has been fixed and needs a backport. Unfortunately I do not think we will be able to get this in for the next update release.

I see that our 4.9 2015q3 release does not have either of these issues, could you use that for the time being?

Kind Regards,
Andre