search for: esoterically

Displaying 20 results from an estimated 287 matches for "esoterically".

Did you mean: esoterical
2009 Nov 11
4
[LLVMdev] Proposal: intp type
On Tue, Nov 10, 2009 at 6:10 PM, Talin <viridia at gmail.com> wrote: > In my case, I've been attempting to build a target-neutral frontend. In my > tool chain, the target is specified at link time, not at compile time. Among > other things, that means that the same IR file can be used for multiple > targets. That's the direction I'm going in too. > > What
2009 Nov 11
0
[LLVMdev] Proposal: intp type
I realize that most users of LLVM aren't affected by this, because most frontends aren't target-neutral, and thus know in advance how big a pointer is. At least, that's my impression. In my case, I've been attempting to build a target-neutral frontend. In my tool chain, the target is specified at link time, not at compile time. Among other things, that means that the same IR file
2009 Nov 10
3
[LLVMdev] Proposal: intp type
On Tue, Nov 10, 2009 at 8:10 AM, me22 <me22.ca at gmail.com> wrote: > 2009/11/9 Kenneth Uildriks <kennethuil at gmail.com>: >> >> 1. Conversions to/from other integer types: right now, integer type >> conversions are always explicity specified as either a trunc, a sext, >> or a zext.  Since the size of intp is not known at IR generation time, >> you
2009 Nov 02
2
[LLVMdev] Moving AVX Upstream
Hey everyone, I'm at the point with our local AVX tree that I'm ready to move some stuff upstream. We've got most of the basic stuff implemented. The more esoteric stuff still has to be done. Because the more esoteric stuff might require some extensive changes to the existing AVX infrastructure, I suspect there might be quite a bit of church until we get things stabilized. Due to
2009 Nov 11
0
[LLVMdev] Proposal: intp type
Kenneth Uildriks wrote: > On Tue, Nov 10, 2009 at 6:10 PM, Talin <viridia at gmail.com> wrote: >> In my case, I've been attempting to build a target-neutral frontend. In my >> tool chain, the target is specified at link time, not at compile time. Among >> other things, that means that the same IR file can be used for multiple >> targets. > > That's
2000 Mar 01
1
smbpasswd failure
I've attempted to change my smb password on a remote NT PDS, but it always fails with resolve_name: Attempting lmhosts lookup for name SERVER<0x20> getlmhostsent: lmhost entry: 127.0.0.1 localhost resolve_name: Attempting host lookup for name SERVER<0x20> Connecting to nnn.nnn.nnn.nnn at port 139 error connecting to nnn.nnn.nnn.nnn:139 (Connection refused) unable to connect to
2004 Sep 22
2
ordered probit and cauchit
What is the current state of the R-art for ordered probit models, and more esoterically is there any available R strategy for ordered cauchit models, i.e. ordered multinomial alternatives with a cauchy link function. MCMC is an option, obviously, but for a univariate latent variable model this seems to be overkill... standard mle methods should be preferable. (??) Googling reveal...
2012 Nov 12
2
[LLVMdev] RFC: Code Ownership
On the topic of code owners: Would it make sense to add target-specific code owners for the codegen targets? Some of the targets are more esoteric (e.g. NVPTX, CellSPU, AMDGPU) and may benefit from more fine-grained code ownership. On Mon, Nov 12, 2012 at 11:26 AM, Renato Golin <rengolin at systemcall.org>wrote: > On 12 November 2012 15:55, Meador Inge <meadori at
2002 Aug 06
1
re| `By reference'
David Brahm <brahm at alum.mit.edu> wrote: >VBMorozov at lbl.gov wrote: >> I would like to pass variables to a function in R in "by reference"... >Just in case the ensuing discussion got too esoteric, here's one simple answer: >R> x <- 1:10 >R> MyFunc <- function(x, zz) assign(deparse(substitute(zz)), sum(x), 1) >R> MyFunc(x,y) >R>
2006 Jan 23
2
Can one write a procedure in R like for instance in Maple ?
Dear R-wizards! I have been learning on my own how to use this fantastic program.. but I agree with some people that even with the manuals, the faq and so on.. when you are sitting fully alone.. progress can be ... slow... very slow indeed.. In fact sometimes, looking at the "solutions" provided by some of you- I am just flabbergasted to the point that I couldn't figure out how to
2009 Nov 11
2
[LLVMdev] Proposal: intp type
On Wed, Nov 11, 2009 at 2:10 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Kenneth Uildriks wrote: >> >> On Tue, Nov 10, 2009 at 6:10 PM, Talin <viridia at gmail.com> wrote: >>> >>> In my case, I've been attempting to build a target-neutral frontend. In >>> my >>> tool chain, the target is specified at link time, not at compile
2011 Feb 09
2
cooperation with samba?
Hallo, Simon (and Andrew), Du meintest am 08.02.11: >> in the samba mailinglist there was a remark that samba 4 is designed >> only for the BIND nameserver; look escpecially at >> >> http://lists.samba.org/archive/samba/2011-February/160848.html >> >> I know that most programmers work in their "free" time (me too). But >> I don't like
2010 Feb 18
5
OpenVPN/SNOM 820: a review.
Hey, all. Got an SNOM 820 in the other day to kick the tires. As with many phones, provisioning it was a bit of a PITA. The biggest problem, as far as I could tell, was that their firmware just doesn't seem that stable, and is sometimes hard to get to. - I managed to corrupt the firmware twice; fortunately, instead of bricking the phone, there's a fairly easy-to-use "rescue
2010 Sep 08
3
[LLVMdev] Complex regalloc contraints
Hi Carlos, Jakob, The PBQP allocator was designed to support a very wide range of constraints, and can handle something like this easily. Say you have 4 of these orX/irX registers, then for any pair of virtual registers used in such an add instruction you would add the following constraint matrix to the PBQP instance: [ 0 inf inf inf ] [ inf 0 inf inf ] [ inf inf 0 inf ] [ inf inf inf 0
2012 Nov 20
2
[LLVMdev] Getting a named value in llvm-c
Hi all, I am wondering if there is a way to get a value by name in the C interface for the LLVM Jit? There seems to be a way to name values consistently, but no way to retrieve those LLVMValueRef's by name. I see it is possible to get a struct by name and a type by name and a function by name, and a few other esoteric things, but not a general value. The reason I am wanting this is that I
2017 Oct 18
2
Is every intrinsic norecurse?
> From: piotrekpad at gmail.com [mailto:piotrekpad at gmail.com] On Behalf Of Piotr Padlewski > Sent: den 16 oktober 2017 17:33 > > Hi David, > The patch didn't get a lot of attention, so probably others does not > consider it a huge deal. Anyway, if someone is willing to review this, I > can pursue rebasing it. Okay. We are interested in getting something akin to your
2007 Apr 11
4
Feature request... I think...
Folks- I just started using Mocha and I wanted to try something but I couldn''t get it to work. I''m coming from the Java world, so my approach may not be optimal for Ruby. Say I''m testing a.do_something() which calls b.do_other_thing() twice, but I really don''t want to change b.do_other_thing(), just ''expect'' it to be called twice. I know I
2013 Nov 27
2
[PATCH v3 RFC 3/4] virtio_blk: avoid calling blk_cleanup_queue() on device loss
On Wed, Nov 27, 2013 at 12:37:02PM +0100, Heinz Graalfs wrote: > On 27/11/13 11:47, Michael S. Tsirkin wrote: > >On Wed, Nov 27, 2013 at 11:32:39AM +0100, Heinz Graalfs wrote: > >>Code is added to avoid calling blk_cleanup_queue() when the surprize_removal > >>flag is set due to a disappeared device. It avoid hangs due to incomplete > >>requests (e.g. in-flight
2013 Nov 27
2
[PATCH v3 RFC 3/4] virtio_blk: avoid calling blk_cleanup_queue() on device loss
On Wed, Nov 27, 2013 at 12:37:02PM +0100, Heinz Graalfs wrote: > On 27/11/13 11:47, Michael S. Tsirkin wrote: > >On Wed, Nov 27, 2013 at 11:32:39AM +0100, Heinz Graalfs wrote: > >>Code is added to avoid calling blk_cleanup_queue() when the surprize_removal > >>flag is set due to a disappeared device. It avoid hangs due to incomplete > >>requests (e.g. in-flight
2009 Nov 02
0
[LLVMdev] Moving AVX Upstream
On Nov 2, 2009, at 11:48 AM, David Greene wrote: > Hey everyone, > > I'm at the point with our local AVX tree that I'm ready to move some > stuff upstream. We've got most of the basic stuff implemented. The > more esoteric stuff still has to be done. > > Because the more esoteric stuff might require some extensive changes > to > the existing AVX