Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] Dev Meeting: Please add me as unconfirmed."
2006 Mar 21
0
[LLVMdev] problem loading analysis results from Inliner pass
A
On 3/21/06, Michael McCracken <michael.mccracken at gmail.com> wrote:
> On 3/21/06, Chris Lattner <sabre at nondot.org> wrote:
> > On Mon, 20 Mar 2006, Michael McCracken wrote:
> >
> > > Hi, I'm trying to access an analysis pass from the Inliner pass, and
> > > I'm having a lot of trouble getting that to work - I can verify that
> >
2006 Apr 03
0
[LLVMdev] lli: problem finding external symbol
On Mon, 3 Apr 2006, Michael McCracken wrote:
> the bytecode with lli - I get the following error:
>
> $ lli -load=/home/mmccrack/linux/lib/libTau.sh leo-inline-300-tau.bc
> ERROR: Program used external function
> '__llvm_cxxeh_allocate_exception' which could not be resolved!
This is most likely because you are trying to link with llvmgcc, not with
llvm-g++. Make sure that
2007 Aug 21
0
[LLVMdev] Problems building llvm-gcc-4.2 on ppc32, OS X 10.4.10
Hi, I'm guessing that no one has tried this exact combination yet.
I'm trying to build the gcc4.2 front end with current LLVM SVN
on a G4 Powerbook running 10.4.10.
I started with this:
../gcc4.2-trunk/configure
--prefix=$HOME/Documents/hpcl/LLVM/llvm-gcc-4-2/install
--enable-llvm=$HOME/Documents/hpcl/LLVM/llvm-svn-obj/
--with-gmp=$HOME/Documents/hpcl/LLVM/llvm-gcc-4-2/libdeps
2006 Apr 03
2
[LLVMdev] lli: problem finding external symbol
Hi, I have a large-ish application I'm trying to build with LLVM, so I
replaced g++ in the Makefiles with llvm-g++. This appears to work fine
when I pass -Wl,-native to generate an ELF executable, but I want to
control the inlining threshold it uses, so I am now passing
-Wl,-disable-inlining and -Wa,-disable-inlining, and having it
generate LLVM bytecode, then running opt -inlining to generate
2006 Sep 11
0
[LLVMdev] gfortran calling convention
Another option might be g95 instead of gfortran. I haven't used it for
a while, but I seem to recall it working fine in gcc 4.0.1.
On 9/11/06, Michael McCracken <michael.mccracken at gmail.com> wrote:
> On 9/9/06, Michael McCracken <michael.mccracken at gmail.com> wrote:
> > On 9/9/06, Steven Bosscher <stevenb.gcc at gmail.com> wrote:
> > > On 9/9/06, Chris
2007 May 15
2
[LLVMdev] FORTRAN compiler status?
I just noticed this - I can't promise any particular amount of TLC, but
I'll certainly be giving the Fortran front-end some attention as soon as
LLVM moves to gcc 4.2.
For future reference, does anyone know of a good free Fortran compiler
test suite?
Cheers,
-mike
On 5/14/07, Duncan Sands <baldrick at free.fr> wrote:
> Hi Duraid,
>
> > Does anyone know what the
2006 Sep 01
0
[LLVMdev] gfortran: patch, question
On 9/1/06, Michael McCracken <michael.mccracken at gmail.com> wrote:
> On 9/1/06, Chris Lattner <sabre at nondot.org> wrote:
> > On Fri, 1 Sep 2006, Michael McCracken wrote:
[snip]
> Now f951 doesn't crash when compiling, but still can't compile the
> libgfortran files. It now finds some syntax errors in a generated file
> that's part of the intrinsics
2006 Sep 11
2
[LLVMdev] gfortran calling convention
On 9/9/06, Michael McCracken <michael.mccracken at gmail.com> wrote:
> On 9/9/06, Steven Bosscher <stevenb.gcc at gmail.com> wrote:
> > On 9/9/06, Chris Lattner <sabre at nondot.org> wrote:
> > > On Sat, 9 Sep 2006, Steven Bosscher wrote:
> > > > You wrote:
> > > >> The NIST F77 test suite doesn't seem to be compatible with
2007 Apr 12
0
[LLVMdev] Compiler name: Nāga
On Apr 12, 2007, at 12:57 PM, Michael McCracken wrote:
> Hi, the idea of a dragon theme reminded me of the dragon-like serpents
> called "Nāga" from Cambodian mythology, among other places.
Interesting, my only comment is if we pick this we need to just spell
it Naga.
Naga are also snake people in D&D (yea... I know).
>
> Here's a brief link explaining the
2006 Sep 11
0
[LLVMdev] gfortran calling convention
On 9/11/06, Chris Lattner <sabre at nondot.org> wrote:
> On Mon, 11 Sep 2006, Michael McCracken wrote:
> >> be though.
> >
> > I'm thinking that effort on 4.0.1 gfortran is not worthwhile, since
> > 4.0.1 fails to compile some pretty basic examples, and there are some
> > pretty extensive changes between then and 4.2.
>
> ok
>
> >>
2006 Aug 31
3
[LLVMdev] gfortran
Hi, in a thread this afternoon about compiling the Fortran SPEC2000 to
LLVM bytecode, Chris mentioned that it should be possible to compile
to LLVM with the gfortran front end, although no one has necessarily
tried it.
I was surprised (and happy) to hear this, as under the impression that
it would require a "complete rewrite of the gfortran backend" [1].
Now, I probably misinterpreted
2006 Sep 10
0
[LLVMdev] gfortran calling convention
On 9/9/06, Steven Bosscher <stevenb.gcc at gmail.com> wrote:
> On 9/9/06, Chris Lattner <sabre at nondot.org> wrote:
> > On Sat, 9 Sep 2006, Steven Bosscher wrote:
> > > You wrote:
> > >> The NIST F77 test suite doesn't seem to be compatible with gfortran at
> > >> all,
> > > Actually, the entire suite compiles flawlessly with
2006 Sep 01
3
[LLVMdev] gfortran: patch, question
On 9/1/06, Chris Lattner <sabre at nondot.org> wrote:
> On Fri, 1 Sep 2006, Michael McCracken wrote:
> > I wanted to know if I should submit patches with comments around them
> > like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to
> > the tree. I'd like to make it as easy as possible to apply these, so
> > let me know any rules I
2007 Apr 12
7
[LLVMdev] Compiler name: Nāga
Hi, the idea of a dragon theme reminded me of the dragon-like serpents
called "Nāga" from Cambodian mythology, among other places.
Here's a brief link explaining the specific Cambodian meaning -
http://en.wikipedia.org/wiki/Naga_(mythology)#N.C4.81gas_in_Cambodia
I like this as a name, because it's unique short and easy to type and
remember (as long as you omit the accent,
2006 Sep 11
0
[LLVMdev] gfortran calling convention
On 9/11/06, Chris Lattner <sabre at nondot.org> wrote:
> On Sat, 9 Sep 2006, Michael McCracken wrote:
> >> No, gfortran in gcc 4.0 is, ehm, highly experimental (read: a piece of
> >> junk). Gfortran in gcc 4.1 was the first one that worked for NIST (and
> >> for SPEC).
> >
> > Hm. I had noticed a bunch of changes in the current sources, but had
>
2006 Sep 06
2
[LLVMdev] gfortran: array constructor problems
On 9/6/06, Chris Lattner <sabre at nondot.org> wrote:
> On Tue, 5 Sep 2006, Michael McCracken wrote:
[snip]
> > ../../src/gcc/llvm-convert.cpp:3871: failed assertion
> > `(TREE_CONSTANT(exp) || TREE_CODE(exp) == STRING_CST) && "Isn't a
> > constant!"'
> >
> > In this case, TreeConstantToLLVM::Convert() is getting a constant to
>
2006 Feb 11
2
[LLVMdev] Another project using LLVM: LENS, a program investigation framework.
Hi, I'm using LLVM as part of my thesis project and wanted to let the
community know about it. (And get your feedback :)
The project is called LENS. It's a file format and a framework for storing
generic information about a program based on the control structure of the
program, and quickly building tools to interact with that data. It might be
best to think of the format as an external
2006 Mar 21
2
[LLVMdev] problem loading analysis results from Inliner pass
Hi, I'm trying to access an analysis pass from the Inliner pass, and
I'm having a lot of trouble getting that to work - I can verify that
my pass is loaded and run (it is a dynamically loaded pass that is
part of an analysisgroup), however, when I access it using
getAnalysis<> from within Inliner::runOnSCC, I am instead getting the
default, dummy version of my analysis, which should
2006 Sep 01
2
[LLVMdev] gfortran: patch, question
Hi, I have a first quick patch and a question. The patch links f951
with g++ when LLVM is enabled. It's at the end of this email.
I wanted to know if I should submit patches with comments around them
like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to
the tree. I'd like to make it as easy as possible to apply these, so
let me know any rules I should be following.
2006 Nov 09
0
[LLVMdev] Fortran and LLVM
On 11/8/06, Warren Armstrong <warren.armstrong at anu.edu.au> wrote:
> Hi all,
>
> I'm looking into using LLVM to do some optimisations of
> Fortran code. As part of this, I've been trying to build
> the frontend with f95 support. At the moment, I'm trying
> to resolve undefined symbol problems for code defined in
> c-common.c + elsewhere - I'm taking