+Jeff To cite some of the previous discussions (http://lists.llvm.org/pipermail/cfe-dev/2016-May/048822.html )
Brian: On our side, we use such pre-link passes to interface with the specifics of our built-in function library. For example, we transform printf calls into a form that interacts with our library. We also transform calls to pipe functions, kernel enqueue related functions, and transform calls to the atomic functions to corresponding LLVM atomic instructions (and keep track of the memory scope elsewhere currently). You may have noticed that we have a proposal out to enable the atomic instructions to directly carry a memory scope. Jeff: We have similar passes related to builtin functions but they are rather specific to our implementation and not too complex. Thanks. Sam -----Original Message----- From: Liu, Yaxun (Sam) Sent: Thursday, May 26, 2016 11:44 AM To: reviews+d20681+public+7364792746786...@reviews.llvm.org; rich...@metafoo.co.uk; anastasia.stul...@arm.com Cc: Stellard, Thomas <tom.stell...@amd.com>; cfe-commits@lists.llvm.org; Sumner, Brian <brian.sum...@amd.com> Subject: RE: [PATCH] D20681: Add target-specific pre-linking passes to Clang + Brian -----Original Message----- From: Tom Stellard [mailto:thomas.stell...@amd.com] Sent: Thursday, May 26, 2016 11:11 AM To: Liu, Yaxun (Sam) <yaxun....@amd.com>; rich...@metafoo.co.uk; anastasia.stul...@arm.com Cc: Stellard, Thomas <tom.stell...@amd.com>; cfe-commits@lists.llvm.org Subject: Re: [PATCH] D20681: Add target-specific pre-linking passes to Clang tstellarAMD added a comment. Can you give some examples of what pre-link passes may be required? http://reviews.llvm.org/D20681 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
