similar to: [LLVMdev] including the host triple in "include/llvm/Config/config.h"

On Nov 30, 2007, at 3:23 PM, Ted Kremenek wrote: > I was wondering if would be possible to get the host's triple captured > as a string in include/llvm/Config/config.h. Autoconf currently > generates this file, and capturing the host triple would be extremely > useful for use in the new C frontend. > > I am not an autoconf expert. Does anyone have any pointers on how >

I am at revision 45341, and I am getting a build failure on Leopard involving an unknown option to the ocaml compiler: llvm[3]: Compiling optimized llvm.ml for Debug build /opt/fink/bin/ocamlopt: unknown option `-g'. Usage: ocamlopt <options> <files> ... My ocaml binaries are compiled from source using fink: (kremenek at tedbook:llvm)$ which ocamlopt /opt/fink/bin/ocamlopt

I'm having a go at writing an LLVM backend for the WDC 65816. The documentation page on writing an LLVM backend<http://llvm.org/docs/WritingAnLLVMBackend.html>gives this example of target registration: extern "C" void LLVMInitializeSparcTargetInfo() { RegisterTarget<Triple::sparc, /*HasJIT=*/false> X(TheSparcTarget, "sparc",

> contains most of them. If they're non-trivial (like the ones I needed to > add for OSX functionality) that's a different story. FWIW the difference is even more significant on, e.g. mingw32 because process spawning is pretty much expensive and sometimes configure time dominates the compile time :) -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics,

On Jan 5, 2011, at 6:34 AM, Óscar Fuentes wrote: > arrowdodger <6yearold at gmail.com> writes: > >>> Or to say it with other words: patches welcome. >> >> So, how should i proceed? Make CMake-generated config to be identical to >> autotools one? > > That would be a good thing. > > Please note that some checks are a bit tricky. A function that

Hello. I see many discrepancies in config.h file generated by CMake and autoheader. Most of them are following: In autofoo-generated config: > /* Define to 1 if you have the `<name>' function. */ > #define HAVE_<name> 1 > but in CMake-generated: > #undef HAVE_<name> > This happens because in config.h.cmake (config.h.in analog) these functions just are not

On Jan 5, 2011, at 9:58 AM, Óscar Fuentes wrote: > Eric Christopher <echristo at apple.com> writes: > >>>> Or cleanup both headers from unused stuff by Eric's >>>> suggestion? >>> >>> I'm not sure this is a good idea (not that it is bad either). Murphy's >>> Law says that a function that you remove today will be used

DOn 2007-12-24, at 01:29, Ted Kremenek wrote: > I am at revision 45341, and I am getting a build failure on Leopard > involving an unknown option to the ocaml compiler: > > llvm[3]: Compiling optimized llvm.ml for Debug build > /opt/fink/bin/ocamlopt: unknown option `-g'. > Usage: ocamlopt <options> <files> > ... > > > My ocaml binaries are compiled

Eric Christopher <echristo at apple.com> writes: >>> Or cleanup both headers from unused stuff by Eric's >>> suggestion? >> >> I'm not sure this is a good idea (not that it is bad either). Murphy's >> Law says that a function that you remove today will be used tomorrow. > > I meant literally functions that aren't used in the

Okay, i've started slowly working. Who can i send patches for review, when they will be ready? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110106/88a7e893/attachment.html>

Andy, Yes, it was wrong, as long as RemoteTarget is available for the target. If you would revert it, please consider then; - non-MCJIT stuff - Running different environment on the JIT e.g.) --build=--host=i686-linux --target=x86_64-linux - Host-incapable target on the JIT e.g.) --build=--host=x86_64-linux ---target=i686-mingw32 If JIT is unavailable for the default target, tests

On Oct 31, 2013, at 11:54 AM, Chandler Carruth <chandlerc at google.com> wrote: > > You'll note that I replied directly to Ted's post asking whether the timeframe would be reasonable or what would be reasonable, and will naturally be waiting to hear back from him before anything happens. =] After some internal investigation and discussion, dropping support for VS 2010 no

Whoops, phone rang and I forgot to cc to the list before I typed the message. ----- Forwarded Message ---- > From: Samuel Crow <samuraileumas at yahoo.com> > To: Ruben Van Boxem <vanboxem.ruben at gmail.com> > Sent: Wed, January 5, 2011 3:38:21 PM > Subject: Re: [LLVMdev] include/Config/config.h discrepancies between CMake and >autofoo builds > > > >

On Thu, Oct 31, 2013 at 10:16 AM, Douglas Gregor <dgregor at apple.com> wrote: > On Oct 31, 2013, at 10:12 AM, Renato Golin <renato.golin at linaro.org> > wrote: > > On 31 October 2013 09:41, Douglas Gregor <dgregor at apple.com> wrote: > >> Not quite :). At present, we (= Apple) still have some dependencies on >> building top-of-tree Clang with

> > We may just not use those functions anymore - do you have a list of these? > Yes, i've started to make up a list of those functions, but it haven't finished yet. > This is more concerning - maybe it's a windows specific problem that came > along? > Not sure, i haven't look yet for CMake checking code itself. By the way, i'm using FreeBSD. Or to say it

These warnings started appearing recently when building LLVM: llvm[2]: Compiling LLParser.cpp for Release build /Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp: In member function ‘bool llvm::LLParser::ParseBr(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’: /Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3195: warning: ‘Op1’ may be used uninitialized in

This is a small bug fix for the ocaml build system that allows for dependencies to be generated for ocaml interface files. --- bindings/ocaml/Makefile.ocaml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) -------------- next part -------------- A non-text attachment was scrubbed... Name: 7c62c2cd93a6402e5f6ebd600e9e3ac7851b4d29.diff Type: text/x-patch Size: 994 bytes Desc: not

arrowdodger <6yearold at gmail.com> writes: >> Or to say it with other words: patches welcome. > > So, how should i proceed? Make CMake-generated config to be identical to > autotools one? That would be a good thing. Please note that some checks are a bit tricky. A function that on platform A is on header foo.h on another platform may be on bar.h. Furthermore, cmake's

Hey all, The frequency count returned by my ferret reader doesn''t decrement after I remove a documents with those terms. Using the example from http://ferret.davebalmain.com/api/classes/Ferret/Index/TermEnum.html the frequency increments after a document is added but stays the same after a document is deleted. index.reader.terms(:tags).each do |term, freq| "#{term} appears

On Jun 10, 2014, at 5:36 PM, C. Bergström <cbergstrom at pathscale.com> wrote: > On 06/11/14 06:58 AM, Ted Kremenek wrote: >> ** NOTE: This is a compiler job announcement. ** >> >> The Apple Source Languages team is looking for exceptional engineers to work on the Swift programming language: > Maybe this has been asked already and I missed it - Will Swift be open