No. of Recommendations: 0
rmhj says

I've seen probably more than my share of compiler bugs, but I'd do more testing before I was sure. It has probably been close to twenty years since I found a real one in an optimizer. In that case, the compiler did an invalid tail-recursion optimization. Shared storage between caller and callee (an array) made the optimization invalid, but it only blew up rarely (SMTP in my case).

Particularly, I'd be confirming that the code is actually wrong in the structure access. That sounds like a too-well-known, too-critical location for a bug like that. There are lots of other subtle ways this could go wrong.

I don't have access to the source code for the struct access, and can't read ARM code with any reliability. Apparently it takes a very specific set of conditions for this bug to manifest, and I rolled the magic number.

I've reported the bug, we'll see what the response is.
Print the post  

Announcements

What was Your Dumbest Investment?
Share it with us -- and learn from others' stories of flubs.
When Life Gives You Lemons
We all have had hardships and made poor decisions. The important thing is how we respond and grow. Read the story of a Fool who started from nothing, and looks to gain everything.
Community Home
Speak Your Mind, Start Your Blog, Rate Your Stocks

Community Team Fools - who are those TMF's?
Contact Us
Contact Customer Service and other Fool departments here.
Work for Fools?
Winner of the Washingtonian great places to work, and Glassdoor #1 Company to Work For 2015! Have access to all of TMF's online and email products for FREE, and be paid for your contributions to TMF! Click the link and start your Fool career.
Advertisement