search for: textualment

I'm a little less new to samba now - but having a heck of a time getting authentication to work. I'm running NIS+, configured samba with --with-nisplus --with-nisplus-home and --with-automount. Does anyone have some good nis/samba references? I'm striking out. The smbpasswd file *does* have to become smbpasswd.org_dir for samba to work. I first created the smbpasswd file using

Hi, I would like to know whether anybody knows a simple way to combine textual and graphical output in R. A typical analysis produces textual output (e.g. model fits) and plots in R. I would like to know whether R has the possibility of combining these into a single 'report' or output. An example of a program that does this is SPSS. After running the analysis you have a combination

Hello, I think this might be a beginner question, but I couldn't find the answer in the manual... http://www.nabble.com/file/p14618947/at-modality.png I created this image with R by using the following code: modality <- read.table("results.table", header=TRUE, sep=",") color <-

Hi all, I am implementing a LLVM IR interpreter and have the following problem: I want to support execution of bitcode files targeted towards different LLVM versions. For example, a user of the interpreter should be able to compile a C file with the latest version of Clang, a Fortran file with Dragonegg (targeting LLVM 3.3), and a Haskell file with GHC (targeting LLVM 3.5), and then just feed it

I've just found the lavaan package, and I really appreciate it, as it seems to succeed with models that were failing in sem::sem. I need some clarification, however, in the output, and I was hoping the list could help me. I'll go with the standard example from the help documentation, as my problem is much larger but no more complicated than that. My question is, why is there one latent

The names are dropped to save memory when a release build of the compiler is being used. This is what you probably want on a release compiler you intend to ship since it should be faster. The NDEBUG check is an easy way to tell the difference between release and debug builds. People probably don't want to have to remember to set an additional cmake option to make a release compiler faster.

I like my LLVM IR text to have nice value names, e.g. %add = add ... %mul = mul ... And this all works well if the build has asserts enabled. If the build does not have asserts enabled, it's not so nice: %1 = add ... %2 = mul ... I understand the use for obfuscating names, but the choice to make this dependent on whether or not asserts are enabled seems odd to me. At the very least

Hi, For my input file I think that llvm-as is encoding an instruction incorrectly. Is there any way to dump the numerical representation of input textual LLVM IR on terminal? "-f" option to llvm-as did not help. -- *Disclaimer: Views, concerns, thoughts, questions, ideas expressed in this mail are of my own and my employer has no take in it. * Thank You. Madhur D. Amilkanthwar

On 7/1/20 2:06 PM, Michael Kruse wrote: > Am Mi., 1. Juli 2020 um 11:37 Uhr schrieb Hal Finkel <hfinkel at anl.gov>: >> We can have different printing modes. There can be a more-human-friendly mode and a more-FileCheck-friendly mode. Or modes customized for different kinds of tests. I agree, however, that this does not solve the fragility problems with CHECK-NOT. > This would be

On Tue, Apr 10, 2018 at 5:33 PM Jake Ehrlich via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Benifits of TBD: > 1) It's human readable and diffs on TBDs correspond to changes in the ABI. > Diffs can be automatically added to review processes to ensure that changes > to the ABI are reviewed. The TBDs also document your precise ABI. > 2) The size is smaller which means

2017-06-07 10:19 GMT-07:00 David Blaikie <dblaikie at gmail.com>: > > > On Wed, Jun 7, 2017 at 10:01 AM Mehdi AMINI <joker.eph at gmail.com> wrote: > >> 2017-06-07 9:44 GMT-07:00 David Blaikie <dblaikie at gmail.com>: >> >>> >>> >>> On Tue, Jun 6, 2017 at 2:21 PM Mehdi AMINI <joker.eph at gmail.com> wrote: >>>

Is there some simple textual frontend to the ManageSieve protocol somewhat easier to use than gnutls-cli? I.e. something to use like managesieve -u ef putscript myscript < /tmp/myscript Password: managesieve -u ef setactive myscript Password: simply doing the TLS authentication and length computation for me.

R Help Forum Is there a R library (or a way) that I can extract unique character strings, or repeating patterns in textual strings. Say for example I have the following records: Abc_1234_kjhksh_276 Abc Abc_1234_lakdofyo_324 Bce_876_skdhk_*&^%*& Bce Bce_454 And I would like to see the following results Abc Abc_1234 Bce Jeff Reichman [[alternative HTML version

Is there going to be a formal interface/API for this version-block information? I have had to "extend" the IR and bitcode representations several times to address absences/limitations in the handling of various vector types, in particular FP16 vector types; and it would be really useful if I had a "standard" way of doing this, and identifying that my dialect was different.

New patches with review feedback incorporated: * Changed single letter flags to short abbreviations ('S' ==> 'nsz') * Indentation fixes * Comments don't state function names -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-Fast-math-flags-added-to-FPMathOperator.patch Type: application/octet-stream Size: 4937 bytes Desc: not

Le 2 juin 2010 à 12:21, Eli Friedman a écrit : > On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote: >> Hi, >> >> We need to generate "Floating point constants" in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special encoding rules to be handled by LLVM later one (hexadecimal coding...) >>

While I understand the value of turning it off, it is somewhat annoying when you're trying to run a clang -S -emit-llvm to discover that you're not getting any value names. I would suggest that, irrespective of the kind of build you use, -S -emit-llvm should cause the value names to be defaulted to on as a principle of least surprise to the user. -----Original Message----- From: llvm-dev

Trying to apply patches.. What's your base revision? Joe On Nov 15, 2012, at 5:44 PM, Michael Ilseman <milseman at apple.com> wrote: > New patches with review feedback incorporated: > * Changed single letter flags to short abbreviations ('S' ==> 'nsz') > * Indentation fixes > * Comments don't state function names > >

On Nov 15, 2012, at 10:38 AM, Evan Cheng <evan.cheng at apple.com> wrote: > Hi Michael, > > The patch looks good in general. But I'm a bit concerned about the textural representation about these flags. 'N', 'I', 'S', 'R', 'A' seem cryptic to me. Does it make sense to expand them a bit 'nnan', 'inf', etc.? They definitely

Are you saying the textual form of IR can change, but bitcode doesn't? I don't know what you mean by assembly syntax. Is there a changlog entry when the textual IR changes? On Sat, Mar 14, 2015 at 5:22 AM, Jeremy Lakeman <Jeremy.Lakeman at gmail.com> wrote: > Assembly syntax can and will break between versions. But bitcode should > generally be upgradeable, or a bug should