[libunwind] r332512 - [OR1K] Add a dedicated PC register to register state.

Author: whitequark Date: Wed May 16 12:09:41 2018 New Revision: 332512 URL: http://llvm.org/viewvc/llvm-project?rev=332512&view=rev Log: [OR1K] Add a dedicated PC register to register state. Before this commit, R9, the link register, was used as PC register. However, a stack frame may have R9 not

[libunwind] r332513 - [OR1K] Add the EPCR special-purpose register to register state.

Author: whitequark Date: Wed May 16 12:09:48 2018 New Revision: 332513 URL: http://llvm.org/viewvc/llvm-project?rev=332513&view=rev Log: [OR1K] Add the EPCR special-purpose register to register state. This makes it possible to unwind hardware exception stack frames, which necessarily save every r

[libunwind] r321440 - [libunwind] Avoid using C++ headers.

Author: whitequark Date: Mon Dec 25 05:06:09 2017 New Revision: 321440 URL: http://llvm.org/viewvc/llvm-project?rev=321440&view=rev Log: [libunwind] Avoid using C++ headers. This is useful for building libunwind on libcxx-free systems. Modified: libunwind/trunk/src/DwarfParser.hpp Modified:

[libunwind] r321441 - [libunwind] convert error logs to _LIBUNWIND_LOG/_LIBUNWIND_LOG0.

Author: whitequark Date: Mon Dec 25 05:27:56 2017 New Revision: 321441 URL: http://llvm.org/viewvc/llvm-project?rev=321441&view=rev Log: [libunwind] convert error logs to _LIBUNWIND_LOG/_LIBUNWIND_LOG0. Use the `_LIBUNWIND_LOG` and `_LIBUNWIND_LOG0` macros instead of the explicit `fprintf` call.

[libunwind] r321442 - [libunwind] fix a typo in r321441.

Author: whitequark Date: Mon Dec 25 05:42:41 2017 New Revision: 321442 URL: http://llvm.org/viewvc/llvm-project?rev=321442&view=rev Log: [libunwind] fix a typo in r321441. Modified: libunwind/trunk/src/DwarfParser.hpp Modified: libunwind/trunk/src/DwarfParser.hpp URL: http://llvm.org/viewvc

[libunwind] r321445 - [libunwind] Add proper support for DWARF unwind on bare metal.

Author: whitequark Date: Mon Dec 25 09:05:07 2017 New Revision: 321445 URL: http://llvm.org/viewvc/llvm-project?rev=321445&view=rev Log: [libunwind] Add proper support for DWARF unwind on bare metal. Right now, ARM EHABI unwind on bare metal expects to find the symbols __exidx_start and __exidx_e

Re: [libunwind] r321440 - [libunwind] Avoid using C++ headers.

mits::max() && "pointer overflow"); ~^ Sorry, I missed this. Any idea on reformulating the assert in a way that does not require libcxx headers? Not having them significantly simplifies bare-metal builds... thanks... don On Mon, Dec 25, 2017 at 5:06 AM, wh

[libunwind] r321446 - [libunwind] Unbreak debug builds after r321440.

Author: whitequark Date: Mon Dec 25 12:04:47 2017 New Revision: 321446 URL: http://llvm.org/viewvc/llvm-project?rev=321446&view=rev Log: [libunwind] Unbreak debug builds after r321440. Modified: libunwind/trunk/src/DwarfParser.hpp Modified: libunwind/trunk/src/DwarfParser.hpp URL: http://ll

Re: [libunwind] r321440 - [libunwind] Avoid using C++ headers.

ed this. Any idea on reformulating the assert in a way that does not require libcxx headers? Not having them significantly simplifies bare-metal builds... Well, assuming pint_t is some unsigned integer type, the max can be found like this: pint_t max_pint_t = ~0; So, that could be used in a p

Re: [libunwind] r321440 - [libunwind] Avoid using C++ headers.

s/dhinton/projects/llvm_project/libunwind/src/DwarfParser.hpp:559:28: error: no member named 'numeric_limits' in namespace 'std' assert(length < std::numeric_limits::max() && "pointer overflow"); ~^ Sorry, I missed this. Any idea on reformulating the assert in a w

[libunwind] r321448 - [libunwind] Remove dubious template function. NFC.

Author: whitequark Date: Mon Dec 25 13:08:41 2017 New Revision: 321448 URL: http://llvm.org/viewvc/llvm-project?rev=321448&view=rev Log: [libunwind] Remove dubious template function. NFC. Per review by Don Hinton. Modified: libunwind/trunk/src/DwarfParser.hpp Modified: libunwind/trunk/src/D

Re: [libunwind] r321440 - [libunwind] Avoid using C++ headers.

vm_project/libunwind/src/DwarfParser.hpp:559:28: error: no member named 'numeric_limits' in namespace 'std' assert(length < std::numeric_limits::max() && "pointer overflow"); ~^ Sorry, I missed this. Any idea on reformulating the assert in a way that does n

[PATCH] D17952: [Clang] Accept absolute paths in the -fuse-ld option

whitequark created this revision. whitequark added a reviewer: majnemer. whitequark added a subscriber: cfe-commits. whitequark set the repository for this revision to rL LLVM. Herald added a subscriber: aemerson. This patch extends the -fuse-ld option to accept a full path to an executable and us

Re: [PATCH] D17952: [Clang] Accept absolute paths in the -fuse-ld option

whitequark marked an inline comment as done. Comment at: cfe/trunk/lib/Driver/ToolChain.cpp:352 @@ +351,3 @@ +return UseLinker; +} else { + // If we're passed -fuse-ld= with no argument, or with the argument ld, silvas wrote: > No need for else af

Re: [PATCH] D17952: [Clang] Accept absolute paths in the -fuse-ld option

whitequark updated this revision to Diff 50021. whitequark added a comment. Windows compatibility Repository: rL LLVM http://reviews.llvm.org/D17952 Files: cfe/trunk/lib/Driver/ToolChain.cpp Index: cfe/trunk/lib/Driver/ToolChain.cpp

Re: [PATCH] D17952: [Clang] Accept absolute paths in the -fuse-ld option

whitequark updated this revision to Diff 50097. whitequark added a comment. Added a test Repository: rL LLVM http://reviews.llvm.org/D17952 Files: cfe/trunk/lib/Driver/ToolChain.cpp cfe/trunk/test/Driver/fuse-ld.c Index: cfe/trunk/test/Driver/fuse-ld.c ==

Re: [PATCH] D17952: [Clang] Accept absolute paths in the -fuse-ld option

This revision was automatically updated to reflect the committed changes. Closed by commit rL262996: Accept absolute paths in the -fuse-ld option. (authored by whitequark). Repository: rL LLVM http://reviews.llvm.org/D17952 Files: cfe/trunk/lib/Driver/ToolChain.cpp cfe/trunk/test/Driver/f