similar to: cmake: program name prefix?

Adding --program-prefix support to the autoconf build has been an adventure. A patch was applied. It worked on the usual llvm bots, but failed on other bots with different configure options. The patch was reverted as it broke on bots specifying --build, --host, and --target in configure. An option is proposed here to change the behavior of program-prefix to it's normal behavior when

the configure option --program-prefix does not work although it is listed in teh configure --help output. The attached patch fixes these issues: 1) program prefix is not substituted in configure 2) program prefix is not present in Makefile 3) scp requires use of a known "scp" program -- bryan diff -cr openssh-2.9.9p2.orig/Makefile.in openssh-2.9.9p2/Makefile.in ***

I just wanted to add to Krzysztof's response. I'm not sure if you're referring to the case when a compile-time trip count loop is completely unrolled or for a loop with a run-time trip count, which would be partially unrolled. For Hexagon, if we partially unroll a loop, we'd also like to use our hardware loop instructions. That is, unrolling and hardware loops are

Hi Brendon, Krzysztof, Thanks for your responses. On 21/11/2012 20:49, Brendon Cahoon wrote: > I just wanted to add to Krzysztof's response. I'm not sure if you're > referring to the case when a compile-time trip count loop is completely > unrolled or for a loop with a run-time trip count, which would be partially > unrolled. For Hexagon, if we partially unroll a loop,

Not to pick on anyone in particular, but for the sake of organization, I think we might need to address the need for variables beyond the standard ones defined here: http://networkupstools.org/docs/developer-guide.chunked/apas01.html From http://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_variable_names : "PLEASE don?t make up new variables and commands just because

Hi, Intel's Xed can interpret "43 40 04 75" as "add al, 0x75", but LLVM's X86 disassembler considers this invalid code. I guess the reason is that LLVM fails to recognize the REX prefix in this case. Is this correct? Thanks. Jun -------------- next part -------------- An HTML attachment was scrubbed... URL:

Óscar Fuentes wrote: > [snip] > >> Just to clarify things: have you *tried* to build LLVM with the >> makefiles generated by cmake on your BSD system? > > Just checked that the makefiles generated by cmake work with `make' on > FreeBSD 7.2 x86. The build fails while building `opt' because libdl is > missing. > They absolutely do work, even on

Chuck Robey <chuckr at telenix.org> writes: >> Just checked that the makefiles generated by cmake work with `make' on >> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >> missing. > > They absolutely do work, even on FreeBSD-current( I run that here), > but not using the native make (the one built as part of "make world"

Óscar Fuentes wrote: > Chuck Robey <chuckr at telenix.org> writes: > >>> Just checked that the makefiles generated by cmake work with `make' on >>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>> missing. >> They absolutely do work, even on FreeBSD-current( I run that here), >> but not using the native make (the

*System:* Debian Linux Sid/Unstable amd64 *LLVM/Clang:* Trunk *Scenario:* In the past couple of days I've been compiling against trunk I get two separate and spurious hang ups with CMake. *Note:* I build against more than just X86 follow along the progress of other platforms, though just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built

On 2009-05-24 20:38, Chuck Robey wrote: > Óscar Fuentes wrote: > >> Chuck Robey <chuckr at telenix.org> writes: >> >> >>>> Just checked that the makefiles generated by cmake work with `make' on >>>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>>> missing. >>>>

Hi, Óscar Fuentes wrote: > Chuck Robey <chuckr at telenix.org> writes: > > >>> Just checked that the makefiles generated by cmake work with `make' on >>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>> missing. >>> >> They absolutely do work, even on FreeBSD-current( I run that here), >>

Hi, I think I''m doing this the right way, but can''t get it going. I''m building a menu from the values in a mySQL table, and want to build it on the fly. This is something that should be working but only works halfway: <% @pages = Page.find(:all, :conditions => [''site_id = 4'']) %> <% @pages.each do |p| %> xyz <%p.id%> <%

On 11/21/2012 10:31 AM, Ivan Llopard wrote: > > Does Hexagon provides the same loop support? How have you addressed this? Yes, Hexagon has hardware support for loops: you set up the loop start address, number of iterations and indicate where the loop ends, and the hardware would execute the code repeatedly until the count goes down to zero. I'm not aware of any specific changes that

Dear all, I am trying to build the llvm with cmake and using the following checkouts. LLVM version 3.2svn clang version 3.2 (trunk 158320) (llvm/trunk 158308) cmake runs with default configuration without any problem. cmake ../llvm -- Target triple: i686-pc-linux-gnu -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Constructing LLVMBuild project information --

Sure I will split it and put it in two patches. Give me few hours. I need to test those patches. Sirish On 4/19/2012 8:40 AM, Tom Stellard wrote: > On Wed, Apr 18, 2012 at 11:18:05PM -0500, Sirish Pande wrote: >> Hi, >> >> Here's a patch for Hexagon Packetizer for review. This patch does >> not yield any warnings. >> > Would it be possible to split this

Török Edwin wrote: > On 2009-05-24 20:38, Chuck Robey wrote: >> Óscar Fuentes wrote: >> >>> Chuck Robey <chuckr at telenix.org> writes: >>> >>> >>>>> Just checked that the makefiles generated by cmake work with `make' on >>>>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is

My project has a C++ library that I want to allow the user to use via some programming language to be JIT'd to call functions in said library. For the sake of simplicity, assume the library has classes like: class item { public: item(); item( int ); ~item(); // ... }; class item_iterator { public: virtual ~item_iterator(); virtual bool next( item *result ) = 0; };

First time here, so I hope this isn''t a FAQ (although I did check *the* faq). I''m using mongrel_cluster with --prefix, and it is very slick. Thanks for that. But I had one problem. At one point in my little app, I have something like this: image_tag(url_for(:action => ''picture'', :id => 1), :size => "160x200") In this scenario,

----- Original Message ----- > From: "Renato Golin" <renato.golin at linaro.org> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Dev" <llvmdev at cs.uiuc.edu>, "jroelofs" <jonathan at codesourcery.com>, "Tobias Grosser" <tobias at grosser.es>, > "David Chisnall" <David.Chisnall at