From: Paul Mackerras <[EMAIL PROTECTED]> Date: Thu, 11 May 2006 07:05:24 +1000
> No, Richard has a point, it's not the value that is the concern, it's > the address, which gcc could assume is still valid after a barrier. > Drat. Oh right, and that's currently part of why we obfuscate the address computation with the RELOC_HIDE() buisness. Once we expose what's really going on with something like __thread, gcc can now be "smart" about it. - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
