[parsec-users] whole-program LLVM bitcodes

Christian Bienia cbienia at CS.Princeton.EDU
Fri Oct 16 22:53:24 EDT 2009


Hi Terence,

What type of errors did you run into? Syntax errors? Some PARSEC users have
ported the suite to quite uncommon architectures, if you describe some of
your problems in more details more people might be able to help you.

- Chris


-----Original Message-----
From: parsec-users-bounces at lists.cs.princeton.edu
[mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of Kelly,
Terence P (HP Labs Researcher)
Sent: Friday, October 16, 2009 5:36 PM
To: parsec-users at lists.cs.princeton.edu
Subject: [parsec-users] whole-program LLVM bitcodes


Has anyone attempted to build whole-program
LLVM bitcodes for the PARSEC applications?

If so, could you share tricks for making the
build work?  The LLVM tools aren't quite
drop-in replacements for their GCC counterparts
and preliminary investigation shows that this
is a non-trivial task.

I'm interested in whole-program bitcodes that
include as LLVM bitcode all code included in
the PARSEC tarball.  It's fine if things like
libc.so and libpthread.so aren't included,
but I'd like the whole-program bitcodes to
include all library code that is bundled
with PARSEC.

Has anyone done this?

Thanks in advance for any tips & tricks you
can share!

-- Terence Kelly, HP Labs Palo Alto

_______________________________________________
parsec-users mailing list
parsec-users at lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/parsec-users



More information about the parsec-users mailing list