similar to: [LLVMdev] The source code Makefile (newbie with pass registering Problem)

Displaying 20 results from an estimated 400 matches similar to: "[LLVMdev] The source code Makefile (newbie with pass registering Problem)"

2008 Apr 22
2
[LLVMdev] The source code Makefile (newbie with pass registering Problem)
Hi!! It's me again. I guess that there is a problem in the Makefile of my source code. But I don't know where. Could you please verify it? The Makefile is written like this: # Makefile for Genetic Algorithm Pass CXXFLAGS = -Wall -I/iss/fpga3/nicole/galib247/ LDFLAGS= -L/iss/fpga3/nicole/galib247/ga/ -lga -Wl,-E # Path to top level of LLVM heirarchy LEVEL=../../../ # Name of the
2008 Apr 21
1
[LLVMdev] newbie with pass registering Problem
Hi!! This is my first time with llvm. I'm still learning and really need help. I wrote only one Function Pass, which uses another Function Pass (blockNrs), and registered this: RegisterPass<FunctionAnalysis> X("gasched", "Genom Scheduling Pass"); When I compile my sourcecode, everything was okay. But when I tried to test it, i got this error Message: nicole at
2008 Apr 23
0
[LLVMdev] newbie with pass registering Problem
Hi John!! >1) Have you ensured that your passes have different arguments to the = >RegisterPass constructor (i.e., they have different names)? Yes, I only write one Pass (Function Pass) and gave it that one name. >2) Are you sure that variable X is only being defined once? There are = >some ways in which you could have unintentionally defined it twice. For = >example, if you
2005 May 19
0
[LLVMdev] [Cygwin] llvm 'make install' build errors
Okay, this is totally bizarre. Your "make TOOL_VERBOSE=1 install" output was perfect, no errors and all the commands look the way I'd expect them to look. My version of install is 5.2.1, older than yours.But I'd expect 5.3 would not change such basic functionality. When you do "make install" without the TOOL_VERBOSE=1, you get the errors? I don't understand how
2010 Aug 15
0
unexpected behaviour with sparse.model.matrix
Hi, I'm trying to get sparse.model.matrix to retain unused levels. I can't seem to get this working through the most obvious routes such as specifying drop.unused.levels = FALSE in the model.frame or trying to pass all levels in xlev,which is an argument to sparse.model.matrix (see code below). Any help would be gratefully received. Cheers, Jarrod fac<-factor(rep(1:10,10),
2019 Feb 21
0
model.matrix.default() silently ignores bad contrasts.arg
An lme4 user pointed out <https://github.com/lme4/lme4/issues/491> that passing contrasts as a string or symbol to [g]lmer (which would work if we were using `contrasts<-` to set contrasts on a factor variable) is *silently ignored*. This goes back to model.matrix(), and seems bad (this is a very easy mistake to make, because of the multitude of ways to specify contrasts for factors in R
2004 Feb 05
0
correction to the previously asked question (about mergin g factors)
First of all, I do not understand why conversion to characters are not allowed. That's what Sundar's solution is doing implicitly (but more elegantly). Here's a test of all three. See the function definitions below. > f1 <- factor(sample(letters[1:3], 1e4, replace=TRUE)) > f2 <- factor(sample(letters[3:5], 1e4, replace=TRUE)) > f3 <- factor(sample(letters[5:7],
2019 Feb 21
0
model.matrix.default() silently ignores bad contrasts.arg
On Thu, Feb 21, 2019 at 7:49 AM Fox, John <jfox at mcmaster.ca> wrote: > > Dear Ben, > > Perhaps I'm missing the point, but contrasts.arg is documented to be a list. From ?model.matrix: "contrasts.arg: A list, whose entries are values (numeric matrices or character strings naming functions) to be used as replacement values for the contrasts replacement function and whose
2005 May 19
2
[LLVMdev] [Cygwin] llvm 'make install' build errors
Reid, Looks like the "make TOOL_VERBOSE=1 -C tools install" was fine. I have got :- install (GNU coreutils) 5.3.0 The copyright is 2005 so I would have thought it would be allright ??? Thanks, Aaron
2019 Feb 21
2
model.matrix.default() silently ignores bad contrasts.arg
Dear Ben, Perhaps I'm missing the point, but contrasts.arg is documented to be a list. From ?model.matrix: "contrasts.arg: A list, whose entries are values (numeric matrices or character strings naming functions) to be used as replacement values for the contrasts replacement function and whose names are the names of columns of data containing factors." This isn't entirely
2005 Jun 01
0
[LLVMdev] [Cygwin] 'make tools-only' configuration error
On Tue, 2005-05-31 at 23:56 +0100, Aaron Gray wrote: > Reid, > > I did look on eBay for you for replacement 2.5" harddisks but they > were expensive and in short supply :( LOL. > > >That all sounds right to me. Must be the "new" version of Cygwin. Go > >to /usr/include and do this: > > > >find . -name '*.h' -exec grep mkdtemp {} \;
2019 Feb 22
0
model.matrix.default() silently ignores bad contrasts.arg
Dear Martin and Ben, I agree that a warning is a good idea (and perhaps that wasn't clear in my response to Ben's post). Also, it would be nice to correct the omission in the help file, which as far as I could see doesn't mention that a contrast-generating function (as opposed to its quoted name) can be an element of the contrasts.arg list. Best, John > -----Original
2019 Feb 23
1
model.matrix.default() silently ignores bad contrasts.arg
>>>>> Fox, John >>>>> on Fri, 22 Feb 2019 17:40:15 +0000 writes: > Dear Martin and Ben, I agree that a warning is a good idea > (and perhaps that wasn't clear in my response to Ben's > post). > Also, it would be nice to correct the omission in the help > file, which as far as I could see doesn't mention that a
2019 Feb 22
2
model.matrix.default() silently ignores bad contrasts.arg
>>>>> Ben Bolker >>>>> on Thu, 21 Feb 2019 08:18:51 -0500 writes: > On Thu, Feb 21, 2019 at 7:49 AM Fox, John <jfox at mcmaster.ca> wrote: >> >> Dear Ben, >> >> Perhaps I'm missing the point, but contrasts.arg is documented to be a list. From ?model.matrix: "contrasts.arg: A list, whose entries are
2005 May 19
0
[LLVMdev] [Cygwin] llvm 'make install' build errors
Aaron, That looks to me like the "install" program on your platform isn't quite up to snuff. It should be doing a command like: /usr/bin/install -c -m 0755 \ /proj/llvm/build/Debug/bin/llvm-ranlib /proj/install/bin/llvm-ranlib Its not supposed to create an llvm-ranlib directory, the second argument is the name of the file to create. This works fine on linux. Can you "make
2009 May 08
2
[LLVMdev] Darwin option processing
I'm toying with building with -mdynamic-no-pic, but for this to work, the shared library bits in llvm can't be built with that flag. I've found that: Index: Makefile.rules =================================================================== --- Makefile.rules (revision 71041) +++ Makefile.rules (working copy) @@ -472,6 +476,9 @@ ifneq ($(DARWIN_MAJVERS),4) LD.Flags += $(RPATH)
2005 Mar 01
0
[LLVMdev] Typo in Makefile.rules and suugestion for Makefile.config.in
1) I find typo in Makefile.rules in printvars rule: - $(Echo) "Preconditions: " '$(Preconditions)' + $(Echo) "PreConditions: " '$(PreConditions)' 2) In Makefile.config.in PROJ_SRC_DIR define for LLVM build mode as PROJ_SRC_DIR := $(subst //,/,$(LLVM_SRC_ROOT)/$(patsubst $(PROJ_OBJ_ROOT)%,%,$(PROJ_OBJ_DIR))) and for other project build mode as PROJ_SRC_DIR
2004 Oct 23
1
[LLVMdev] UPDATE: Makefile.rules Changes (IMPORTANT)
If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.
2009 May 08
0
[LLVMdev] Darwin option processing
On May 7, 2009, at 6:24 PM, Mike Stump wrote: > I'm toying with building with -mdynamic-no-pic, but for this to work, > the shared library bits in llvm can't be built with that flag. Hi Mike, If you're doing this for Clang's benefit, I think the best thing to do is to compile LLVM PIC (the default) and then build the clang front- end pieces with -mdynamic-no-pic. Does
2008 May 16
0
[LLVMdev] Size and performance figures for LLVM?
On May 14, 2008, at 4:46 AM, Dominic Hamon wrote: > Bill Wendling wrote: >> On Tue, May 13, 2008 at 2:24 AM, Joachim Durchholz >> <jo at durchholz.org> wrote: >> >>> Am Dienstag, den 13.05.2008, 00:42 -0700 schrieb Bill Wendling: >>> >>>> Sorry to step into this in the middle of a thread, but what >>>> exactly is