Re: [cfe-users] Code locations from the Memory Sanitizer

2017-04-28 Thread Erik de Castro Lopo via cfe-users
Rainer Gerhards wrote: > I often need to set the ASAN_SYMBOLIZER_PATH: > > https://clang.llvm.org/docs/AddressSanitizer.html#id4 > > It often tends to be wrong by package default... Bingo! In my case, since I'm using Memory Sanitizer I needed to set MSAN_SYMBOLIZER_PATH rather than ASAN_SYMBOL

Re: [cfe-users] RFC v2: Re: cacheflush.2

2020-12-11 Thread Alejandro Colomar (man-pages) via cfe-users
Hi Michael, On 12/11/20 9:15 AM, Michael Kerrisk (man-pages) wrote: > i Alex, > > On 12/10/20 9:56 PM, Alejandro Colomar (man-pages) wrote: >> Hi all, >> >> v2: >> >> [ >> NOTES >>Unless you need the finer grained control that this system >>call provides, you probably want to

[cfe-users] RFC v2: Re: cacheflush.2

2020-12-11 Thread Alejandro Colomar (man-pages) via cfe-users
Hi all, v2: [ NOTES Unless you need the finer grained control that this system call provides, you probably want to use the GCC built-in function __builtin___clear_cache(), which provides a more portable interface: void __builtin___clear_cache(vo

Re: [cfe-users] cacheflush.2

2020-12-11 Thread Alejandro Colomar (man-pages) via cfe-users
Hi Heinrich, It looks like a bug (or at least an undocumented divergence from GCC) in Clang/LLVM. Or I couldn't find the documentation for it. Clang uses 'char *': https://github.com/llvm/llvm-project/blob/7faf62a80bfc3a9dfe34133681fcc31f8e8d658b/clang/include/clang/Basic/Builtins.def#L583 GCC

Re: [cfe-users] cacheflush.2

2020-12-11 Thread Alejandro Colomar (man-pages) via cfe-users
It looks like GCC recently moved from 'char *' to 'void *'. This SO question[1] (4 years ago) quotes the GCC docs and they had 'char *'. Maybe Clang hasn't noticed the change. I'll report a bug. [1]: https://stackoverflow.com/q/35741814/6872717 On 12/9/20 8:15 PM, Alejandro Colomar (man-pages) wr

[cfe-users] RFC v3: Re: cacheflush.2

2020-12-11 Thread Alejandro Colomar (man-pages) via cfe-users
Hi all, Please review this text: [ NOTES Unless you need the finer grained control that this system call provides, you probably want to use the GCC built-in function __builtin___clear_cache(), which provides a more portable interface: void __bui

[cfe-users] RFC v4: Re: cacheflush.2

2020-12-11 Thread Alejandro Colomar (man-pages) via cfe-users
I forgot to add a junk to the text. v4: NOTES Unless you need the finer grained control that this system call provides, you probably want to use the GCC built-in function __builtin___clear_cache(), which provides a portable interface across platforms supported

Re: [cfe-users] RFC v2: Re: cacheflush.2

2020-12-11 Thread Michael Kerrisk (man-pages) via cfe-users
i Alex, On 12/10/20 9:56 PM, Alejandro Colomar (man-pages) wrote: > Hi all, > > v2: > > [ > NOTES >Unless you need the finer grained control that this system >call provides, you probably want to use the GCC built-in >function __builtin___clear_cache(), which pr

Re: [cfe-users] cacheflush.2

2020-12-21 Thread Alejandro Colomar (man-pages) via cfe-users
Hello Martin, Thanks for the correction! Then the prototypes that changes from 'char *' to 'void *' in r269082 were not exposed to the user, right? I guess then those are just internal implementation where GCC did use 'char *'. Where is the actual prototype exposed to the user declared? Thanks,

[cfe-users] Ping: cacheflush.2

2020-12-21 Thread Alejandro Colomar (man-pages) via cfe-users
Hi Martin, I sent you an email, but I received a "delivery failure". If you're reading this from a list, could you answer, please? Thanks, Alex On 12/14/20 11:34 PM, Alejandro Colomar (man-pages) wrote: > Hello Martin, > > Thanks for the correction! > Then the prototypes that changes from 'cha

Re: [cfe-users] Ping: cacheflush.2

2020-12-21 Thread Alejandro Colomar (man-pages) via cfe-users
Hi Martin, Thanks! It's good to learn some GCC internal details :) Cheers, Alex On 12/18/20 5:51 PM, Martin Sebor wrote: > On 12/18/20 3:42 AM, Alejandro Colomar (man-pages) wrote: >> Hi Martin, >> >> I sent you an email, but I received a "delivery failure". >> If you're reading this from a li

[cfe-users] Ping: [PATCH v6] cacheflush.2: Document __builtin___clear_cache() as a more portable alternative

2020-12-21 Thread Alejandro Colomar (man-pages) via cfe-users
Ping On 12/15/20 2:30 PM, Alejandro Colomar wrote: > Reported-by: Heinrich Schuchardt > Signed-off-by: Alejandro Colomar > Cc: Martin Sebor > Cc: Dave Martin > --- > > v6: > - GCC has always exposed 'void *', as Martin Sebor noted. > It's Clang (and maybe others) that (following GCC's docs)

Re: [cfe-users] [PATCH v6] cacheflush.2: Document __builtin___clear_cache() as a more portable alternative

2020-12-21 Thread Michael Kerrisk (man-pages) via cfe-users
On 12/15/20 2:30 PM, Alejandro Colomar wrote: > Reported-by: Heinrich Schuchardt > Signed-off-by: Alejandro Colomar > Cc: Martin Sebor > Cc: Dave Martin > --- > > v6: > - GCC has always exposed 'void *', as Martin Sebor noted. > It's Clang (and maybe others) that (following GCC's docs) > e

Re: [cfe-users] .deb package for LibC++

2017-02-13 Thread Duncan P. N. Exon Smith via cfe-users
+Eric Eric, do you know? > On 2017-Feb-12, at 13:43, Michal Jaszczyk via cfe-users > wrote: > > Hey, > > I'm trying to set up my Ubuntu Yakkety dev environment to use Clang and > LibC++. > > I'm trying to use Clang 4.0. It is not available in Yakkety b

Re: [cfe-users] Getting variable names in LLVM IR

2017-02-14 Thread Duncan P. N. Exon Smith via cfe-users
> On 2017-Feb-13, at 23:10, Subhendu Malakar via cfe-users > wrote: > > Hi, > I'm a newbie in LLVM environment. > > I'm trying to generate the LLVM IR of a c file using clang. The command line > argument I'm passing is as : > "clang -O0

Re: [cfe-users] complie clang with clang

2017-03-21 Thread Duncan P. N. Exon Smith via cfe-users
> On 2017-Mar-21, at 06:51, Masaru Tsuchiyama via cfe-users > wrote: > > Hi. > > I'm trying to complie clang with clang. This should be fairly well documented. Try these: http://clang.llvm.org/get_started.html http://llvm.org/docs/CMake.html http://llvm.org/d

Re: [cfe-users] question about building

2017-04-24 Thread Duncan P. N. Exon Smith via cfe-users
+cfe-dev; bcc:cfe-users (this is more of a development question than a user question, AFAICT) > On Apr 17, 2017, at 08:18, Michael Mitchell via cfe-users > wrote: > > I'm new to LLVM and also new to Cmake. I've checked out multiple LLVM > projects including clan

[cfe-users] Using clang-format to format old style C source code

2018-02-25 Thread Jose-Marcio Martins da Cruz via cfe-users
Hello, I'm trying to use clang-format to format source files of a project, nowadays done with the help of indent. I'm trying to get an old tradition thing like : int myfunction(a, b) inta; char *b; { ... But, playing with .clang-format file, what I have is always something like :

Re: [cfe-users] Crash reporting for inline functions

2018-03-30 Thread Duncan P. N. Exon Smith via cfe-users
at 16:28, Michael Eisel via cfe-users > wrote: > > Hi, > > I've been playing around with a stack trace of inlined functions, e.g.: > > void __attribute__((always_inline)) f1() { > f2(); > } > > void __attribute__((noinline)) f2() { > f3()

Re: [cfe-users] App security and the __FILE__ macro

2018-04-12 Thread Duncan P. N. Exon Smith via cfe-users
`strrchr(__FILE__, '/')+1` should get resolved at compile-time whenever you have optimizations on. > On Apr 12, 2018, at 15:38, Rick Mann via cfe-users > wrote: > > The higher-ups decided we needed penetration testing of our app. One of their > concerns was that if

[cfe-users] PostgreSQL 12 build issues on Solaris 11.4

2019-10-07 Thread Dechaux Eric CEN (BCQ STIG) via cfe-users
Hello, With the official llvm/clang release for Solaris 11.4 I tried to build PostgreSQL 12 with JIT enabled. JIT uses LLVM. However, the build fails with the following error : gmake[2] : on entre dans le répertoire « /tmp/build/pg12/postgresql-12.0/src/backend/jit/llvm » g++ -Wall -Wpointer

[cfe-users] Problem with installing clang-3.8.0

2020-06-09 Thread Kwiatek, Michal (Nokia - PL/Wroclaw) via cfe-users
Hi, I have troubles with installing clang 3.8.0 I am able to install versions such as 6.0 or 10 but I cannot install 3.8.0 When I write: `sudo apt-get install clang-3.8.0` I get following message (screen included) Os version: Ubuntu 20.04 ___ cfe-users

[cfe-users] how to build latest version of Clang

2020-08-18 Thread Jost, Gabriele (ARC-TNC)[Supersmith] via cfe-users
Hello Fellow Clang users, My clang install is still clang 9.0 and I would like to upgrade to the latest release. I am not sure what the latest version is. I saw that there clang 12 still in progress, but on the download page, I only see clang 10. So I followed the instructions here, because I ne

[cfe-users] building clang for target off

2018-04-30 Thread Jost, Gabriele (ARC-TNC)[CSRA, LLC] via cfe-users
Hello, I am trying to build clang with GPU support, in particular with support for OpenMP target offload. I want to build for a Xeon+Nvidia GPU. I did this: git clone https://github.com/clang-ykt/openmp.git and built the OpenMP libomp.so Then I try this: git clone https://github.com/clang-ykt/libo

[cfe-users] building clang for target offload

2018-04-30 Thread Jost, Gabriele (ARC-TNC)[CSRA, LLC] via cfe-users
Hello, I am trying to build clang with GPU support, in particular with support for OpenMP target offload. I want to build for a Xeon+Nvidia GPU. I did this: git clone https://github.com/clang-ykt/openmp.git and built the OpenMP libomp.so Then I try this: git clone https://github.com/clang-ykt/libo

[cfe-users] clang and mcmodel=medium

2018-04-30 Thread Jost, Gabriele (ARC-TNC)[CSRA, LLC] via cfe-users
Hi, I have some benchmarks where I have to use mcmodel=medium, but clang does not seem to have a flag corresponding to this. I was wondering if there is recommended way around this. Greetings, Gabriele ___ cfe-users mailing list cfe-users@lists.llvm.org

<    8   9   10   11   12   13