Hi John. On Thu, Mar 7, 2013 at 5:47 PM, John Meacham <[email protected]> wrote: > I belive it is okay because the 'casted' non-volatile pointer is only > used once. as in, there is never a non-volatile version of the pointer > that is used in more than one place that the compiler might try to > optimize out. Each use jhc will generate code that creates the pointer > relative to the volatile physicalAddr so it won't be able to merge > them.
Ah. It's good news for me. I understand that poke function spec isn't BUG. I will rewrite Cortex-M3 demo with extern_volatile.patch style. And Ajhc's volatile patch should be dropped. In my use case, ForeignData style doesn't be needed. Thank you for your time. -- Kiwamu Okabe _______________________________________________ jhc mailing list [email protected] http://www.haskell.org/mailman/listinfo/jhc
