similar to: Is it possible to generate the IR representation with the original macro information?

> It's the linkers job to hook together functions and definitions that end up in the same binary. Your OS will then hook in functions from other binaries when your executable is loaded into memory. How does it know whether it is a system function or a user-defined function? It seems that user functions have higher priorities over system functions as demonstrated by the following example.

Hi, I see things like this. What does it mean? Is it documented somewhere? Thanks. ; preds = %for.body https://llvm.org/docs/LangRef.html ; <label>:91: ; preds = %88 %92 = load i8**, i8*** @glob_complete_word.matches, align 8, !dbg !99798 %93 = load i32, i32* @glob_complete_word.ind, align 4, !dbg !99799 %94 = sext i32 %93 to i64, !dbg !99798

Hi In the generated .ll file, it may have something like this. How does LLVM know where to look for the definition of printf? Is it documented somewhere? Thanks. declare i32 @printf(i8*, ...) #1 -- Regards, Peng

Hi SSH, I have put the ssh command in `script.sh`, with the code: ~~~ #!/usr/bin/env bash ssh -q server date ~~~ And I have one `main.sh` to call `script.sh` as below. ~~~ #!/usr/bin/env bash # vim: set noexpandtab tabstop=2: while read -r run do ./script.sh done < <(seq 10) ~~~ The `script.sh` can be called only once, say ~~~ $ ./main.sh Tue Oct 18 12:26:05 CDT 2016 ~~~ But 10 runs

On Mon, Jan 28, 2019 at 8:16 AM Tim Northover <t.p.northover at gmail.com> wrote: > > On Mon, 28 Jan 2019 at 14:10, Peng Yu via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > ld: unknown option: -plugin-opt=save-temps > > The macOS linker supports -save-temps directly (but not -plugin-opt). > I haven't tried, but I'd guess that if you modified the

Hi I use the LDFLAGS=" -flto -fuse-ld=gold -Wl,-plugin-opt=save-temps " to generate the makefile and to make the whole program. However, found four different kinds of bitcode for each target. For example, I am compiling coreutils. For the program "nohup", I can get nohup.0.0.preopt.bc nohup.0.2.internalize.bc nohup.0.4.opt.bc nohup.0.5.precodegen.bc If I am right, I

> https://llvm.org/docs/LangRef.html#structure-types I don't follow the above link. Could you help explain what it means? > Fundamentally, llvm is not designed to preserve details about front end language features. If directly compile .c to .ll can preserve the original struct information even they are essentially the same, why flto can not? It seems to me that there must be a way to

Hi Teresa Thanks for your very quick and clear explanation. I have one more question. The emit-llvm option will give you the IR for a single source file when you compile it with -c. All of those files when combined give the IR in the preopt.bc temp file. =========== So if I use "clang -emit-llvm -c" to generate the .ll file. It should be the same as the one I generated by using

These are the bitcode at different stages of the LTO portion of the compile. LTO merges the IR for all files being linked and optimizes them as a single monolithic module. The preopt.bc is the merged IR just after merging and before performing any LTO optimizations. internalize.bc is after performing whole program internalization. opt.bc is after the optimization pipeline, and .precodegen.bc is

> On macOS you just omit the '-fuse-ld=gold' and it will work out of the box. > > ./configure CC=clang RANLIB=llvm-ranlib CFLAGS=-flto > > LDFLAGS=-Wl\,-plugin-opt=save-temps\ -flto\ -fuse-ld=gold > > make No. It doesn't work on Mac OS by just omitting '-fuse-ld=gold'. $ ../../../extract/bash-5.0/configure CC=clang CXX=clang++ RANLIB=llvm-ranlib

The versioning information is confusing for end-users. The numbers are stuck at 1.5.0 when the tools have moved to 1.8.3. I suggest removing the versioning system in the kernel altogether and let the kernel version be the guide to debug issues. However, if you think versioning is still required, please state the reason and modify the version string in the ver.* files to reflect the uptodate

On Tue, Dec 18, 2012 at 1:09 PM, Craig Topper <craig.topper at gmail.com> wrote: > But its pretty easy to change the tabstop within the editor to make it > readable. > True, in this case... The output is not trying to be intelligent in the general case, just spitting out tabs. I agree that to replace this, however, it would be best to look at some smart column-padded formatting

To compile an auto-tooled project to bitcode, I used to use plugin-opt=save-temps switch as explained in: http://gbalats.github.io/2015/12/10/compiling-autotooled-projects-to-LLVM-bitcode.html. This switch works with LLVM 3.8.0. However, it seems to have no effect with LLVM 5.0.0. I can see intermediate bitcode files on disk, but not the final one. Is the option removed altogether? Has the switch

Hi, I'm curious about Tab stops in graphics: plot(1) text(1.2, 1.2, "Char\nMoreChar") works fine, but text(1.2, 0.8, "Char\tMoreChar") doesn't. Exporting with pdf tells me that the sign width is unknown. I'm not into informatics, so I don't know how a tabstop actually works. Is this at all possible in graphical commands as it is in write.table and the like?

Hi, With LTO, it seems that compilers should have the information to decide whether to inline a function or not. In this case, is it unnecessary to specify functions as inline in C/C++ code? -- Regards, Peng

Hi everyone, I'll be very thankful if anyone can help me. I want to extract the dependences details by using polly. I followed the following steps on example code matmul.c: 1. clang -S -emit-llvm matmul.c -o matmul.s 2. opt -S -polly-canonicalize matmul.s > matmul.preopt.ll 3. opt -basicaa -polly-dependences -analyze matmul.preopt.ll But it doesn't show me the dependences. I

Perfect, thank you very much :) 2011/10/26 Tobias Grosser <tobias at grosser.es>: > On 10/24/2011 11:32 PM, Marcello Maggioni wrote: >> >> Strange , with --enable-shared (I use auto tool by the way ...) it gives: >> >> MacBook-Pro-di-Marcello:examples Kariddi$ ./compile_ex.sh >> not_so_simple_loop >> clang (LLVM option parsing): Unknown command line

On 08/16/2013 02:42 AM, Star Tan wrote: > At 2013-08-16 12:44:02,"Tobias Grosser" <tobias at grosser.es> wrote: >> Hi, >> >> I tried to reproduce your findings, but could not do so. > > > Sorry, I did not put all code in my previous email because the code seems a little too long and complicated. > You can refer to the detailed C code and LLVM IR

But its pretty easy to change the tabstop within the editor to make it readable. On Tue, Dec 18, 2012 at 1:01 PM, Eli Bendersky <eliben at google.com> wrote: > On Tue, Dec 18, 2012 at 11:36 AM, Caldarale, Charles R > <Chuck.Caldarale at unisys.com> wrote: > >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > >> On Behalf Of Eli

On Tue, Dec 18, 2012 at 1:13 PM, Eli Bendersky <eliben at google.com> wrote: > On Tue, Dec 18, 2012 at 1:09 PM, Craig Topper <craig.topper at gmail.com> > wrote: > > But its pretty easy to change the tabstop within the editor to make it > > readable. > > > > True, in this case... The output is not trying to be intelligent in > the general case, just