search for: iform

Displaying 20 results from an estimated 21 matches for "iform".

Did you mean: form
2007 Feb 14
2
[LLVMdev] Linux/ppc backend
...GPRClass::iterator I; if (Subtarget.isMachoABI()) { I = Defs_Macho + (sizeof(Defs_Macho)/sizeof(unsigned)); } else { I = Defs_ELF + (sizeof(Defs_ELF)/sizeof(unsigned)); } return I; } }] in { // Convenient aliases for call instructions def BL : IForm<18, 0, 1, (ops calltarget:$func, variable_ops), "bl $func", BrB, []>; // See Pat patterns below. def BLA : IForm<18, 1, 1, (ops aaddr:$func, variable_ops), "bla $func", BrB, [(PPCcall (i32 imm:$func))]>; d...
2001 Oct 09
1
bug in paste?
...from m inbetween the ce0 values at all! However, this needs some background information. ce0 is originally from a large dataset (7000 obs x 1200 vars), read from a stata7-file using read.dta: > ce0 <- read.dta( "file.dta")[1,230:240] So I am afraid ce0 contains some kind of extra iformation which I was not able to figure about. Can anybody explain me what is going on here? My R is as follows: platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 1 minor 3.1 year 2001 month 08 day 31 language R Thanks in advance,...
2013 Jul 21
3
[LLVMdev] Inst field in MSP430InstrFormats.td
...quot;MSP430InstrFormats.td" there is a class called "MSP430Inst" which has "Instruction" as superclass. Within this class there is a field called "Inst" (field bits<16> Inst;) which gets assigned in classes which specifies a specific instruction format, e.g. IForm contains: let Inst{12-15} = opcode; let Inst{7} = ad.Value; let Inst{6} = bw; let Inst{4-5} = as.Value; >From what I can see these values does not propagate to the files generated by TableGen. I have tried removing the field and it is at least still possible to run llc on a simple input...
2007 Feb 15
0
[LLVMdev] Linux/ppc backend
...> I = Defs_Macho + (sizeof(Defs_Macho)/sizeof(unsigned)); > } else { > I = Defs_ELF + (sizeof(Defs_ELF)/sizeof(unsigned)); > } > > return I; > } > }] > > in { > // Convenient aliases for call instructions > def BL : IForm<18, 0, 1, (ops calltarget:$func, variable_ops), > "bl $func", BrB, []>; // See Pat patterns > below. > def BLA : IForm<18, 1, 1, (ops aaddr:$func, variable_ops), > "bla $func", BrB, [(PPCcall (i32 im...
2006 Oct 16
0
[LLVMdev] Implicit defs
...].second.getValueType())); if (InFlag.Val) Ops.push_back(InFlag); Chain = DAG.getNode(CallOpc, NodeTys, &Ops[0], Ops.size()); This creates a call node with a list of input registers, these are marked as uses. In the PPC backend, this is matched with this pattern: ... def BLA : IForm<18, 1, 1, (ops aaddr:$func, variable_ops), "bla $func", BrB, [(PPCcall (i32 imm:$func))]>; ... The "variable_ops" part of the operation list causes all those registers to be added to the node when the isel turns the isel graph into the sched...
2007 Feb 02
0
[LLVMdev] Linux/ppc backend
On Fri, 2 Feb 2007, Nicolas Geoffray wrote: > I have almost completed the implementation of a linux/ppc backend in llvm. Cool! > There were a few things to modify in > lib/Target/PowerPC with a lot of "if (!isDarwin)". Some meta comments: 1. Please don't change PPC -> llvmPPC. I assume that you did this because PPC is a #define in some system header. Please
2006 Oct 15
2
[LLVMdev] Implicit defs
Hi Chris, Thanks for your response. > On Sat, 14 Oct 2006, Roman Levenstein wrote: > > Is it possible to dynamically define implicit defs for some > > instructions? > > Yes! This is what explicit operands are :). Specifically, if you > want to > vary on a per-opcode basis what registers are used/def'd by the > instruction, you can just add those registers
2013 Dec 15
2
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
...nd then get similar information from the other vendors, then it should be straight forward to add a routine to the upsdrvctl connection code that does something like: Attempt to connect if no connect; then probe usb system with udevadm info -a -n for all /dev/bus/usb/*/* parse/compare to known iformation if data matches known; then write/install udev rule (or use found information to otherwise connect) fi fi Attempt to connect if no connect; the throw error; fi This again, is all just brainstorming. If you have thoughts on it, let me know. I will have limited time over the next few...
2009 Nov 10
0
Pdbedit <-> /etc/passwd sync?
Hi, i have a question about syncing without pdbedit (exactly iformations stored in passdb.tdb) and /etc/passwd. I creating user with some comment, for example adduser test -c "my comment" -d /home/users/test -g 600 -s /bin/false and then i will add this user to samba pdbedit -a -s /etc/samba/smb.conf -u test Now i have stored in samba also comment...
2009 Nov 12
0
Pdbedit <-> /etc/passwd sync? (fwd)
...---------- Forwarded message ---------- Date: Tue, 10 Nov 2009 15:01:19 +0100 (CET) From: extmaillist at linuxbox.cz To: samba at lists.samba.org X-Spam-Score: -1.0 (), 4 required Subject: [Samba] Pdbedit <-> /etc/passwd sync? Hi, i have a question about syncing without pdbedit (exactly iformations stored in passdb.tdb) and /etc/passwd. I creating user with some comment, for example adduser test -c "my comment" -d /home/users/test -g 600 -s /bin/false and then i will add this user to samba pdbedit -a -s /etc/samba/smb.conf -u test Now i have stored in samba also comment...
2006 May 15
1
[LLVMdev] Old-style code generators broken?
Hi, it looks like old-style code generators can no longer work with LLVM CVS, because: 1. The TableGen uses the DAG from instruction to computed the number of operands written in generated tables, and when there's no DAG, writes 0. 2. MachineInstructions::addRegOperand checks for maximum number of operands. So, when not using DAGS in TableGen input, addRegOperand asserts on adding the very
2013 Jul 22
0
[LLVMdev] Inst field in MSP430InstrFormats.td
...ats.td" there is a class called > "MSP430Inst" which has "Instruction" as superclass. Within this class > there is a field called "Inst" (field bits<16> Inst;) which gets > assigned in classes which specifies a specific instruction format, > e.g. IForm contains: > let Inst{12-15} = opcode; > let Inst{7} = ad.Value; > let Inst{6} = bw; > let Inst{4-5} = as.Value; > > From what I can see these values does not propagate to the files > generated by TableGen. I have tried removing the field and it is at > least still possi...
2005 May 28
2
xc-ast 0.9.0 is out today
.... * Due to popular demand, an explicit "delta" from period to period was added. * It is now possible to see waiting periods and call durations in real-time (as long as your system clock is the same or is synchronized to the Asterisk clock; in any other case you will not see relevant iformation and should turn off this feature). * Fixed a bug with the English pages where a percentage was showed with the Italian locale * Assorted minor bugfixes As always, the product is available free (as in beer) to smaller installations and * enthusiasts around the world to use and hack. Fut...
2007 Feb 02
5
[LLVMdev] Linux/ppc backend
Hi everyone, I have almost completed the implementation of a linux/ppc backend in llvm. There were a few things to modify in lib/Target/PowerPC with a lot of "if (!isDarwin)". There are some places where I need help before saying the port is complete. I attached the diff file as a reference 1) In order to generate a creqv instruction before a vararg call, I created a new
2013 Dec 15
0
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
On Dec 14, 2013, at 4:23 PM, David C. Rankin wrote: > Do you know if the problem with upsdrvctl being able to probe/connect to the > usb devices is the result of some default permission change in Linux in general. > It seems to me that since nut used to work right out-of-the-box, then all/most > distros must have had the default permissions on usb nodes set to 0666, where >
2013 Dec 16
0
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
...een multiple UPSes (which can be done at the NUT driver level in ups.conf), but would not be necessary for setting the proper permissions with udev. > Attempt to connect > if no connect; then > probe usb system with udevadm info -a -n for all /dev/bus/usb/*/* > parse/compare to known iformation > if data matches known; then > write/install udev rule (or use found information to otherwise connect) > fi > fi > Attempt to connect > if no connect; the throw error; fi While this should work, the parse/compare step should be done by udev using the existing rules fi...
2007 May 26
14
big problem with HTB/CBQ and CPU for more than 1.700 customers
2013 Dec 14
2
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
On 12/14/2013 02:06 PM, David C. Rankin wrote: > Charles, > > Setting uid:gid to root:nut on /dev/bus/usb/004/002 seemed to be the issue. > The question now become how to automate this process so that the user isn't > required to manually hunt down the usb dev and change gid to the nut gid? So > far, either manually setting the gid or hand-rolling the udev files to do the
2012 Sep 17
1
[LLVMdev] SPIR provisional specifciation is now available in the Khronos website
...sible and while the vector type conversions are well defined in LLVM and properly converts to scalar when needed, SPIR needs to be able to work with people who don't use LLVM. By adhering as close as possible to OpenCL C, the amount of work to support SPIR is reduced. 2) From what I've been iformed of by Aaftab Munshi, when OpenCL C was developed, there were many different implementations that supported vector casts, but they were not conversion casts(e.g. Altivec/Cell C extensions). So OpenCL requires explicit vector conversion functions, and as such SPIR inherits those rules. 3) Since man...
2012 Sep 11
0
[LLVMdev] SPIR provisional specifciation is now available in the Khronos website
Hi Boaz, I have a couple of specific questions: (a) You mention special calling conventions and adding them to LLVM. What are their semantics? And what is their purpose? (b) Why disallow type conversion for vector types? (ss. 3.3) Cheers, James On Tue, 2012-09-11 at 12:56 +0100, Ouriel, Boaz wrote: > Hi All, > > In continuation of the previous SPIR introduction email here is a link