aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Demangle/ItaniumDemangle.cpp
AgeCommit message (Collapse)AuthorFilesLines
2018-04-12[demangler] Add a partial demangling API for LLDB.Erik Pilkington1-0/+191
This parses a mangled name into an AST (typically an intermediate stage in itaniumDemangle) and provides some functions to query certain properties or print certain parts of the demangled name. Differential revision: https://reviews.llvm.org/D44668 llvm-svn: 329951
2018-04-12[demangler] NFC: Some refactoring to support partial demangling.Erik Pilkington1-42/+97
I'm committing this to libcxxabi too so that the two demanglers remain as simular as possible. llvm-svn: 329950
2018-04-09[demangler] Support for fold expressions.Erik Pilkington1-3/+126
llvm-svn: 329601
2018-04-09[demangler] Support for <data-member-prefix>.Erik Pilkington1-0/+9
llvm-svn: 329600
2018-04-09[demangler] Support for partially substituted sizeof....Erik Pilkington1-1/+24
llvm-svn: 329599
2018-03-26[demangler] Fix a bug in r328464 found by oss-fuzz.Erik Pilkington1-2/+27
llvm-svn: 328507
2018-03-25[demangler] Use a back-patching scheme to resolve forward references.Erik Pilkington1-40/+79
Strictly in a conversion operator's type, a <template-param> refers to a <template-arg> that is further ahead in the mangled name. Instead of doing a second parse to resolve these, introduce a ForwardTemplateReference Node and back-patch the referenced <template-arg> when we're in the right context. This is also a correctness fix, previously we would only do a second parse if the <template-param> was out of bounds in the current set of <template-args>. This lead to misdemangles (gasp!) when the conversion operator was a member of a templated struct, for instance. llvm-svn: 328464
2018-03-25[demangler] Tweak how parameter pack sizes are determined.Erik Pilkington1-210/+105
Rather than eagerly propagating up parameter pack sizes in Node ctors, find the parameter pack size during printing. This is being done to support back-patching forward referencing <template-param>s. llvm-svn: 328463
2018-03-25[demangler] Support for clang's enable_if attribute.Erik Pilkington1-6/+35
Fixes PR33569. llvm-svn: 328462
2018-03-21Reapply Support layering fixes.David Blaikie1-4/+6
Compiler.h is used by Demangle (which Support depends on) - so sink it into Demangle to avoid a circular dependency DataTypes.h is used by llvm-c (which Support depends on) - so sink it into llvm-c. DataTypes.h could probably be fixed the other way - making llvm-c depend on Support instead of Support depending on llvm-c - if anyone feels that's the better option, happy to work with them on that. I /think/ this'll address the layering issues that previous attempts to commit this have triggered in the Modules buildbot, but I haven't been able to reproduce that build so can't say for sure. If anyone's having trouble with this - it might be worth taking a look to see if there's a quick fix/something small I missed rather than revert, but no worries. llvm-svn: 328123
2018-03-21Revert layering changesJonas Devlieghere1-6/+4
This reverts: r328072 "Move Compiler.h from Support to Demangler to fix layering." r328073 "Fix the actual user of DataTypes.h in llvm-c to avoid the circular dependency" Failing bots: http://green.lab.llvm.org/green/job/clang-stage2-coverage-R/ http://green.lab.llvm.org/green/job/clang-stage2-configure-Rlto/ llvm-svn: 328085
2018-03-21Move Compiler.h from Support to Demangler to fix layering.David Blaikie1-4/+6
Support depends on Demangle (Support/Unix/Signals.inc), so Demangle including Support/Compiler.h created a circular dependency. Leave a forwarding shim of Compiler.h because it makes more sense for users (a deeper fix might involve splitting Support into lower and upper Support - but that also sounds a bit weird/awkward) than thinking about the dependency on the Demangler. llvm-svn: 328072
2018-03-19[demangler] Recopy the demangler from libcxxabi.Erik Pilkington1-3943/+4521
Some significant work has gone into libcxxabi's copy of this file: - Uses an AST to represent mangled names. - Support/bugfixes for many C++ features. - Uses LLVM coding style. llvm-svn: 327859
2017-12-19Silence a bunch of implicit fallthrough warningsAdrian Prantl1-1/+2
llvm-svn: 321114
2017-05-28[ItaniumDemangle] Fix a exponential string copying bugErik Pilkington1-0/+3
This is a port of libcxxabi's r304113. llvm-svn: 304114
2017-05-27[Demangler] copy changes made in libcxxabi's r303718 to ItaniumDemangleErik Pilkington1-21/+28
llvm-svn: 304053
2017-05-24Demangler: Fix constructor cv qualifier handlingTamas Berghammer1-0/+2
Previously if we parsed a constructor then we set parsed_ctor_dtor_cv to true and never reseted it. This causes issue when a template argument references a constructor (e.g. type of lambda defined inside a constructor) as we will have the parsed_ctor_dtor_cv flag set what will cause issues when parsing later arguments. Differential Revision: https://reviews.llvm.org/D33385 libcxxabi change: https://reviews.llvm.org/rL303737 llvm-svn: 303738
2017-05-18Revert r303375 "LLVM_FALLTHROUGH instead of fall-through comment."Rui Ueyama1-1/+1
This reverts commit r303375 since it didn't compile. llvm-svn: 303377
2017-05-18LLVM_FALLTHROUGH instead of fall-through comment.Galina Kistanova1-1/+1
llvm-svn: 303375
2017-05-18Reduce gcc-7 warnings by fall-through comments.Galina Kistanova1-1/+1
llvm-svn: 303365
2017-01-31Add support for demangling C++11 thread_local variables. David Bozier1-0/+23
In clang, the grammar for mangling for these names are "<special-name> ::= TW <object name>" for wrapper variables or "<special-name> ::= TH <object name>" for initialization variables. Initial change was made in libccxxabi r293638 llvm-svn: 293643
2017-01-27Fix ASAN failure in cxa_demangleMehdi Amini1-1/+2
Found with ASAN + libFuzzer by Kostya Serebryany <kcc@google.com> llvm-svn: 293330
2017-01-24Demangle: correct demangling for CV-qualified functionsSaleem Abdulrasool1-6/+9
When demangling a CV-qualified function type with a final reference type parameter, we would treat the reference type parameter as a r-value ref accidentally. This would result in the improper decoration of the function type itself. Resolves PR31741! llvm-svn: 292976
2017-01-24Demangle: use named values for CV qualifiersSaleem Abdulrasool1-12/+18
Rather than hard-coding magic values of 1, 2, 4 (bit-field), use an enum to name the values. NFC. llvm-svn: 292975
2017-01-24Demangle: avoid butchering parameter typeSaleem Abdulrasool1-2/+2
When demangling a CV-qualified function type with a final parameter with a reference type, we would insert the CV qualification on the parameter rather than the function, and in the process adjust the insertion point by one extra, splitting the type name. This avoids doing so, even though the attribution is still incorrect. llvm-svn: 292965
2017-01-20Revert "Demangle: only demangle mangled symbols"Saleem Abdulrasool1-10/+1
This reverts SVN r286795. This was incorrect the demangler is expected to be able to demangle types as well as functions. This makes the behaviour of itaniumDemangle similar to __cxa_demangle once more. llvm-svn: 292573
2016-11-20Demangle: remove references to allocator for default allocatorSaleem Abdulrasool1-50/+29
The demangler had stopped using a custom allocator but had not been updated to remove the use of the explicit allocator passing. This removes that as we do not need to do anything special here anymore. This just makes the code more compact. NFC. llvm-svn: 287472
2016-11-20Demangle: remove unnecessary typedef for std::vectorSaleem Abdulrasool1-5/+3
We could create a local typedef for std::vector called Vector. Inline the use of std::vector rather than use the typedef. NFC. llvm-svn: 287471
2016-11-20Demangle: replace custom typedef for std::string with std::stringSaleem Abdulrasool1-41/+37
We created a local typedef for `std::basic_string<char, std::char_traits<char>>` which is just `std::string`. Remove the local typedef and propagate the type information through the rest of the demangler. NFC. llvm-svn: 287470
2016-11-20Demangle: use direct member initialization (NFC)Saleem Abdulrasool1-14/+7
Prefer direct member initialization over the explicit out-of-line initialization for the construction of the local type. NFC. llvm-svn: 287469
2016-11-14Demangle: only demangle mangled symbolsSaleem Abdulrasool1-1/+10
Only attempt to demangle symbols which have the itanium C++ prefix of `_Z`. This ensures that we do not treat any symbol name as a managled named. We would previously treat a C function `f` as a mangled name and decode that to `float` incorrectly. While it is easy to add tests for this, Mehdi recommended against introducing tests for the demangler as libc++abi should cover the testing. llvm-svn: 286795
2016-09-06Avoid using alignas and constexpr.Rafael Espindola1-136/+5
This requires removing the custom allocator, since Demangle cannot depend on Support and so cannot use Compiler.h. llvm-svn: 280750
2016-09-06Fix ItaniumDemangle.cpp build with MSVC 2013Reid Kleckner1-18/+19
llvm-svn: 280740
2016-09-06Add an c++ itanium demangler to llvm.Rafael Espindola1-0/+4431
This adds a copy of the demangler in libcxxabi. The code also has no dependencies on anything else in LLVM. To enforce that I added it as another library. That way a BUILD_SHARED_LIBS will fail if anyone adds an use of StringRef for example. The no llvm dependency combined with the fact that this has to build on linux, OS X and Windows required a few changes to the code. In particular: No constexpr. No alignas On OS X at least this library has only one global symbol: __ZN4llvm16itanium_demangleEPKcPcPmPi My current plan is: Commit something like this Change lld to use it Change lldb to use it as the fallback Add a few #ifdefs so that exactly the same file can be used in libcxxabi to export abi::__cxa_demangle. Once the fast demangler in lldb can handle any names this implementation can be replaced with it and we will have the one true demangler. llvm-svn: 280732
generated by cgit v1.1 at 2025-10-18 11:54:56 +0000