similar to: [LLVMdev] link bytecode files into a native executable with debug info

On Thu, Jul 6, 2017 at 2:19 AM, Tim Northover <t.p.northover at gmail.com> wrote: > On 5 July 2017 at 17:51, Luís Marques via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Cool. When I did that on macOS, LDC generated a lot of complaints, > possibly > > because it is assuming mach-o files. I tried changing from > -mtriple=msp430 > > to

*llvm-project version:dd8a2013dc1804be1b7d9cffacad2e984300bd22* *Instructons to build LLVM+clang:* ``` cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/home/llvm/workspace/llvm/llvm-project/llvm_install -DCMAKE_BUILD_TYPE="Release" -DDEFAULT_SYSROOT="/home/llvm/workspace/riscv/riscv-tc-20200220/bin/riscv32-unknown-elf"

Hi, If we specify an explicit alignment attribute for globals (either at the Clang or LLVM IR level) we get asm alignment directives with values that seem to be `max(natural_alignment, specified_alignment)`. This seems to happen for multiple archs. GCC instead just emits the asked-for alignment. Is there a good reason for this LLVM behavior? Example: https://godbolt.org/z/B5ZcN_ (Clang)

On Thu, Jul 6, 2017 at 1:35 AM, Nicholas Wilson < iamthewilsonator at hotmail.com> wrote: > Luís, try using the -no-integrated-as flag to execute the assembler for > you. > We should probably make that the default for MSP430. > Cool. When I did that on macOS, LDC generated a lot of complaints, possibly because it is assuming mach-o files. I tried changing from -mtriple=msp430

Hello, While trying to find out why the LDC compiler refuses to generate object code for MSP430 targets (but generates MSP430 assembly or LLVM IR/bitcode), I came across the following apparent inconsistency. This works: $ clang --target=msp430 -c test.c This doesn't work: $ clang --target=msp430 -S -emit-llvm test.c $ llc -filetype=obj test.ll /opt/msp430/bin/llc: target does not support

Colleagues: I have encountered the following situation: SERIES OF COMMANDS source("File1") MORE COMMANDS source("File2") Optimally, I would like File1 and File2 to be merged into a single file (FileMerged). However, if I wrote the following: SERIES OF COMMANDS source("FileMerged") MORE COMMANDS I encounter an error: the File2 portion of FileMerged

Hi, I am trying to use rsync for incremental backup and I am facing some issues. I would like to ask your help to understand what is going on and have the proper command line. 1) my goal is I the following folders: ./dest: file3.txt ./orig: file1.txt   file10.txt  file2.txt   file20.txt And I would like to have as incremental backup ./dest: backup      file1.txt     file2.txt  file3.txt

I have the following situation: file2 on remote host and file1 on localhost. file1 and file2 are mostly the same. Simply running rsync remotehost:file2 file2 will actually transfer the entire file. But I would like to use the factt that I have local file1 that is mostly similar to file2. I.e. how can I make rsync to use file1 as a reference while transferring file2? (cp file1 file2 locally and

Hi everyone, I have a question for R code to merge. Say I have two dataframes: File1 is: V1 V2 V3 V4 1 100 101 name1 2 200 201 name2 2 300 301 name3 3 400 401 name4 3 500 501 name5 4 600 601 name6 4 700 701 name7 File2 is: V1 V2 V3 V4 1 50 55 p1 3 402 449 p2 4 550 650 p3 4 651 660

Hi, all: My folders are organized in such a way: root ----branch1 ---------------A -----------------------file1.txt -----------------------file2.txt ---------------B -----------------------file1.txt -----------------------file2.txt ----branch2 ---------------A -----------------------file1.txt -----------------------file2.txt ---------------B -----------------------file1.txt

Hi, I want to use rsync to make daily backups using hard-links in this way: rsync -av --delete --link-dest=../backup_old ./source/. ./backup_new This works great, but the problem is, that rsync does not show correctly what action it performs (-v option). It shows correctly all new and changed files/folders, but it does not show files that were deleted. This works only if I do not use the

> From: Indunil Jayasooriya <indunil75 at gmail.com> > > > > > > [root at centos67 loop]# cat file1 > > > firstname1 > > > firstname2 > > > > > > [root at centos67 loop]# cat file2 > > > lastname1 > > > lastname2 > > > > > > I need a OUTPUT like this > > > > > > > > >

Hi everybody. I've just started learning about LLVM and didn't get too far studying the core. I couldn't find the solution to my problem (if it has one) in the mailing list or the source code. The problem is: how can I redefine a function that's been called already by some other function? Suppose I have 3 files, all compiled to bytecode through llvm-gcc (I think it could be clang

hello, I am trying to build LLVM with default options. I am getting the following error message after make. [100%] Building C object tools/llvm-c-test/CMakeFiles/llvm-c-test.dir/metadata.c.o [100%] Building C object tools/llvm-c-test/CMakeFiles/llvm-c-test.dir/module.c.o [100%] Building C object tools/llvm-c-test/CMakeFiles/llvm-c-test.dir/object.c.o [100%] Building C object

I have a question about the llvm debugging records, especially wrt compile units. In the non-LLVM sense, a compile unit is essentially everything contained within a single .o file, and it is derived from one or more source and header files. Included in a compile unit are functions and global data. Dwarf records refer to compile units in the same way: a compile unit record has children which

This testscript creates reflinks to files on different subvolumes, overwrites the original files and reflinks, and moves reflinked files between subvolumes. Originally submitted as testcase 302, changes are made based on comments from Eric: http://oss.sgi.com/archives/xfs/2013-03/msg00231.html Two new common/rc functions used in this script (_require_cp_reflink and _verify_reflink) have been

Hi, > Suppose I have the following source: > > file1: > #include "file2" > #include "file3" > int fn1(void) ... > > file2: > int a; > > file3: > int fn2(void) ... > > then fn1, along with all the base types etc appear to be in compile unit > "file1", the variable a appears to be in compile unit

Lets say I have two source files file1.c and file2.c The latter just contains sub-routines to be used by the first. i.e. in file1.c I have the line #include "file2.c" Let's say "R CMD SHLIB file1.c" runs perfectly and I want to include the code in a package, "R CMD build" also runs fine but R CMD check" gives * checking whether package

Just want to emphasize this particular bug, since it is serious enough, even if apparently this mode isn't used often. Having a samba server S, a windows client W and a linux client L, and two files on S, file1 and file2. 1. On W, mount the share and lock file1 (eg. if it is executable, start it). 2. On L, mount the share and try to remove (rm) file1. This will hang because the file

Hello I think there is a conflict between setwd() and \SweaveOpts{prefix.string=}. In the same document, those both command get Sweave confuse the files and directories. See: say my .Rnw document is in File1 If one inserts some setwd() for another file: -setwd(File2) then the command \SweaveOpts{prefix.string=graphics/Rplots} will search the "graphics" folder in File2 because of