Displaying 20 results from an estimated 2000 matches similar to: "LLVM v3.9.0 and math built-ins"
2016 Sep 20
4
LLVM v3.9.0 and math built-ins
Hi Mehdi,
The ISO C specification does permit the math functions to modify ‘errno’, but I thought that the ‘-fno-math-errno’ option was to tell the optimiser to assume that ‘errno’ is not modified by the math functions. Explicitly providing ‘-fno-math-errno’ is not restoring the elision optimisation that was performed by LLVM v3.8, and this is really only a driver option, with ‘-fmath-errno’
2016 Nov 25
2
Translation of custom attribute (defined for variables) from clang to llvm
Hi All,
I need your guidance about a custom attribute. I have defined one for
variables. It is accepted in the source code (without any warnings from
clang), for example in following snippet.
#define NEWATTR __attribute__((moviAttr(1)))
int main()
{
NEWATTR volatile unsigned int a = 5;
volatile unsigned int *p;
p = &a;
return (a+*p);
}
and actually when I Dump the declaration, after
2016 Nov 25
3
Translation of custom attribute (defined for variables) from clang to llvm
Hi Asit,
thanks for the reply.
But I guess I was not clear in my question. Actually, i dont want to use
__ATTRIBUTE__((ANNOTATE("MOVIATTR"))), since in documentation it is
stated that "This intrinsic allows annotation of local variables with
arbitrary strings. This can be useful for special purpose optimizations
that want to look for these annotations. These have no other
2016 Nov 28
2
Translation of custom attribute (defined for variables) from clang to llvm
Hi John,
I have looked into the EmitAutoVarAlloca() in CGDecl.cpp. However, I
could not figure out how to employ my custom attribute for code
generation. For example, my custom attribute is visible in CGDecl.cpp
but how can I generate based on my custom attribute
if (D.hasAttr<myCustomAttri>())
{
//What to do here?
}
What I wan in IR is something like below.
Without Custom Attribute:
2020 Jan 28
3
Floating point semantic modes
About ftrapping-math:
I think we should eliminate ftrapping-math, a boolean option, because it overlaps with ffp-exception-behavior, a 3 valued option. Or we can keep it in the clang driver for compatibility, but it should be rewritten by clang driver into ffp-exception-behavior=ignore and ffp-exception-behavior=strict. There are various fields in llvm and/or clang that maintain Boolean
2016 Dec 09
4
Strange clang behavior when compiled against musl
I have managed to compile llvm and clang against musl, but it behaves really strange:
At first I tried to launch the compiler with musl dynamic loader:
$ LD_LIBRARY_PATH=/path/to/musl/lib /path/to/musl/lib/ld-musl-x86_64.so.1 /path/to/llvm/bin/clang -v
clang version 4.0.0 (https://github.com/llvm-mirror/clang 40adebeca0f99006d407508653c2cbd270a1a51c) (https://github.com/llvm-mirror/llvm
2014 Jun 03
2
[LLVMdev] How much memory clang llvm needs for debug compiling?
On Tue, Jun 3, 2014 at 7:59 AM, Nancy <nancydreaming at gmail.com> wrote:
>> First, you could switch to ld.gold instead of ld.bfd. It uses much
> $ln -s `which gold` /usr/local/bin/ld
>
>> the idea. I think for autoconf you need ".../configure
>> --enable-split-dwarf" to use this.
>>
> $.../configure --enable-targets=x86 --enable-split-dwarf
>
2009 Sep 02
0
[LLVMdev] 2.6 pre-release1 ready for testing
Hi Tanya,
The sources weren't updated for this pre-release testing. So I had the
same problems on PPC.
-bw
On Sun, Aug 30, 2009 at 10:50 PM, Tanya Lattner<lattner at apple.com> wrote:
> LLVMers,
> 2.6 pre-release1 is ready to be tested by the community.
> http://llvm.org/prereleases/2.6/
> You will notice that we have quite a few pre-compiled binaries (of both
> clang
2019 Jun 28
2
Conflicts with custom passes
You are right. Thanks!
I fixed that one as well as some other issues.
I built LLVM-8 with Debug + no-rtti. But it now has the following error:
Stack dump:
0. Program arguments: clang-8 -cc1 -triple x86_64-unknown-linux-gnu -emit-llvm -disable-free -main-file-name time-1.7.c -mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
2013 Oct 12
1
[LLVMdev] Fwd: unsupported gc: vmkit
when I execute clang on llvm bitcode files, I get the following error:
clang: error: unable to execute command: Aborted
unsupported GC: vmkit
UNREACHABLE executed at GCMetadata.cpp:87!
0 clang 0x09e9d5d9 llvm::sys::PrintStackTrace(_IO_FILE*) + 41
Stack dump:
0. Program arguments: /home/ali/llvm-3.3.src/Release+Asserts/bin/clang
-cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all
2018 Aug 21
4
different output with fast-math flag
This is of course not homework. I am trying to understand how fast math
optimizations work in llvm. When I compared IR for both the programs, the
only thing I have noticed is that fdiv and fmul are replaced with fdiv fast
and fmul fast. Not sure what happens in fdiv fast and fmul fast.
I feel that its because d/max is really small number and fast-math does not
care about small numbers and consider
2012 Jul 18
2
[LLVMdev] Setting up a cross-compiler for cortex-m3
On 18 July 2012 15:24, salvatore benedetto
<salvatore.benedetto at gmail.com> wrote:
> I'm not sure how to interpret the above output, but I don't understand
> why if say -triple armv4t-none--gnueabi .
Ok, we're getting there... ;)
I think these errors are due to Clang not finding the
libraries/includes/etc for the target you're building.
If you have
2012 Jun 19
0
[LLVMdev] Is cross-compiling for ARM on x86 with llvm/Clang possible?
Hello
> ./clang -v -emit-llvm -ccc-host-triple arm-none-linux-gnueabi
> -I/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/include
> -L/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin hello.c
You forgot about sysroot here.
> /home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin/ld:
> unrecognised emulation mode: armelf_linux_eabi
>
2019 Nov 04
4
Debugging clang with debugger breakpoints ?
Hi David,
Thank you for your patience but I still don’t get it: I don’t see how that is a “command”, as it’s just a list of strings that state command options.
I know how to use the debugger, this is what I attempt to debug:
clang --target=msp430 -emit-llvm -c -S -Oz main.c
The debugger works fine, but only on the main thread. However breakpoints do not work with the code that was invoked
2009 Sep 22
0
[LLVMdev] LLVM Build Difficulties
Hi Curtis,
> I hope this is the right list for such questions.... I've been trying to
> get LLVM compiled under Linux (Ubuntu 9.04, 64 bit) for the last couple
> of days.
I can't reproduce this with ubuntu 9.10, 64 bit x86, gcc 4.4.1, using
your configure options. What version of gcc are you using?
> CXXFLAGS="-fPIC" ./configure --enable-optimized
2010 Apr 27
3
[LLVMdev] "clang -v" shows a GCC call
Hi everyone,
I'm very new to the world of compilation and I've got to spend some time
time on LLVM.
As I have to produce a cross compiler for a completely new target and I
don't want to cross-build the binutils, I choose Clang as a replacement
frontend for llvm instead of llvm-gcc.
But first, I just would like to compile something on my Linux platform in
order to test the software,
2019 Nov 04
2
Debugging clang with debugger breakpoints ?
Hi David,
Thank you for your help. Please, can you elaborate on this?. The command line that I get with -### starts with this:
clang version 9.0.1 (https://github.com/llvm/llvm-project.git 6e38ee067b8fa08792f551fb565bbb8ada4864b1)
Target: msp430
Thread model: posix
InstalledDir: /Users/joan/LLVM-9/llvm-project/build/Debug/bin
"/Users/joan/LLVM-9/llvm-project/build/Debug/bin/clang"
2016 Mar 05
2
instrumenting device code with gpucc
On Fri, Mar 4, 2016 at 5:50 PM, Yuanfeng Peng <yuanfeng.jack.peng at gmail.com>
wrote:
> Hi Jingyue,
>
> My name is Yuanfeng Peng, I'm a PhD student at UPenn. I'm sorry to bother
> you, but I'm having trouble with gpucc in my project, and I would be really
> grateful for your help!
>
> Currently we're trying to instrument CUDA code using LLVM 3.9, and
2012 Aug 02
1
[LLVMdev] Questions about clang options
Dear Zhang,
Compiler ends up invoking cc1 (the backend) anyways. So if you would
like to invoke it by hand, the only thing to know is the right
combination of options. Try to use the compiler verbose option "-v".
It will show you how exactly clang invokes the backend:
> clang -v -c showdebug.c
clang version 3.2 (trunk 156703)
Target: x86_64-unknown-linux-gnu
Thread model: posix
2012 Aug 02
0
[LLVMdev] Questions about clang options
On Thu, Aug 2, 2012 at 8:56 AM, Xinglin Zhang <xinglinzh at gmail.com> wrote:
> Hi,
>
> I am quite new to LLVM. I just compiled LLVM and clang on Ubuntu11.10 then
> followed the tutorial http://llvm.org/docs/DebuggingJITedCode.html
>
> clang -cc1 -O0 -g -emit-llvm showdebug.c
>
>
> where showdebug.c contains:
>
> #include<stdio.h>
> int main()
>