similar to: Help with Error: POSIX collating elements are not supported

For sometime now I have not been able to print Collated pages on windows client machines Domain Wide. Our print server is cups, running on Linux Gentoo. If I print directly to the printer within windows I am able to collate. If a Linux machine prints from command line specifying Collate=True while printing pages it works. I have been searching quite some time now to find a fix, or a how to but no

R 0.65.0 (and all others I have seen), Solaris 2.6. > sort(c("a", "A", "b", "B")) [1] "A" "a" "B" "b" > "a" < "B" [1] FALSE in the en_UK locale. I don't think it is good idea that sort and < have a different idea of ordering, so I rate this as a bug. As far as I can see sort uses

Dumb newbie question: I've searched the manual, R help and the mailing list archives, but can't seem to find the answer to this simple problem that I have. If I have a series of columns in a dataframe: (A, B, C ...) and I want to merge them with another series of columns (Z,Y,X ...) such that the resulting data frame has columns A,Z,B,Y,C,X ..., how do I do this? In other words, I'm

Hello, I have a question about postfix. I have a few webservers, each with their own mailing system. Obviously manually adding items can be quite tedious going from one to another to another. I am in the process of making a list of domains (commercial spammers) that bother me. My idea is to use the access file to reject them. My question is this... Can I make a text page on one of my html

Doug, I have been attempting to learn a little bit about nlme without too much documentation except the online help. The Latex file in the nlme directory looks interesting but uses packages that I do not have so that I have not been able to read it. I have run the example from gnls to compare it with the results I get from my libraries (code below - I have not included output as it is rather

Hi Susan, Thanks for the clarification, and the test case. I think I know what the problem is now. Saving and restoring RBP is the job of the PEI (PrologEpilogInsertion) pass, which runs after register allocation. To determine which callee-saved physregs actually need to be saved it checks MachineRegisterInfo::isPhysRegOrOverlapUsed(unsigned reg). Your register allocator needs to notify

Thanks Lang, I'll try substPhysReg. I did try your latest code, and although it made the assembler errors go away, now some of my tests produce bad output when executed. I need to look into that some more... (I did change my "usedPregSet" to be ALL pregs used in the whole function, not just those in the current instruction, so the problem should not be the erroneous

Hi Susan, RBP is used as the frame pointer on x86 (hence its automatic appearance in your code), and shouldn't be allocated to any vreg in function bar. Loading/saving RBP should be managed by the stack frame setup/teardown code. If it doesn't already, your allocator should filter out reserved registers (See MachineRegisterInfo::isReserved(unsigned preg)) when assigning physregs.

Aha, yes, this is definitely helpful! Is there documentation on all this somewhere? I still have errors for some large test inputs, and it would be nice if I didn't have to keep bugging you for information. Thanks! Susan On 12/2/2012 10:55 PM, Lang Hames wrote: > Hi Susan, > > Thanks for the clarification, and the test case. I think I know what > the problem is now. Saving

Thanks Jakob. I should have mentioned that earlier. :) When you see mismatched sizes on operands it's a fair bet that the subreg rewriting has gone wrong. I should have pulled that entirely out of the preg search loop in the previous example. Fixed version attached. - Lang. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Susan, Jakob just pointed me to 'MachineOperand::substPhysReg(unsigned preg, const TargetRegisterInfo& TRI)'. That substitutes the given physreg for a virtreg operand, taking the subregister index into account. That is what my examples have been doing manually. Using substPhysReg would allow you to tidy the Gcra code up slightly. - Lang. On Thu, Nov 15, 2012 at 11:21 AM, Lang

Hey all, I've found a bug in either the PBQP register allocator or in VirtRegRewriter. I'm observing this assertion in VirtRegRewriter::rewrite() fail: unsigned VirtReg = MO.getReg(); unsigned PhysReg = VRM->getPhys(VirtReg); ... assert(!MRI->isReserved(PhysReg) && "Reserved register assignment"); Indeed there is a case where

Hi Susan, The problem is that the allocator is re-using the 'preg', which is calculated for an operand that may have a subreg index, for loads and stores to a stack-slot. The stack slot always has the same width as vreg (which is the right behavior), but for operands with subreg indexes, 'preg''s class will be different from 'vreg', in which case you get the mismatched

Thanks Lang, we are making progress! I no longer get the failed assertion, but the code I'm using for vregs that don't get allocated a preg, and thus need to be spilled and re-loaded is causing assembler errors. I suspect the problem is my code for allocating space in the stack, but I don't know how to fix it. I've attached a new version of the simple register-allocation

Can someone explain the theory behind the spillers in VirtRegMap.cpp? It seems as though the spillers do triple duty: - Insert load/store operations and/or fold instructions as necessary to carry out spills - Rewrite the spilled virtual registers to use machine registers (mapping given by the caller in the VRM). - Rewrite machine code to change virtual registers to physical registers

Hi Susan, In x86-64 the REX prefix must be used to access an extended register (r8-r15 and their aliases), but cannot be used when accessing the high byte of the ABCD regs (AH, BH, CH, DH). In your test case you have hardcoded %vreg1 to R8B, and %vreg15 to AH, and the test case contains a copy between these registers. The copy simultaneously must have a REX prefix, and cannot have a REX prefix,

Lang - Your fix does prevent the assembler errors, but it doesn't seem to produce correct assembly. I created a slightly modified version that, for each instruction that includes a vreg, adds a check that the preg selected is not already in that instruction. I've attached that version. I think that this version of Gcra.cpp should produce correct assembler, since it's allocating

Thanks Lang! Here's another question: I'm trying to process this input: int main() { return 0; } but I'm getting an error Assertion `!Fn.getRegInfo().getNumVirtRegs() && "Regalloc must assign all vregs"' failed. At the start of runOnMachineFunction I call Fn.getRegInfo().getNumVirtRegs(); and find that there is 1 virtual register. However,

Estimados ?podrían enviarme un ejemplo en el que analicen un documento de texto con la librería library(tm) mis saludos cordiales jose [[alternative HTML version deleted]]

Sorry about that. I created the assembly file and attached it (as math.txt). Susan On 11/11/2012 12:41 AM, Lang Hames wrote: > Hi Susan, > > It looks like the bitcode you have attached is corrupted. You should > make sure to attach it as a binary file. Alternatively you can attach > the LLVM assembly as text. You can generate an assembly file from > bitcode with: > >