search for: spitbal

Just spitballing... why not have a splat construct straight through LLVM? It would make the IR more readable, opposed to the insert+shuffle method. On Thu, Aug 29, 2019 at 19:06 Amara Emerson via llvm-dev < llvm-dev at lists.llvm.org> wrote: > +1 to a new node, we’d very likely do the same thing for...

Hi, I am new to R and wondering if it is possible for it to connect to an Informix database. I tried google but nothing came back that I could figure out. Can somebody tell me if its possible (which I believe it is) and how to connect to an Informix database using R. Thanks! -- View this message in context: http://r.789695.n4.nabble.com/R-connect-to-Informix-Database-tp4310594p4310594.html

after investigating why the reloader wasnt working , i discovered 2 probs, one of which was sorta my fault (but will likely happen to others who make one-file apps) first, my app was like this: #!/usr/bn/env ruby %w{applib1 applib2 digest/md80 airbus}.each{|r| require r}} if __FILE__ == $0 Mongrel.config do handler ''/'', Camping.reloader.new(__FILE__) end end not

I'm running Samba 4 and I've created a share on a member server to hold the message files for the Thunderbird email client. Over time I seem to get corruption of the message files to the point where the folder file needs to be reconstructed outside of Thunderbird. In other cases, the file corruption in combination with folder compaction results in deletion of the messages in the folder.

Hi, During the discussion on introducing scalable vectors we established that we could use the canonical IR form for splats of scalable vector types (insert element into lane 0 of an undef vector, shuffle that with another undef vector of the same type and a zeroinitializer mask). We do run into a problem for lowering to SelectionDAG however, since the canonical form there is a BUILD_VECTOR with

I love the pointer analogy. Presumably the additional complication of scope breaks this however. * itself would have been a nice operator for this were it not prone to ambiguity (`a * *b` vs `a**b`, from which @ does not suffer). Would this extension require that function authors explicitly enable auto-quoting support? I somewhat envisioned functions seeing the resolved unquoted object (within