similar to: [LLVMdev] How much adaptable is the LLVM to POSIX pattern?

Hi, as you come to speak of it, i have implemented an OpenCL-Backend for LLVM as part of my bachelor thesis (and for GLSlang as well, see http://www.cdl.uni-saarland.de/publications/theses/moll_bsc.pdf ). However, the code is currently unreleased. But that could be arranged, if you are interested in using it. Regards, Simon Am Freitag, den 26.08.2011, 20:11 -0500 schrieb llvmdev-request at

You can find out about OpenCL here: http://www.khronos.org/opencl/ That being said, AMD OpenCL is not a target of LLVM. AMD uses LLVM for its optimizer and code generation paths for the OpenCL compiler. Micah From: geovanisouza92 at gmail.com [mailto:geovanisouza92 at gmail.com] Sent: Friday, August 26, 2011 10:06 AM To: Villmow, Micah Subject: Re: [LLVMdev] Is LLVM compatible with AMD? So,

Hi all! I'm getting starting with LLVM, and I'm creating a new cross-platform programming language LLVM-based with a Standard Library POSIX-based. The language has sintatic sugar of Object Pascal and Ruby. My doubt is if LLVM is compatible with AMD (e.g. Fusion), allowing so that my StdLib can be used to create Games, in future... Regards! -------------- next part -------------- An HTML

Villmow, excuse me about the previous reply. :$ So, I'm thinking about OpenGL, or other generic graphical libraries. 2011/8/26 Villmow, Micah <Micah.Villmow at amd.com> > In what context? Also, please have all replies go to the mailing list and > not to the contributor directly.**** > > ** ** > > Thanks,**** > > Micah**** > > ** ** > > *From:*

I've got two patterns I want to match on making an outgoing call... (one day - to do Least Cost Routing for Cell/Mobile calls) Firstly - I prefer '0' rather than '9' to get an outside line... Either its a call to a mobile No... (072 -or- 082 -or- 083 -or- 084) or its just another number to dial... I added the following... the playback just advises me which 'route' is

Hey Guys, I'm trying to install R on an SGI IRIX 5.3 machine. I'm having trouble getting R to use POSIX regular expressions. Here is the error message I get when I run help: > help() Error in gsub(pattern, replacement, x, ignore.case, extended) : POSIX regular expressions not available I looked through the R-help archives and I found a few tips concerning the problem. I tried them

When trying grep(), I get the following: > grep("[a-z]", letters) Error in grep(pattern, x, ignore.case, extended, value) : POSIX regular expressions not available I can't find any pointer in the installation kit. How can I configure R to make it "avaliable"? I run R in an Irix 5.3 system. Thanks in advance! --

>>>>> <dietmar.schindler at manroland-web.com> >>>>> on Tue, 4 Apr 2017 08:45:30 +0000 writes: > Dear Sirs, > while >> regexpr('(.{1,2})\\1', 'foo') > [1] 2 > attr(,"match.length") > [1] 2 > attr(,"useBytes") > [1] TRUE > yields the correct match, an

On Apr 30, 2009, at 3:59 PM, David Greene wrote: > Here's the big RFC. > > A I've gone through and designed patterns for AVX, I quickly > realized that the > existing SSE pattern specification, while functional, is less than > ideal in > terms of maintenance. In particular, a number of nearly-identical > patterns > are specified all over for

I''ve just written an ActiveRecord adapter for Informix. It lacks a pair of features that I will add later, but it works for me. I found this on the web: http://wiki.rubyonrails.com/rails/pages/HowToWriteAnActiveRecordAdapter and followed it, but when I get to $ rake test_informix I get the following error messages: -----------------------8<-----------------------

On Apr 30, 2009, at 3:59 PM, David Greene wrote: > Here's the big RFC. > > > Of course we would not transition away from X86InstrSSE.td until > X86InstrSIMD.td is proven to cover all current uses of SSE correctly. > > The pros of the scheme: > > * Unify all "important" x86 SIMD instructions into one framework and > provide > consistency While

Here's the big RFC. A I've gone through and designed patterns for AVX, I quickly realized that the existing SSE pattern specification, while functional, is less than ideal in terms of maintenance. In particular, a number of nearly-identical patterns are specified all over for nearly-identical instructions. For example: let Constraints = "$src1 = $dst" in { multiclass

Hi, is there a core list of gems that one needs to install in a production environment? Anyways, here''s a current list of installed gems on godaddy.com: Gems *actionmailer 1.0.1* [www] <http://www.rubyonrails.org/> - depends on actionpack <http://www.situationman.com/_h_admin_/gems.html#actionpack>. Service layer for easy email delivery and testing. *actionmailer 1.1.5*

How is exact pattern matching achieved in GREP (and GREPlike) functions ? # Want: listing of all object names that end in *.lm > objects(pattern="*.lm",pos=1) # ... but get: all objects that partially match *.lm, e.g., *.lme [1] "j3.lm" "J3.lme" "j8.lm" "J8.lme" # Want: position of string "4jan2002" in vector >

At the suggestion of Stas, I'm starting a new thread on this one. This pretty much covers where I'm at right now: Doug, thanks, here's a complete listing of the config file, and some logging, hopefully this will be illuminating to somebody. > Neither of these lines set the log level. Yes, I've been setting it in the init script. When I do ps -ef | grep smbd, I see that

The SMB3 POSIX extensions is different from the old Unix extensions. The Unix extensions can only support vers=1.0, but the new SMB3 POSIX extensions can support SMB3.1.1, vers=3.1.1. You can check this 2018 presentation slides: https://www.snia.org/sites/default/files/SDC/2018/presentations/SMB/Steve_French_SMB311.pdf Page 12 shows that POSIX extensions has been added. Page 22 shows that SMB3

On 05/10/2019 06:49, Chris Han via samba wrote: > Hi, I want to use the SMB3 POSIX extensions in the latest Samba (with > SMB3.1.1, vers=3.1.1). By following the user manual, I have added the > "posix" mount option when mounting, but it shows the following error > messages. > > Error messages: > [xxxxx] CIFS VFS: Server does not support mounting with posix SMB3.11

Hey everyone, after we finished the introduction of the new posix acl api last cycle we still left the generic POSIX ACL xattr handler around for two reasons. First, because a few filesystems relied on the ->list() method of the generic POSIX ACL xattr handlers in their ->listxattr() inode operation. Second, during inode initalization in inode_init_always() the registered xattr handlers in

Hi David, On 30-Apr-09, at 6:59 PM, David Greene wrote: > This is not scalable. > > So what I've done is a little experiment to see if I can unify all > SSE and AVX > SIMD instructions under one framework. I'll leave MMX and 3dNow > alone since > they're oddballs and hardly anyone uses them. I don't want to unnecessarily expand your scope, but while

On Mon, Jan 30, 2023 at 10:10:52AM +0100, Christian Brauner wrote: > However, a few filesystems still rely on the ->list() method of the > generix POSIX ACL xattr handlers in their ->listxattr() inode operation. > This is a very limited set of filesystems. For most of them there is no > dependence on the generic POSIX ACL xattr handler in any way. > > In addition, during