Displaying 20 results from an estimated 300 matches similar to: "Unifying CMake variable names used in checks across subprojects"
2020 Sep 22
2
Unifying CMake variable names used in checks across subprojects
> On Sep 22, 2020, at 15:28, Eric Christopher <echristo at gmail.com> wrote:
>
> From the "not largely affected" camp:
>
> - the churn doesn't feel that major for HAS_ and ...
> - the uniformity feels nice
>
> and in general feels nice and in pursuit of the longer term goals here.
>
> -eric
>
> On Tue, Sep 22, 2020 at 11:58 AM Petr
2020 Sep 25
2
Unifying CMake variable names used in checks across subprojects
> On Sep 24, 2020, at 23:52, Petr Hosek <phosek at chromium.org> wrote:
>
> Using more interface libraries is definitely the right direction and a modern way to use CMake. I'm not sure if we can get to a single interface target since different runtimes have different requirements. I was assuming that we would have one interface target per dependency and use the existing CMake
2019 Jan 24
2
[Release-testers] [8.0.0 Release] rc1 has been tagged
On Thu, 2019-01-24 at 19:58 +0100, Dimitry Andric via Release-testers
wrote:
> On 24 Jan 2019, at 01:49, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:
> >
> > 8.0.0-rc1 was just tagged (from the branch at r351980).
> >
> > It took a little longer than planned, but it's looking good.
> >
> > Please run the test
2018 Mar 16
2
How to get c++ function demangled name without parameters.
Hi all,
We know that 'ItaniumDemangle' has been added into llvm lib to resolve
demangling related issues.
And if we dump mangled function name '_Z3duti' into 'char
*llvm::itaniumDemangle(const char *mangled_name, char *buf, size_t *n, int
*status)', we will get 'dut(int)'.
So my question is:
How can I just get the function name 'dut' without parameters,
2018 Mar 16
0
How to get c++ function demangled name without parameters.
Hi Fangqing,
llvm::itaniumDemangle() doesn't yet provide this functionality, but I'm
working on adding it in now for the LLDB folks
(http://lists.llvm.org/pipermail/lldb-dev/2018-January/013186.html). I
should have a patch up Very Soon! If you would like I can CC you to it.
Thanks,
Erik
On 2018-03-16 2:15 PM, Fangqing Du via llvm-dev wrote:
> Hi all,
>
> We know that
2018 May 15
12
[PATCH libldm 00/12] New API: an ability to retrieve created device-mapper devices back after they have been created.
The main goal of these patch series is to implement a new API that allows to retrieve created device-mapper devices for volumes and partitions back after they have been created.
As part of this patch:
- required libdevmapper version was bumped to 1.02. I think it is safe because it was released more then 10 years ago;
- newer version of libdevmapper allowed to simplify code base a little bit;
-
2017 May 29
0
[PATCH] Add CMake build script
Description
===========
This patch adds support of CMake meta build system, so you can generate
Unix makefiles, VS 6.0-2017 projects and many more.
Features
========
* Win32 and Linux tested
* Travis CI test added
* Generates working Visual Studio 6.0-2017 solutions
* Generates working Unix Makefile
* Supported options (<option> - <default value>):
* `ENABLE_FLOATING_POINT` - on
2019 Nov 20
2
libunwind is not configured with -funwind-tables when building it for ARM Linux?
> On 18 Nov 2019, at 22:11, Peter Smith <peter.smith at linaro.org> wrote:
>
> On Mon, 18 Nov 2019 at 17:06, Sergej Jaskiewicz <jaskiewiczs at icloud.com <mailto:jaskiewiczs at icloud.com>> wrote:
>>
>>
>>
>> On 18 Nov 2019, at 19:55, Peter Smith <peter.smith at linaro.org> wrote:
>>
>> On Mon, 18 Nov 2019 at 15:23, Sergej
2005 Jan 05
1
rsync filename heuristics
On 5 Jan 2005, Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Tue, 2005-01-04 at 18:24 +0100, Robert Lemmen wrote:
> > hi rusty,
> >
> > i read on some webpage about rsync and debian that you wrote a patch to
> > rsync that let's it uses heuristics when deciding which local file to
> > use. could you tell me whether this is planned to be included in
2012 Jul 07
2
[LLVMdev] Crash using the JIT on x86 but work on x64
Hello everyone, i’m using LLVM (updated to 3.1 after seeing that bug, but it’s the same with 3.0) for running a bitcode on a C++ program, and Clang for compiling it. My code work perfectly, as expected on x64, but crash on x86. I’m on Windows 7 x64 and LLVM + Clang was compiled using Visual Studio 2010 (tested in both Release and Debug build). Project was make using CMake.
Here is my code:
2004 Jul 14
4
String overflow in safe_strcpy .
Just Installed 3.0.5rc1 and the problem persists unfortunately,
heres a sample of my log :
wins[15212]: [2004/07/12 12:31:03, 0] lib/util_str.c:safe_strcpy_fn(600)
Jul 12 12:31:03 mandrake1 nss_wins[15212]: ERROR: string overflow by 1
(9 - 8) in safe_strcpy [TAENO~EI.PDF]
Jul 12 12:31:03 mandrake1 nss_wins[15212]: [2004/07/12 12:31:03, 0]
lib/util_str.c:safe_strcpy_fn(600)
Jul 12 12:31:03
2013 Oct 18
1
[RFC/PATCH 2/3] core: MultiFS infrastructure added.
From: Raphael S. Carvalho <raphael.scarv at gmail.com>
MULTIFS SYNTAX:
(hd[disk number]:[partition number])/path/to/file
The meaning of this_fs was changed to improve the flexibility of the support.
Now, this_fs means the file system being currently used.
root_fs was created to save the context of the main file system (where ldlinux.sys lives in).
get_fs_info is a function pointer that
2016 Jun 19
2
Linker failures in debug build - compiler/linker poll?
This probably just works around a layering violation. Can you provide the
cmake line that produces a broken build?
Cheers,
Rafael
On Jun 18, 2016 7:34 AM, "Nicolai Hähnle" <llvm-dev at lists.llvm.org> wrote:
Hi,
since recently I'm getting linker failures in debug builds. The root cause
is that -fvisibility-inlines-hidden causes inline functions in explicit
template
2012 Nov 25
6
[LLVMdev] Improved Covered Default Switch detection
If cmake happens to detect GCC for the C compiler and Clang for the C++ compiler, then a manual override of either the C compiler or SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG is required. This has been happening on my Darwin build environments:
-- The C compiler identification is GNU 4.2.1
-- The CXX compiler identification is Clang 4.1.0
Without the manual overrides, all C sources fail to compile
2012 Aug 20
13
[PATCH 00/12] Multidisk support
Hello,
the following patches should get multidisk access working.
The syntax accepted is the following:
(hdx,y)/path/to/file
where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk.
the other accepted syntax is using MBR's 32 bits disk signature so for example:
(mbr:0x12345678,2)/foo/bar
would address
2020 Apr 08
2
Clarifying the supported ways to build libc++, libc++abi and libunwind
Thanks Shoaib for a great summary. To summarize this as an answer to Louis'
questions:
1. What is a "Standalone build"? What does it enable that a normal monorepo
build can't?
This means building any of the runtimes separately, where the runtime's
CMakeLists.txt (e.g. path/to/my/llvm-project/libcxx/CMakeLists.txt) is the
top-level one. The reason for using this variant is
2012 Mar 11
2
[patch] Threading support in ssh-agent
Hi all!
I do not know openssh patch policy so I am just sending
the patch to the mailing list. Sorry for inconvenience.
Ssh-agent seems to be too slow if you need to access thousands of
servers. This is a simple patch to enable threading in ssh2 authentication.
Patch adds "-p numthreads" option and defaults to the number of processors.
I've tested it as I could, but
2019 Nov 18
2
libunwind is not configured with -funwind-tables when building it for ARM Linux?
> On 18 Nov 2019, at 19:55, Peter Smith <peter.smith at linaro.org> wrote:
>
> On Mon, 18 Nov 2019 at 15:23, Sergej Jaskiewicz <jaskiewiczs at icloud.com <mailto:jaskiewiczs at icloud.com>> wrote:
>>
>> Hi Peter,
>>
>> Thanks for your response.
>>
>> On 18 Nov 2019, at 17:44, Peter Smith <peter.smith at linaro.org> wrote:
2018 Apr 11
2
[compiler-rt] r329776 - [XRay][compiler-rt] Fix osx-based builds
Hi Dean,
For me the build is still broken:
-- Builtin supported architectures: i386;x86_64;x86_64h
CMake Error at projects/compiler-rt/lib/xray/tests/CMakeLists.txt:21 (add_library):
add_library cannot create target "RTXRay.test.osx" because another target
with the same name already exists. The existing target is a static library
created in source directory
2018 Apr 11
0
[compiler-rt] r329776 - [XRay][compiler-rt] Fix osx-based builds
Hi Dean,
I have fixed the build failure in r329832.
In general, do you think it would be possible to perform the task using higher-level functions available from AddCompilerRT.cmake?
They were written exactly to avoid such errors.
Regards,
George
> On Apr 11, 2018, at 10:50 AM, George Karpenkov <ekarpenkov at apple.com> wrote:
>
> Hi Dean,
>
> For me the build is still