similar to: [LLVMdev] LLVM: C++ -> C

On Sep 29, 2009, at 9:37 AM, dilas dilas wrote: > I've read that LLVM can convert from C++ to C code. It does, but it does not supply a C++ library. You'll need to do that. > So I've used it in such a way: > I'm Windows-user so I used MinGW. > I employed this file as the test: > > llvm-hello.cpp: > > #include <iostream> > > int main(int

Hello, Jeff. You wrote Saturday, January 22, 2005, 3:57:28 AM: JC> Reid, the binary/text mode is a valid issue. This set of flags worked for me: std::ios_base::out | std::ios_base::trunc | std::ios_base::binary Yes, there are open issues with std::ios_base::binary, but llvm are not affected with them now. JC> I have successfully used a bytecode file on Windows that was created JC> on

Thanks for the suggestion, Andre. I downloaded GNAT GPL 2007, and followed the directions on your web page. Now I get a lot of C++ errors. In fact, the output I captured to a log file is over six megabytes just from the start of the problem command to the termination of the make. I'm obviously not going to include it all here, but the command and the first few errors are copied below.

I see that some of the system header-file definitions have the internal keyword. For example, define internal void @__cxx_global_var_init() section "__TEXT,__StaticInit,regular,pure_instructions" { entry: call void @_ZNSt8ios_base4InitC1Ev(%"class.std::ios_base::Init"* @_ZStL8__ioinit) %0 = call i32 @__cxa_atexit(void (i8*)* bitcast (void

On 5/23/11 1:05 PM, George Baah wrote: > Hi, > I am writing a pass which is supposed to ignore library functions. Is > there a way to > distinguish functions declared and defined by a developer from > non-local functions (library functions)? > Thanks. There is no reliable way to do this, but there are several heuristics that will probably work well in practice. When

Hi Eric, > llvm-main.o: In function `__static_initialization_and_destruction_0': > /usr/lib/gcc/i386-redhat-linux/4.3.2/../../../../include/c++/4.3.2/iostream:77: > undefi\ > ned reference to `std::ios_base::Init::Init()' > /usr/lib/gcc/i386-redhat-linux/4.3.2/../../../../include/c++/4.3.2/iostream:77: > undefi\ > ned reference to `std::ios_base::Init::~Init()'

Hi, I am writing a pass which is supposed to ignore library functions. Is there a way to distinguish functions declared and defined by a developer from non-local functions (library functions)? Thanks. George -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110523/650c7fa4/attachment.html>

No, Chris, I'm not buying that argument, due to I've tweaked /usr/include/types.h a little bit, so the configuration and compilation of the cfrontend would be correct: /* * 64bit type for BSD compatability */ #ifdef __GNUC__ typedef long long int quad_t; typedef unsigned long long int u_quad_t; typedef long long int int64_t; typedef unsigned long long int u_int64_t;

Hi guys Is some one able to explain me, why these errors emerge: gmake[2]: Entering directory `/usr/local/src/llvm/lib/VMCore' Compiling AsmWriter.cpp AsmWriter.cpp: In function `void WriteConstantInt(std::ostream&, const llvm::Constant*, bool, std::map<const llvm::Type*, std::string, std::less<const llvm::Type*>, std::allocator<std::pair<const llvm::Type* const,

Hi, I am not sure how widespread this problem is, but definitely occurs for me on 64 bit Win 7 with a 64 bit R. I think I have isolated the issue (to a certain extent) in the attached Test.cpp file. Basically, I think linking with boost serialization is causing the plugin to fail. If I compile Test.cpp with line 43 (Dummy* Read() ...) commented out, I get the expected output in R: >

On Wed, 7 Jul 2004, Henrik Bach wrote: > This tweak seems to work. > > As far as I can see, correct me if I'm wrong, it is the compiler, that can't > figure out which std::basic_ostream to use. Why? What I'm saying is that it appears that your implementation of operator<< is not functional or is missing. You said that you are using GCC on internix. Is it possible

On Fri, 17 Aug 2007, David Greene wrote: >> Posix is pretty available, what system doesn't have them? > > Windows, for one. If POSIX is ok, it's better in my mind to just directly Windows has POSIX calls. > use open, write and friends, which is what I do now. Going the cstdio > route should only be done for portability reasons to support non-POSIX > systems. I

Yes, Chris you're right. It seems that my << operator for int64_t is missing in my '/opt/gcc.3.3/include/c++/3.3/bits/ostream.tcc' file. Which ordinary version of GCC are you working with and how do your definition of the << operator for int64_t look like? /Henrik > >Here is an excerpt from the config.log for LLVM: > >configure:19451: checking for int64_t

Hello, lately, I have been thinking about how to resolve the problem with that the program size increases enormously when including <iostream> when compiling with libstdc++. In this library, in <iostream> there is a static object __ioinit initialized like so: ... // For construction of filebuffers for cout, cin, cerr, clog et. al. static ios_base::Init __ioinit; ... This

Hi, Sorry, I just tried posting this but I had it in the wrong format of text, so this is a cleared format repost: I?m trying to call some of my c++ code from R and seem to be having an issue with streams, although that?s just one obvious sign of something different in performance between calling the same function from main in c++ vs. calling the same function from R. I?m not getting any signs

On Friday 17 August 2007 13:17, Chris Lattner wrote: > On Fri, 17 Aug 2007, David Greene wrote: > >> Posix is pretty available, what system doesn't have them? > > > > Windows, for one. If POSIX is ok, it's better in my mind to just > > directly > > Windows has POSIX calls. Ok, I'll admit I don't know a lot about what's available there.

Hi Dimitry, I do not particularly need to build libc++ from the package. Is the name of the package's libc++, libcxx, because this is where the installation starts finding undefined references, during linking CXX shared library ../../../lib/libc++.so. Please check below the first part of the log when the first error appear, I omited repeating results. Furthermore, the undefined references are

Hello All, I came to know from a friend that using LLVM insfrastucture one can convert C++ programs to C. I needed this for my cross-compiler because we don't have support for C++ compilation in our cross-compiler. I tried following: http://llvm.org/docs/FAQ.html#translatecxx While I can generate .bc its llc which gives error. Then I also tried "clang" as oppose to llvm-g++. Here

Hi Ioannis, Just delete the projects/libcxx directory, then rebuild from scratch. You should only need to checkout llvm (in the top level directory) and cfe (into the tools/clang subdirectory). -Dimitry > On 29 Mar 2016, at 00:08, Ioannis Koukoulis <i.g.koukoulis at gmail.com> wrote: > > Hi Dimitry, > > I do not particularly need to build libc++ from the package. Is the

Hi Dimitry, this definitely worked. I am passed by the linking errors regarding libc++ or similar. My build stopped now at 95% while linking a clang extra, I am not pretty sure which because i do not have my laptop, possible the clang-rename, if such exists. No undefined references here, however, my hdd's free space run out, so this might be the cause. I have to move or expand now, alas!! The