search for: to_low

Displaying 6 results from an estimated 6 matches for "to_low".

Did you mean: to_log
2010 Oct 18
1
[LLVMdev] pass case sensitive information to a llvm target backend
Hi, we're writing a new target backend (based on the c backend) for the llvm. We need to pass case sensitive strings from the command line to the backend (unix paths). Currently we're using the Subtarget features string to relay the information. It turns out that the llvm applies a to_lower to the this string, so unix paths become basically useless. Is there a better way to pass this information to the backend. If not, what are the chances that a patch that disables the conversion to lower case for this string is accepted? Thx, Alex P.S.: Sorry for double post, this belongs on llv...
2010 Oct 19
3
[LLVMdev] pass case sensitive information to a llvm target backend
...target backend (based on the c backend) for the >> llvm. We need to pass case sensitive strings from the command line to >> the backend (unix paths). Currently we're using the Subtarget features >> string to relay the information. >> It turns out that the llvm applies a to_lower to the this string, so >> unix paths become basically useless. >> Is there a better way to pass this information to the backend. If not, >> what are the chances that a patch that disables the conversion to lower >> case for this string is accepted? >> > Hi A...
2010 Oct 18
0
[LLVMdev] pass case sensitive information to a llvm target backend
...re writing a new target backend (based on the c backend) for the > llvm. We need to pass case sensitive strings from the command line to > the backend (unix paths). Currently we're using the Subtarget features > string to relay the information. > It turns out that the llvm applies a to_lower to the this string, so > unix paths become basically useless. > Is there a better way to pass this information to the backend. If not, > what are the chances that a patch that disables the conversion to lower > case for this string is accepted? Hi Alex, Whether there's a better...
1998 Apr 06
2
problems with chron library
I have installed the chron library, but it does not seem to work: > chron("04/06/98") Error in .C(NAME = "to_lower", strings = as.character(str), nstrings = as.integer(n)) : C/Fortran function not in load table > chron(17894) Error in .C(NAME = "to_lower", strings = as.character(str), nstrings = as.integer(n)) : C/Fortran function not in load table > I am using R Version 0.61.0 Alpha (De...
2010 Oct 19
0
[LLVMdev] pass case sensitive information to a llvm target backend
...(based on the c backend) for the >>> llvm. We need to pass case sensitive strings from the command line to >>> the backend (unix paths). Currently we're using the Subtarget features >>> string to relay the information. >>> It turns out that the llvm applies a to_lower to the this string, so >>> unix paths become basically useless. >>> Is there a better way to pass this information to the backend. If not, >>> what are the chances that a patch that disables the conversion to lower >>> case for this string is accepted? >>...
2010 Aug 06
5
[LLVMdev] PTX backend, BSD license
Hi, finally we changed the license of the PTX-backend from GPL to BSD(license of llvm). You can get the latest version here: https://sourceforge.net/projects/llvmptxbackend/ It should be compatible to the current llvm svn trunk. (revision 110329, Thu 05 Aug 2010) The backend now uses the address space attribute of LLVM for local, global, ... and constant address space. However the clang frontend