search for: isacceptablechar

Displaying 5 results from an estimated 5 matches for "isacceptablechar".

2012 Apr 02
0
[LLVMdev] [PATCH] Output UTF-8-encoded characters as identifier characters into assembly by default.
...\t"; AscizDirective = "\t.asciz\t"; diff --git a/lib/Target/Mangler.cpp b/lib/Target/Mangler.cpp index 53ad155..786a0c5 100644 --- a/lib/Target/Mangler.cpp +++ b/lib/Target/Mangler.cpp @@ -22,12 +22,13 @@ #include "llvm/ADT/Twine.h" using namespace llvm; -static bool isAcceptableChar(char C, bool AllowPeriod) { +static bool isAcceptableChar(char C, bool AllowPeriod, bool AllowUTF8) { if ((C < 'a' || C > 'z') && (C < 'A' || C > 'Z') && (C < '0' || C > '9') && C != ...
2013 Mar 29
0
[LLVMdev] Print Global Prefix Issue
> Hey, > > I have an odd problem with printing prefixed global symbols in my > AsmPrinter. > > In my MCAsmInfo subclass implementation, I set > > GlobalPrefix = "%"; > > > because my assembler needs this to avoid name collisions. > Now, whenever a global symbol (be it a label, mbb operand ,etc.) gets > printed, it is encapsulated in quotes.
2013 Mar 29
2
[LLVMdev] Print Global Prefix Issue
Hey, I have an odd problem with printing prefixed global symbols in my AsmPrinter. In my MCAsmInfo subclass implementation, I set GlobalPrefix = "%"; because my assembler needs this to avoid name collisions. Now, whenever a global symbol (be it a label, mbb operand ,etc.) gets printed, it is encapsulated in quotes. With other chars than '%' everything is okay... I also
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
Looks to me like it converted the ? into the ascii hexadecimal representation _3F_. I don't think another underscore was pre-pended. This is probably thanks to lib/Target/Mangler.cpp. You'll want to let ? be treated as an acceptable character. static bool isAcceptableChar(char C, bool AllowPeriod) { if ((C < 'a' || C > 'z') && (C < 'A' || C > 'Z') && (C < '0' || C > '9') && C != '_' && C != '$' && C != '@' &&...
2011 Nov 25
5
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
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-