Huh - weird. I've never seen that warning appear. What system was this on?
The code you flagged gets called exactly once, so overhead isn't an issue. Just
puzzling why it would now suddenly appear after it has been there for years.
On Jun 14, 2012, at 11:21 AM, Orion Poplawski wrote:
> While t
While trying to debug some other stuff, I discovered that
opal_timer_linux_open() ends up setting the inexact floating point exception here:
/* numer is in MHz - convert to Hz and make an integer */
opal_timer_linux_freq = (opal_timer_t) cpu_f * 100;
I'm not sure if this is anythi
