search for: microsoftmangl

A long time ago, when I devised the grammar and structure of the Microsoft C++ name mangling scheme (decorated names), the document describing the object model and the name decoration scheme were made publically available. Perhaps this is still available publically, or perhaps Microsoft might be willing to share an up to date definition of the name-decoration grammar, especially in light of the

...>> There also has to be a way to communicate to llvm from clang that this >> symbol should not receive a prepended _. > I could swear that when I wrote that code I stuck a '\1' character in front of the name to prevent LLVM's mangler from doing anything to it (see lib/AST/MicrosoftMangle.cpp:162). (I knew the prepending of '_' characters was a problem, but I didn't know LLVM magically transformed chars it doesn't like into _xx_.) That is a magic marker that says "this is the literal name of this symbol, don't mangle it in the usual way." > > It...

...gas syntax. > There also has to be a way to communicate to llvm from clang that this > symbol should not receive a prepended _. I could swear that when I wrote that code I stuck a '\1' character in front of the name to prevent LLVM's mangler from doing anything to it (see lib/AST/MicrosoftMangle.cpp:162). (I knew the prepending of '_' characters was a problem, but I didn't know LLVM magically transformed chars it doesn't like into _xx_.) That is a magic marker that says "this is the literal name of this symbol, don't mangle it in the usual way." It looks lik...

...There also has to be a way to communicate to llvm from clang that this >>> symbol should not receive a prepended _. >> I could swear that when I wrote that code I stuck a '\1' character in front of the name to prevent LLVM's mangler from doing anything to it (see lib/AST/MicrosoftMangle.cpp:162). (I knew the prepending of '_' characters was a problem, but I didn't know LLVM magically transformed chars it doesn't like into _xx_.) That is a magic marker that says "this is the literal name of this symbol, don't mangle it in the usual way." >> &gt...

Hi, I'm trying to find a solution to the following problem: I need to generate a mangled name for given C++ function. Could I use llvm Mangler class for it? Regards, Blackbox dev team -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130509/0ed811f7/attachment.html>

...code 5's clang with the failure... [ 54%] [ 54%] Building CXX object lib/Analysis/CMakeFiles/LLVMAnalysis.dir/AliasAnalysisCounter.cpp.o Building CXX object lib/ExecutionEngine/CMakeFiles/LLVMExecutionEngine.dir/ExecutionEngine.cpp.o /sw/src/fink.build/llvm34-3.4-0/llvm-3.4/tools/clang/lib/AST/MicrosoftMangle.cpp:418:12: error: read-only variable is not assignable *I++ = 'A' + (Value & 0xf); ~~~~ ^

So I was taking a look at Microsoft C++ ABI support while on vacation, and ran into a major issue. Given the following llvm-ir: $ clang++ -S -emit-llvm -O3 mangling.cpp -o - -Xclang -cxx-abi -Xclang microsoft ; ModuleID = 'mangling.cpp' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-f80:128:128-v64:64:64-

...lso has to be a way to communicate to llvm from clang that this >>>> symbol should not receive a prepended _. >>> I could swear that when I wrote that code I stuck a '\1' character in front of the name to prevent LLVM's mangler from doing anything to it (see lib/AST/MicrosoftMangle.cpp:162). (I knew the prepending of '_' characters was a problem, but I didn't know LLVM magically transformed chars it doesn't like into _xx_.) That is a magic marker that says "this is the literal name of this symbol, don't mangle it in the usual way." >>>...

On Mon, Jun 19, 2017 at 12:49 PM Rui Ueyama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > We have clang/lib/AST/MicrosoftMangle.cpp, so looks like what I should do > is to write code that do the reverse of it. One thing I should be careful > is to produce the exact same outputs as Microsoft's UnDecorateSymbolName > function would output so that the behavior doesn't change between Windows > and non-Windo...

On Mar 1, 2014, at 7:15 PM, Chandler Carruth <chandlerc at google.com> wrote: > On Sat, Mar 1, 2014 at 5:59 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > The current guidelines [1] on the use of the struct keyword are too > restrictive and apparently ignored. They limit the use of struct to > PODs, citing broken compilers. > > The guidelines are

Hello Zachary, Sorry for replying so lately but It's been a week I'm thinking an working hard on your "dll memory buffer" idea to see if it works and give you feedbacks ! And it works pretty well until now : I shared on the list what I did : - create a .ASM file full of "int 3" instructions (to ensure that if we execute over the boundaries we instantly break. -