llvm dev - Jul 2010 - [LLVMdev] Qualitative comparisons between Open64 and llvm

Hi!

what about
#if !defined(__cplusplus) || defined(__STDC_CONSTANT_MACROS)
in front of the constant macros for visual c to emulate
the behaviour of stdint.h more precisely?

-Jochen

Jochen Wilhelmy <j.wilhelmy at arcor.de> writes:
> what about
> #if !defined(__cplusplus) || defined(__STDC_CONSTANT_MACROS)
> in front of the constant macros for visual c to emulate
> the behaviour of stdint.h more precisely?
What is this good for?

The purpose of DataTypes.h is to provide the pieces LLVM needs and the
platform lacks. Reimplementing some missing header file is overkill,
IMHO.

Hi,

I have been working towards developing compiler optimization tools
targeting multi core processors while using LLVM IR as the starting
point and building on top of the analysis and optimization passes
available in the llvm source. 

Recently, I looked into Open64 and its intermediate representation
WHIRL. Documentation for developers to use Open64 seems to be inadequate
(when compared to LLVM documentation). I am planning to download the
source and look into it.

I was wondering if anyone has worked with both LLVM and Open64 and has
some qualitative comparisons between the two. Maybe, in terms of (a)
Ease of developing new passes (2) Ease of debugging (3) Quality of
results (4) Support for developers (5) Documentation (6) Ability to
retarget towards multi core processors.

Thanks in advance
Sincerely
Arvind

CPU Technology
Software Engineer