search for: volkmar

Displaying 11 results from an estimated 11 matches for "volkmar".

2008 Apr 07
2
"\0" gives no warning "unknown escape sequence" (PR#11107)
Full_Name: Volkmar Klatt Version: 2.6.2 OS: linux Submission from: (NULL) (84.147.0.178) Hello, the documentation article ?Quotes from package:base could be improved by discussing the meaning of "\0" escape sequence. In R (currently used: R-2.6.2), a "\0" in a string will silently terminate th...
2008 Apr 09
0
"\0" gives no warning "unknown escape sequence" (PR#11117)
...your subject line: such as warning would be misleading in the extreme. What is done with \0 is not explained on that help page, but then neither is what is done with \b or \t -- it is not the parser reference manual. (There is one, and that is where the semantics should be.) On Mon, 7 Apr 2008, volkmar.klatt at bnv-bamberg.de wrote: > Full_Name: Volkmar Klatt > Version: 2.6.2 > OS: linux > Submission from: (NULL) (84.147.0.178) > > > Hello, > > the documentation article > ?Quotes > from package:base could be improved by discussing > the meaning of "\0&quo...
2006 Dec 14
23
Using DTrace to monitor productions systems
Hi, we are developing and operating an very critical application in the financial sector. Now our customer wants us to report performance data (roundtrip times of the messages routed). My idea is using dtrace to measure the times with the pid provider catching the timestamps on entry of the in and out functions of the processes. Now my questions ;-): 1) Is this an appropriate method to monitor
2003 Oct 09
1
Recursive indexing can cause R-1.8.0 (and R-1.7.1) to segment fault (PR#4486)
...to PR#3324) Recursive indexing can cause R-1.8.0 / R-1.7.1 / R-1.7.0 (operating system: linux, compiler: gcc 3.3.1 or 2.95.3) to produce a segment fault. Suppose we have the following code: (be aware: it crashes R!) ################################################################### # R code from Volkmar Klatt, email: volkmar.klatt AT stud.uni-bayreuth.de # just make a nested list: erzeugeTestListe <- function( laenge ) { Liste <- list() for (i in 1: laenge ) { hilf <- round(runif(1)*20) +1 X <- runif( hilf ) Y <- runif( hilf )^2 summeX <- sum(X) summeY <-...
2017 Feb 03
3
Clang 5.0 support for armv8 64 bit with neon and auto vectorization
...www.bosch.com<http://www.bosch.com/> Tel. +49(711)811-47379 | Fax +49(711)811-0 | Zeeshan.Haider at de.bosch.com<mailto:Zeeshan.Haider at de.bosch.com> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner, Dr. Stefan Asenkerschbaumer, Dr. Rolf Bulander, Dr. Stefan Hartung, Dr. Markus Heyn, Dr. Dirk Hoheisel, Christoph Kübel, Uwe Raschke, Dr. Werner Struth, Peter Tyroller -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-d...
2017 Feb 03
2
Clang 5.0 support for armv8 64 bit with neon and auto vectorization
...CC/ESM1) Robert Bosch GmbH | Postfach 16 61 | 71226 Leonberg | GERMANY | www.bosch.com Tel. +49(711)811-47379 | Fax +49(711)811-0 | Zeeshan.Haider at de.bosch.com Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner, Dr. Stefan Asenkerschbaumer, Dr. Rolf Bulander, Dr. Stefan Hartung, Dr. Markus Heyn, Dr. Dirk Hoheisel, Christoph Kübel, Uwe Raschke, Dr. Werner Struth, Peter Tyroller -----Original Message----- From: Tim Northover [mailto:t.p.northover at gmail.com] Sent: Freitag, 3. Februar 2017 16:02...
2003 Sep 25
2
Bugs compiling R-1.7.1 with Intel compilers icc and ifc (PR#4295)
..."nlm(function(x) fdd(x[1], x[2]), c(-1.2, 1), hessian = TRUE)" (compared with an R-1.7.1, build with gcc 3.3.1 on the same machine, no special configure options) I'll give only an extract of the compiler warnings. There are many more warnings, of course. Feel free to contact me, Volkmar Klatt volkmar.klatt AT stud.uni-bayreuth.de or CanisMaior AT web.de -------------------- * Most warnings are harmless and derives from the gcc compiling flag '-mieee-fp', that icc and ifc dont't understand. This flag is hard coded in the configure.ac file, and it seems that one c...
2007 Apr 18
3
[RFC, PATCH 4/24] i386 Vmi inline implementation
...compatibility. In particular, a method to convert machine to physical mappings in PTEs is one missing interface, and with that and some other rather small changes, a VMI kernel is perfectly capable of running in a Xen hypervisor. Many thanks to Joshua LeVasseur at the University of Karlsruhe, and Volkmar Uhlig, now at IBM, who verified this claim on a slightly different form of the interface. We are actively working on assembling all of those bits together right now to work on the Xen 3.0 interface. The end result is that the exact same kernel binary can run on native hardware as well as multiple...
2007 Apr 18
3
[RFC, PATCH 4/24] i386 Vmi inline implementation
...compatibility. In particular, a method to convert machine to physical mappings in PTEs is one missing interface, and with that and some other rather small changes, a VMI kernel is perfectly capable of running in a Xen hypervisor. Many thanks to Joshua LeVasseur at the University of Karlsruhe, and Volkmar Uhlig, now at IBM, who verified this claim on a slightly different form of the interface. We are actively working on assembling all of those bits together right now to work on the Xen 3.0 interface. The end result is that the exact same kernel binary can run on native hardware as well as multiple...
2007 Apr 18
7
[RFC, PATCH 5/24] i386 Vmi code patching
The VMI ROM detection and code patching mechanism is illustrated in setup.c. There ROM is a binary block published by the hypervisor, and and there are certainly implications of this. ROMs certainly have a history of being proprietary, very differently licensed pieces of software, and mostly under non-free licenses. Before jumping to the conclusion that this is a bad thing, let us consider more
2007 Apr 18
7
[RFC, PATCH 5/24] i386 Vmi code patching
The VMI ROM detection and code patching mechanism is illustrated in setup.c. There ROM is a binary block published by the hypervisor, and and there are certainly implications of this. ROMs certainly have a history of being proprietary, very differently licensed pieces of software, and mostly under non-free licenses. Before jumping to the conclusion that this is a bad thing, let us consider more