similar to: [LLVMdev] Error in LLVM 2.0 Cygwin build

Hi Nikolaos, Following commands work great for me. $ clang -S -emit-llvm -target nvptx -x cl -include clc/clctypes.h ../data-types/scalar.cl $ llc -mcpu=sm_30 scalar.s You can follow Justin's blog [1]. It helped me a lot to understand where to start. [1] http://jholewinski.org/blog/llvm-3-0-ptx-backend/ Best, Ankur On Mon, Feb 4, 2013 at 11:40 PM, Justin Holewinski < justin.holewinski

Hi Duncan >>> br i1 %38, label %17, label %39 >>> ; <label>:39 ; preds = %._crit_edge >>> ret void >>> >>> However, ";" is a comment-line character. How is this interpreted, as a >>> meta-comment? (a semantically important comment)? >> >> it's just a comment and has no

Alright, couple of points here: 1. Address space 0 is invalid for global variables. This is causing a crash in llc where we use llvm_unreachable() on this case. This is most likely why you're seeing llc run forever. The fix for this is to use address space 1 for globals, which puts them into PTX global memory. On our side, we should provide a meaningful error message in this case. 2. The

> > > > I believe Aaron Gray has had success building llvm on Cygwin: > > http://www.aarongray.org/LLVM/BuildingLLVMonCygwin.html > > > > However, those instructions may be a bit out of date... > > Tanya: OK. And how about the clang frontend. Is it usable without having dependencies with the rest of the infrastructure? Which are your typical Linux platforms

Hi, > Can you post the llc command line you're using? Can you post an LLVM IR > file that causes this behavior? yes: ${LLVM_PATH}/bin/llc -o helloworld.s -march=nvptx helloworld.ll where LLVM_PATH my local installation path for LLVM. Also attaching helloworld.c: #include <stdio.h> int main(void) { printf("Hello World!\n"); return 0; } and helloworld.ll:

On Mon, Feb 4, 2013 at 1:09 PM, <nkavv at physics.auth.gr> wrote: > Hi Justin, > > > Has anyone had similar problems with the NVPTX backend? Shouldn't this >>> code be linked to the AsmPrinter library for NVPTX (already)? >>> >> >> What do you mean by "doesn't work"? The AsmPrinter library really houses >> the MCInst

On Sep 25, 2007, at 6:54 PM, nkavv at physics.auth.gr wrote: >>> >>> I believe Aaron Gray has had success building llvm on Cygwin: >>> http://www.aarongray.org/LLVM/BuildingLLVMonCygwin.html >>> >>> However, those instructions may be a bit out of date... >>> > > Tanya: > OK. And how about the clang frontend. Is it usable without

Hi Duncan >> br i1 %38, label %17, label %39 >> ; <label>:39 ; preds = %._crit_edge >> ret void >> >> However, ";" is a comment-line character. How is this interpreted, as a >> meta-comment? (a semantically important comment)? > > it's just a comment and has no semantic comment. You can delete

Hi Justin, >> Has anyone had similar problems with the NVPTX backend? Shouldn't this >> code be linked to the AsmPrinter library for NVPTX (already)? > > What do you mean by "doesn't work"? The AsmPrinter library really houses > the MCInst printer, which isn't implemented for NVPTX yet. The older > assembly printer works just fine. This is

Hi Nikolaos, On 20/01/13 12:00, nkavv at physics.auth.gr wrote: > Hi all, > > i'm writing a TXL (http://www.txl.ca) grammar and a revamp of bison/flex grammar > for LLVM. > > I've noticed an inconsistency regarding label naming conventions. > > For instance, the following is a segment of legit LLVM assembly (human-readable) > IR: > > br i1 %38, label

Hi there i would like to ask a few questions to the developers responsible for the register allocator(s) design in LLVM (Fernando and other people). First of all, congrats on providing more than one option for register allocation. Now to the questions: 1. I can see the standard algorithms (bigblock, linearscan -- good choice for the JIT and for general use as well, and the other algorithms).

Hi all, i'm writing a TXL (http://www.txl.ca) grammar and a revamp of bison/flex grammar for LLVM. I've noticed an inconsistency regarding label naming conventions. For instance, the following is a segment of legit LLVM assembly (human-readable) IR: br i1 %38, label %17, label %39 ; <label>:39 ; preds = %._crit_edge ret void

On Thu, Jan 24, 2013 at 7:20 AM, Ahmed Bougacha <ahmed.bougacha at gmail.com>wrote: > On Thu, Jan 24, 2013 at 12:46 PM, <nkavv at physics.auth.gr> wrote: > > Hi all, > > > > i'm just starting out with LLVM (although i've been observing its > evolution > > since that first release some years ago :) > > > > I would like to develop a

On Thu, Jan 24, 2013 at 12:46 PM, <nkavv at physics.auth.gr> wrote: > Hi all, > > i'm just starting out with LLVM (although i've been observing its evolution > since that first release some years ago :) > > I would like to develop a backend for a generic assembly-like language, > called NAC (N-Address Code). More info on NAC can be found here: >

On Oct 6, 2007, at 6:11 PM, nkavv at physics.auth.gr wrote: >>> You mean a temporary defined in an instruction. OK, that is what i >>> basically >>> need here. Is it guaranteed to "live" in the physical register for >>> the entire >>> program (or at least for a single function, which would trivially >>> work for >>>

> > You are thinking about the gcc extension which allows the programer > to tie a register to global variable? This feature isn't implemented > nor am I aware of anyone driving to get it to implemented. Looks like > you will have to roll up your sleeves if that's what you want. :-) > > Evan Hi Evan is this the -fixed-reg<num> feature, or something that has

Hi all is it possible to avoid the emission of metadata information by opt and/or clang? For instance, I would like to go without "tbaa" metadata in LLVM assembly code as printed by "-emit-llvm". I'm using the 3.1 binary release for MinGW (and for Linux on a different machine). Best regards Nikolaos Kavvadias

You can turn off TBAA metadata by passing -fno-strict-aliasing to clang. You can turn off emitting debug metadata by not passing -g. There is no flag for turning off metadata in general (for example, range metadata will still be produced for certain casts, and if you compile Objective-C for the GNU runtimes then you will still have some metadata attached to message sends. If you want to remove

Hi Justin I just came across your presentation regarding the LLVM 3.0 (?) PTX backend: http://llvm.org/devmtg/2011-11/Holewinski_PTXBackend.pdf Is this the NVPTX backend or the predecessor (in PTX? directory) backend? Best regards Nikolaos Kavvadias

>> You mean a temporary defined in an instruction. OK, that is what i >> basically >> need here. Is it guaranteed to "live" in the physical register for >> the entire >> program (or at least for a single function, which would trivially >> work for >> single-function programs)? >No it's just guaranteed to be defined in a fixed register.