<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Dec 10, 2013, at 6:43 AM, H.J. Lu <<a href="mailto:hjl.tools@gmail.com">hjl.tools@gmail.com</a>> wrote:<br><div><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote type="cite"><blockquote type="cite">This may break builds where others added code relying on these patches,<br>but please *do not* revert this commit. Instead, we will prepare patches<br>which fix the failures.<br><br>Reverts the following commits:<br>r168306: "[asan] support x32 mode in the fast stack unwinder. Patch by H.J. Lu"<br>r168356: "[asan] more support for powerpc, patch by Peter Bergner"<br>r196489: "[sanitizer] fix the ppc32 build (patch by Jakub Jelinek)"<br></blockquote><br><br>As one of the authors of these patches, what is the rational for reverting them?<br><br></blockquote><br>libsanitizer is used in both llvm and GCC. What takes for GCC developers<br>to contribute changes to libsanitizer?<br></div></blockquote></div><br><div>As far as I'm concerned, there is no such distinction. You either agree to the llvm policies and have commit access to LLVM - or not. It doesn't matter what other projects you work with.</div><div><br></div><div>-Chris</div></body></html>