chiasa.men via llvm-dev
2021-Sep-15 09:58 UTC
[llvm-dev] __FUNCTION__ - MS: string literal vs. GCC: string
Is there a way to tell clang to adapt to the microsoft way of defining __FUNCTION__ as string literal and not as string? I stumbled upon this problem and am obviously not alone: https://stackoverflow.com/questions/4773941/wide-version-of-function-on-linux/ 51381572#51381572 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210915/980052c1/attachment.html>
David Blaikie via llvm-dev
2021-Sep-15 20:38 UTC
[llvm-dev] __FUNCTION__ - MS: string literal vs. GCC: string
this'd be more suitable on cfe-dev (moving to cfe-dev, llvm-dev to bcc) - though might present some challenges in compatibility with GCC if GCC's doing it differently. I guess in ms-mode (clang-cl) it should/could be done in the MS-way. On Wed, Sep 15, 2021 at 2:59 AM chiasa.men via llvm-dev < llvm-dev at lists.llvm.org> wrote:> Is there a way to tell clang to adapt to the microsoft way of defining > __FUNCTION__ as string literal and not as string? > > I stumbled upon this problem and am obviously not alone: > > > https://stackoverflow.com/questions/4773941/wide-version-of-function-on-linux/51381572#51381572 > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210915/fdef760c/attachment.html>