| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
|\ \
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | | |
* cc-msvc-target:
test: Run cc-msvc-builtin-1923 test with suitable target triple
Detect: Add MSVC target triple component
|
| | | |
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
* cc-msvc-target:
test: Run cc-msvc-builtin-1923 test with suitable target triple
Detect: Add MSVC target triple component
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The test added by commit 4ef8cb85 (test: Add case for
__builtin_assume_aligned declaration in MSVC header, 2020-04-03,
v0.3.3~2^2) uses the MSVC `__cdecl` calling convention specifier.
That is not supported by all target ABIs, so update the test to
run CastXML using the `x86_64-pc-windows-msvc` target triple.
Fixes: #165
|
| |/
| |
| |
| | |
When `_MSC_VER` is among compiler predefines, the target ABI is MSVC.
|
|\ \
| |/ |
|
| | |
|
|\ \
| |/ |
|
| |\ |
|
|\ \ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For Windows targets, GNU compilers predefine `_WIN32` and `__MINGW32__`.
CastXML uses those to set the target triple correctly when using
`--castxml-cc-gnu`. Teach our fake GNU compiler in the test suite to
define these too. Otherwise CastXML does not add `gnu` to the target
triple. This causes the Windows-hosted Clang to choose `msvc` in the
default triple and enable MS compatibility, which is incorrect.
|
| | | |
|
|\ \ \
| | |/
| |/| |
|
| |\ \
| | |/ |
|
|\ \ \
| | |/
| |/| |
|
| |/
| |
| |
| |
| |
| | |
In commit f9a05da6 (RunClang: Tolerate __builtin_assume_aligned
declaration in MSVC header, 2020-03-31, v0.3.2~1^2) we left out a test
case. Add one now.
|
|\ \
| |/ |
|
| | |
|
|\ \
| |/ |
|
| |\ |
|
|\ \ \
| | |/
| |/| |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
MSVC tools 14.23 and above declare `__builtin_assume_aligned` in
`intrin0.h` with a signature incompatible with Clang's builtin. It is
guarded by `!defined(__clang__)` but that breaks when we simulate MSVC's
preprocessor. Rename the builtin via preprocessing to avoid the
conflict.
|
|\ \
| |/ |
|
| | |
|
| | |
|
|\ \
| |/ |
|
| |\ |
|
|\ \ \
| | |/
| |/| |
|
| |/
| |
| |
| |
| | |
Clang 9 introduced a `clang-cpp` shared library that we can optionally
use instead of linking to the static libraries.
|
| | |
|
|\ \
| |/ |
|
|/ |
|
|
|
|
| |
We've made modifications in every year since the last update.
|
| |
|
|\ |
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
Revise the logic from commit 60dc8284 (Version: Update version scheme to
distinguish release and dev versions, 2019-04-11, v0.2.0~2) to drop the
`-<count>` portion of the version number. This makes the version string
the same for versions built from a Git source tree and from a tarball.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Update the approach from commit 60dc8284 (Version: Update version scheme
to distinguish release and dev versions, 2019-04-11, v0.2.0~2) to prefer
`export-subst` information. This will allow exported source trees to be
imported into unrelated Git repositories while still using the original
upstream CastXML commit information.
|
|\ \
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | | |
* ppc64:
Detect: Drop detected predefined macros conflicting with Clang's
Detect: Fix GNU builtin include directory detection on ppc64
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The `llvm::StringRef` type now requires explicit conversion to
`std::string`. Such explicit conversions still work with older
versions of LLVM/Clang too.
|
| | |
| | |
| | |
| | | |
CastXML already compiles and passes all tests against this version.
|
| | |
| | |
| | |
| | |
| | | |
Extend the `--castxml-output=1` format to support decltype.
Create a dump node for the underlying type.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Clang renamed `clang/AST/TypeNodes.{def => inc}` and replaced the
`createDriverOptTable` factory with a singleton returned by
`getDriverOptTable`.
|
| | |
| | |
| | |
| | |
| | |
| | | |
LLVM now compiles as C++14. It does not provide `llvm::make_unique`.
The `clang::CompilerInvocation::CreateFromArgs` signature now accepts an
`ArrayRef` for the argument range instead of iterators.
|