search for: pecular

This is something between a question and a bug report. {sometimes one should first ask on R-help before sending to R-bugs....} I wanted to plot (.) a formula with "..." ## Works : e0 <- expression(T(x[1],...x[n])*", "*N[1] == 101) # works ok plot(1, main = e0) ## Now, need substitute, to replace with value of variableThis works nn <- 102 (e1 <-

Thank you for this reply. If so, is there any way to merge basic blocks into a single one? Thanks, Seung J. Lee ---- Original message ---- >Date: Fri, 29 Jun 2007 22:27:38 +0200 >From: Basile STARYNKEVITCH <basile at starynkevitch.net> >Subject: Re: [LLVMdev] LLVM assembly without basic block >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >Seung

thanks Evan, I have just started writing td files. Any ideas how do I describe instructions for an accumulator based machine. The other pecularity is that we do not want to have any software stack. So the instructions like load and store have no meanings. In that case, how do I lower instructions that operate on stack frame? TIA, Sanjiv On 11/26/07, Evan Cheng <evan.cheng at apple.com> wrote: > > > On Nov 24, 2007, at 7...

...the control flow graph, i.e. by the points in the >>> program to which (conditional or unconditional) jumps go. In other words, basic blocks are defined by the destination of >>> goto (in particular those in loops and tests) and calls. > > >Basic blocks is not some LLVM pecularity, it is a notion you can find in any compiler book! > >The only way to have bigger basic blocks is to avoid branching (ie any kind of jumps, including loops, tests, function >calls and returns). > >Intuitively you cannot jump inside a basic block or outside of it, only at the star...

Hello all. I am trying ot load table rows using AJAX based on a search. The following code results in: 1. Firefox renders correctly (Multiple rows inserted into page). 2. Opera renders the entire returned string in one <td> by the looks of it (Bunched up under first header, the <> tags arne''t visible) 3. IE6 does nothing....great ;) This is driving me nuts so any help

Hello. I have a question to inheritance in Rails(2.3.4). I have this three models. class Vehicle < ActiveRecord::Base end class Car < Vehicle end class RallyCar < Car end And this Migration: class CreateVehicles < ActiveRecord::Migration def self.up create_table :vehicles do |t| t.string :name t.string :brand t.string :type t.timestamps end

On Nov 24, 2007, at 7:28 PM, Sanjiv Gupta wrote: > Could anybody guide me what information do I need to know about my > target in order to provide the target lowering info to the llvm DAG > generator? We do not have any fixed registers for argument passing. > Everything including the formal and actual arguments will take part in > a global interprocedural regalloc. You don't

Could anybody guide me what information do I need to know about my target in order to provide the target lowering info to the llvm DAG generator? We do not have any fixed registers for argument passing. Everything including the formal and actual arguments will take part in a global interprocedural regalloc. Any pointers to learn about this will be a great help. Sanjiv

...d: Permission denied >> RS >> RS >> ^CRS >> Signal 2: exiting >> $ >> > > Actually, it wasn't my intent that patch would go into the distribution, it was my intent to help others who have these UPSes > still in service to get a better handle on their pecularities. But, you actually bring up a great point. Why have ANY variables at all in upslog? I'm not PL so I don't decide what gets into production here and the point simply was 1.) , intended to RFC the community of this general developer practice Q, but in no way to insult You in any way....

...ritepid: fopen /var/run/nut/upslog.pid: Permission denied > RS > RS > ^CRS > Signal 2: exiting > $ > Actually, it wasn't my intent that patch would go into the distribution, it was my intent to help others who have these UPSes still in service to get a better handle on their pecularities. But, you actually bring up a great point. Why have ANY variables at all in upslog? We should just have the output of upslog an empty log. And tell users to specify ALL the parameters they want that are important to them on the command line to upslog. After all, selecting ANY parameters...

