search for: artagnon

It should be noted that a symlink to the built llvm-config will return the paths for the system llvm instead of the built llvm; it's fine on OS X though. Some differences in realpath?

..., May 22, 2015 at 4:14 PM, Keno Fischer <kfischer at college.harvard.edu> wrote: > This might be related to GOT relocations. I rewrote that part of > RuntimeDyldELFbecause I was seeing this issue. Have you tried trunk? > > On Fri, May 22, 2015 at 5:10 PM, Ramkumar Ramachandra <artagnon at gmail.com> > wrote: > >> So it appears that we get about half the crashes with the large code >> model. The rest are crashing in the same way. It could either mean that >> large code model still takes that crashing codepath and that the number of >> crashes only...

...hin a 2 GB offset of the first allocation in a > 64-bit process. For various reasons that I don't understand, reserving 2 GB > of address space upfront and allocating from that is not workable for some > MCJIT clients. > > On Tue, May 19, 2015 at 7:19 AM, Ramkumar Ramachandra <artagnon at gmail.com> > wrote: > >> Hi, >> >> We are seeing sporadic crashes since we migrated to MCJIT on Win64. The >> same tests pass without issues on Mac64 and Linux64. The issue is this >> assertion failure in RuntimeDyldELF.c: >> >> RealOffset &lt...

On Wed, Jul 10, 2013 at 12:29 PM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > The instructions btr and bts are perfectly valid, and have existed since > Intel 386. GNU as supports them fine. Unfortunately, LLVM does not > support them, and barfs with: > > error: ambiguous instructions require an explicit suffix > > Fix this...

Hi Dmitri, Dmitri Gribenko wrote: > On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra > <artagnon at gmail.com> wrote: >> Add several .gitignore rules to various directories to ensure a clean >> worktree after a default build. > > Hi, > > These gitignore lists require maintenance. Is is possible to express > the same set of filenames as patterns like '*.inc...

...Keno Fischer < > kfischer at college.harvard.edu> wrote: > >> This might be related to GOT relocations. I rewrote that part of >> RuntimeDyldELFbecause I was seeing this issue. Have you tried trunk? >> >> On Fri, May 22, 2015 at 5:10 PM, Ramkumar Ramachandra <artagnon at gmail.com >> > wrote: >> >>> So it appears that we get about half the crashes with the large code >>> model. The rest are crashing in the same way. It could either mean that >>> large code model still takes that crashing codepath and that the number of &...

Provide a full-fledged example of working variable arguments on X86_64, since it's easily the most popular platform. Cc: Reid Kleckner <rnk at google.com> Signed-off-by: Ramkumar Ramachandra <artagnon at gmail.com> --- docs/LangRef.rst | 44 ++++++++++++++++++++++++++++++-------------- 1 file changed, 30 insertions(+), 14 deletions(-) diff --git a/docs/LangRef.rst b/docs/LangRef.rst index ddef803..f429062 100644 --- a/docs/LangRef.rst +++ b/docs/LangRef.rst @@ -6695,7 +6695,8 @@ Overview:...

...So far, I've found one candiate: speculative execution in SimplifyCFG (test/Transforms/SimplifyCFG/SpeculativeExec.ll). However, it's somewhat involved to show that SimplifyCFG does kick in for gc.relocate. Is there a better way to directly test it? Signed-off-by: Ramkumar Ramachandra <artagnon at gmail.com> --- lib/IR/Value.cpp | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/lib/IR/Value.cpp b/lib/IR/Value.cpp index 5f7e258..aa701d5 100644 --- a/lib/IR/Value.cpp +++ b/lib/IR/Value.cpp @@ -23,8 +23,10 @@ #include "llvm/IR/GetElementPtrTypeIterator.h" #include...

On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Add several .gitignore rules to various directories to ensure a clean > worktree after a default build. Hi, These gitignore lists require maintenance. Is is possible to express the same set of filenames as patterns like '*.inc' in the root gitigrore file,...

