> I'm quite confused about the current state of this issue. Are the things described by Dave Nadler still relevant or
> applicable? Is ST going to fix the bugs in the __retarget_lock* implementations? For people using Cube's
> generated code, how are you all dealing with this at the moment?
That was a very long and unpleasant saga.
From what I've read through (also on Nadler's github issues, you should look it up), ST did address this. They years to do so, and the final result raised further questions. From what I gather "strategy 5" seemed to be ok, and "strategy 4" (fixed) was possibly ok. It is all very confusing, I agree. We all owe Nadler a thank you for identifying and explaining the issue, and then pressuring ST (not that it helped) to fix it. But as ST dragged their feet for years, Nadler got increasingly belligerent and unpleasant. I don't think this was much encouragement for the ST employee who tried to communicate ongoing status (nor would anyone else in their right mind willingly step into the rage pit that thread became) to continue to communicate with the vox populi directly.
There was a subsequent post by ST (same guy, who in my view was doing his best seeing as he's just an engineer in the corporate trenches) explaining the solution they deployed, which again had some backlash from Nadler, and that's pretty much where it's stood since then.
Nadler put his own solution on Github (Announcement post) and so far that seems to be the only fix whose functionality isn't shrouded in ambiguity and FUD.
I suspect no one at ST is eager to rekindle the bonfire in a public forum again, you may have more luck within the relative intimacy of an OLS ticket.
- If someone's post helped resolve your issue, please thank them by clicking "Accept as Solution".
- Please post an update with details once you've solved your issue. Your experience may help others.