...".section .altinstr_replacement,\"ax\"\n" \ + "663:\n\t" newinstr "\n664:\n" /* replacement */ \ + ".previous" :: "i" (feature) : "memory") + +/* + * Alternative inline assembly with input. + * + * Pecularities: + * No memory clobber here. + * Argument numbers start with 1. + * Best is to use constraints that are fixed size (like (%1) ... "r") + * If you use variable sized constraints like "m" or "g" in the + * replacement maake sure to pad to the worst case length. +...

...".section .altinstr_replacement,\"ax\"\n" \ + "663:\n\t" newinstr "\n664:\n" /* replacement */ \ + ".previous" :: "i" (feature) : "memory") + +/* + * Alternative inline assembly with input. + * + * Pecularities: + * No memory clobber here. + * Argument numbers start with 1. + * Best is to use constraints that are fixed size (like (%1) ... "r") + * If you use variable sized constraints like "m" or "g" in the + * replacement maake sure to pad to the worst case length. +...

I'm having trouble grokking complex NaN's. This first set examples using complex(re=NaN,im=NaN) give what I expect > Re(complex(re=NaN, im=NaN)) [1] NaN > Im(complex(re=NaN, im=NaN)) [1] NaN > Arg(complex(re=NaN, im=NaN)) [1] NaN > Mod(complex(re=NaN, im=NaN)) [1] NaN > abs(complex(re=NaN, im=NaN)) [1] NaN and so do the following > Re(complex(re=1,

...> RS >>> ^CRS >>> Signal 2: exiting >>> $ >>> >> >> Actually, it wasn't my intent that patch would go into the >> distribution, it was my intent to help others who have these UPSes >> still in service to get a better handle on their pecularities. But, >> you actually bring up a great point. Why have ANY variables at all in >> upslog? > > I'm not PL so I don't decide what gets into production here and the > point simply was 1.) , intended to RFC the community of this general > developer practice Q, >...

Hi Ted, Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: > > Note that since the UPS relies on the voltage from the battery pack to > determine state of charge, it is quite useful to add in the battery pack > voltage to the logs as such: > > --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 > +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 > @@ -50,6 +50,7

...sp), %%esp" +#define vmi_postamble7 "lea 28(%%esp), %%esp" +#endif + +#if defined(CONFIG_VMI_STDCALL) +#define vmi_postamble(num_inputs) +#else +#define vmi_postamble(num_inputs) vmi_postamble##num_inputs +#endif + +/* + * VMI inline assembly with input, output, and clobbers. + * + * Pecularities: + * Input and output must be wrapped using XCONC(...) + * Best is to use constraints that are fixed size (like (%1) ... "r") + * If you use variable sized constraints like "m" or "g" in the + * replacement make sure to pad to the worst case length. + */ + +#defin...

...sp), %%esp" +#define vmi_postamble7 "lea 28(%%esp), %%esp" +#endif + +#if defined(CONFIG_VMI_STDCALL) +#define vmi_postamble(num_inputs) +#else +#define vmi_postamble(num_inputs) vmi_postamble##num_inputs +#endif + +/* + * VMI inline assembly with input, output, and clobbers. + * + * Pecularities: + * Input and output must be wrapped using XCONC(...) + * Best is to use constraints that are fixed size (like (%1) ... "r") + * If you use variable sized constraints like "m" or "g" in the + * replacement make sure to pad to the worst case length. + */ + +#defin...

THANKYOUTHANKYOUTHANKYOUTHANKYOU!!!!!! There was a smaller patch posted to the list for lines -1389,9 +1390,10 a couple years ago, it helped some - BUT - it was still buggy. I have a Compaq R3000, I will get this patch integrated pronto and test Note that since the UPS relies on the voltage from the battery pack to determine state of charge, it is quite useful to add in the battery pack

Thanks Martin and Peter, I agree that we can be careful and narrow and still see a nice improvement in behavior. While Herve's point is valid and I understand his frustration, I think staying within the matrix vs c(matrix, array) space is the right scope for this work in terms of fiddling with inheritance. As another point, I don't know off the top of my head of any other classes which