On Nov 13, 2012, at 8:34 AM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Hi Dmitri, > > Dmitri Gribenko wrote: >> On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra >> <artagnon at gmail.com> wrote: >>> Add several .gitignore rules to various directories to ensure a clean >>> worktree after a de...

Hi, According to the GNU as documentation [1], .cfi_startproc simple is a valid directive. Unfortunately, LLVM complains with: error: invalid instruction mnemonic 'simple' I happened to notice it while attempting to compile linux.git with clang: see arch/x86/ia32/ia32entry.S:75. [1]: http://sourceware.org/binutils/docs-2.22/as/Pseudo-Ops.html#Pseudo-Ops Thanks.

Hi, I happened to notice that linux.git uses plenty of btr and bts instructions (not btrl, btrw, btsl, btsw). For examples, see arch/x86/include/asm/bitops.h. LLVM barfs on these due to ambiguity, while GNU as is fine with them. Surely, there must be architectures where the w/l variant is unavailable? LLVM must support those architectures, no? Thanks.

Hi, These warnings are included by default with -Wall in GCC 4.6 [1], and LLVM should support them instead of throwing -Wunknown-warning-option. [1]: http://gcc.gnu.org/gcc-4.6/porting_to.html Thanks.

On Wed, Jul 10, 2013 at 11:12 AM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Hi, > > I happened to notice that linux.git uses plenty of btr and bts > instructions (not btrl, btrw, btsl, btsw). For examples, see > arch/x86/include/asm/bitops.h. LLVM barfs on these due to ambiguity, > while GNU as is fine with them. Surely, there...

Hi, When I pulled the latest changes, I found that --enable-optimized was ON by default, contrary to old behavior and documentation. I have to do a ./configure --disable-optimized to get the usual Debug+Asserts build. Is this an intentional change? Ram

Also, please elaborate on why this is a good change. Because gas accepts it isn’t sufficient reason in and of itself. -Jim On Jul 10, 2013, at 1:18 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Wed, Jul 10, 2013 at 12:29 PM, Ramkumar Ramachandra > <artagnon at gmail.com> wrote: >> The instructions btr and bts are perfectly valid, and have existed since >> Intel 386. GNU as supports them fine. Unfortunately, LLVM does not >> support them, and barfs with: >> >> error: ambiguous instructions require an explicit suffix...

...vailable at: > http://lab.llvm.org:8011/builders/ppc64le-sanitizer/builds/0 > > Buildbot URL: http://lab.llvm.org:8011/ > > Buildslave for this Build: ppc64le-sanitizer > > Build Reason: scheduler > Build Source Stamp: [branch trunk] 225670 > Blamelist: ab,abataev,alexfh,artagnon,benlangmuir,chandlerc,chapuni,compnerd,dexonsmith,djasper,dsanders,ehsan,eugenis,foad,gribozavr,hfinkel,jhibbits,jkolek,joerg,majnemer,matze,nathan,rafael,rdivacky,rksimon,rsmith,rtrieu,sanjoy,seurer,spatel,timurrrr,tomatabacu,tstellar > > BUILD FAILED: failed annotate > > sincerely, &g...

On Wed, Jul 10, 2013 at 2:08 PM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Jim Grosbach wrote: >> To say that another way, is the assembler correctly diagnosing a previously >> unnoticed problem in the project source code, or is the assembler not >> behaving correctly according the the documented Intel assembly mnemonics? &gt...

Add several .gitignore rules to various directories to ensure a clean worktree after a default build. Signed-off-by: Ramkumar Ramachandra <artagnon at gmail.com> --- Just cloned and built LLVM. This annoyed me. Here's a trivial patch. .gitignore | 10 ++++++++++ bindings/ocaml/llvm/.gitignore | 1 + docs/.gitignore | 1 + include/llvm/.gitignore...

Jim Grosbach wrote: > To say that another way, is the assembler correctly diagnosing a previously > unnoticed problem in the project source code, or is the assembler not > behaving correctly according the the documented Intel assembly mnemonics? Where are the authoritative instruction set pages? If such a thing were readily available, why are there gaps in the current implementation? A