search for: l23

Displaying 17 results from an estimated 17 matches for "l23".

Did you mean: 23
2000 Mar 31
1
R: one bananna aov() question
...0 L13 5 3.94067233590221 11 L16 7 1.68130480999203 12 L17 8 -1.31869519000797 13 L18 9 -2.05932766409779 14 L19 10 2.44067233590221 15 L21 13 -1.66682168482594 16 L22 14 0.0925458410842417 17 L23 15 -2.90745415891576 18 L28 19 1.09254584108424 19 L29 20 -1.90745415891576 20 L1 1 2.36694915254237 21 L2 11 -3.56101694915254 22 L3 21 3.36694915254237 23 L4 23 2.43898305084746 24 L5...
2019 Jul 23
2
RFC: changing variable naming rules in LLVM codebase & git-blame
...evant git blame documentation change: https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/blame-options.txt#L113-L125 Relevant git config documentation change: https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/config/blame.txt#L23-L28 -----Original Message----- From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Peter Waller via llvm-dev Sent: Tuesday, July 23, 2019 11:25 To: llvm-dev at lists.llvm.org Cc: nd <nd at arm.com> Subject: Re: [llvm-dev] RFC: changing variable naming rules in LLVM codebas...
2015 Mar 17
2
Proposing a change in the base::sink interface for type argument
...Here is the current interface: sink(file=NULL, append=FALSE, type = c("output", "message"), split=FALSE) However, reading the implementation there is implicit assumption that type is a single character value: https://github.com/wch/r-source/blob/trunk/src/library/base/R/sink.R#L23 I'm finding this very confusing as the interface is giving a default value of a character _vector_ causing the illusion that by default both output/message will be redirected. I'm proposing either a change in the interface so it is a single character (either output or message) or a loop i...
2015 Jan 09
2
latex warning
...eg R builds off the CRAN / PPA repos administered by Michael, but for some other libraries it shows its age. One can code around it if one knows how to prepare a matching .deb (cf [1] which I need to document/blog about). Dirk [1] https://github.com/eddelbuettel/rquantlib/blob/master/.travis.yml#L23:L26 -- http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
2015 Jul 06
2
libopus and TI am335x with linphone
Hello, has anyone running a linphone-application on am335x (like beaglebone) with opus codec. My CPU has extreme high load, wenn ist start with opus codec. Is there a possibikity tu optimize f?r this single core ARM? Thanks Helmut Sholz ______________________________ BAYERISCHER RUNDFUNK Rundfunkplatz 1 80335 M?nchen HA IT und Medientechnik Abteilung Systemservice Funkhaus FG Sendungssysteme
2015 Mar 18
1
Proposing a change in the base::sink interface for type argument
...(file=NULL, append=FALSE, type = c("output", "message"), split=FALSE) > > > >However, reading the implementation there is implicit assumption that type > >is a single character value: > >https://github.com/wch/r-source/blob/trunk/src/library/base/R/sink.R#L23 > > > >I'm finding this very confusing as the interface is giving a default value > >of a character _vector_ causing the illusion that by default both > >output/message will be redirected. > > > >I'm proposing either a change in the interface so it is a s...
2015 Mar 18
0
Proposing a change in the base::sink interface for type argument
...rface: > >sink(file=NULL, append=FALSE, type = c("output", "message"), split=FALSE) > >However, reading the implementation there is implicit assumption that type >is a single character value: >https://github.com/wch/r-source/blob/trunk/src/library/base/R/sink.R#L23 > >I'm finding this very confusing as the interface is giving a default value >of a character _vector_ causing the illusion that by default both >output/message will be redirected. > >I'm proposing either a change in the interface so it is a single character >(either ou...
2015 Jul 06
0
libopus and TI am335x with linphone
Hello, you can compile opus with "--enable-fixed-point". That saves a cpu ressources. https://github.com/Studio -Link/PKGBUILDs_clean/blob/master/opus/PKGBUILD#L23 -- nice regards, Sebastian Reimers ------------------------------------------ IT-Service Sebastian Reimers Am blanken Boom 14 32369 Rahden Festnetz: 05776-3930000 Fax-Nummer: 05221-17242088 Skype: miete-admin E-Mail: service at it-sreimers.de Internet: www.it-sreimers.de Internet: www.miete-adm...
2016 Jun 02
4
Minimum RAM requirement for CentOS 6.x graphic installer?
Hi, The title says it all. What's the minimum RAM requirement for the CentOS 6.x graphic installer? In our public libraries we have some old hardware running CentOS 5, and I wonder if some of these machines can be upgraded to CentOS 6. Unfortunately RHEL 5.x' nifty text mode installer got seriously crippled with version 6.x. Cheers, Niki Kovacs -- Microlinux - Solutions informatiques
2017 Jun 06
2
Putting "tied-to" constraints on virtual registers in SelectionDAGISel's Select() method
Hello. I expand an instruction to a sequence of MachineSDNodes at instruction selection, in the Select() method of the SelectionDAGISel class. For efficiency, in order to generate fewer instructions, I would like to assign twice to the same physical register - but since I don't want to "mess" with the register allocator, I am using only virtual registers. However,
2020 Jan 30
2
Writing loop transformations on the right representation is more productive
...close by miles to the in-memory thing your loop hierarchy optimizer would > be using. For eg., here's the input IR and the output IR of a simple outer > loop vectorization performed in MLIR: > > https://github.com/bondhugula/llvm-project/blob/hop/mlir/test/Transforms/vectorize.mlir#L23 > > Again, the proposal is about the in-memory representation using red/green trees (which I firmly disagree with being close to MLIR's in-memory representation), not the textual format. Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://l...
2018 Dec 12
3
PXE boot img for both BIOS and EFI
On Wed, 2018-12-12 at 17:10 -0600, Carl Karsten wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > > While I am here, I want to ask: >
2019 Jul 22
3
RFC: changing variable naming rules in LLVM codebase
> On Jul 18, 2019, at 6:09 PM, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > >> On Jul 18, 2019, at 3:49 PM, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> And one more question: >> >> What is the plan of renaming variables in llvm and clang? Will it be
2018 Aug 29
2
JIT client - late cross references
Hello Alex, This is an interesting approach! Thank you for that! I understand the basic idea but sadly... My skills in handling the IR are not very high, so I can't imagine where and when to replace the calls to b() with the trampoline. The only thing I can handle would be creating that trampoline variable. Also will this approach be a problem for really time critical tasks? Since I replace
2020 Feb 06
2
Why is lldb telling me "variable not available"?
...trating the invocations I used to create each of these, as a gist on GitHub: https://gist.github.com/modocache/670bc38e5a5ea2e0a3d6bafe8ea9c693 I'm looking at lldb's behavior on lines 23-40 of the C++ program, https://gist.github.com/modocache/670bc38e5a5ea2e0a3d6bafe8ea9c693#file-test-cpp-L23-L40, which I’ll paste below: ``` coro foo() { int i = 0; ++i; printf("%d\n", i); // 1 // Breakpoint 1: // (lldb) frame variable i // (int) i = 1 co_await suspend_always(); int j = 0; ++i; ++j; printf("%d, %d\n", i, j); // 2, 1 // Breakpoint 2: //...
2015 Jan 08
2
latex warning
Dear all, I am getting an R CMD check warning about the PDF manual. I am having a hard time finding out what is wrong, here is the log of the Rd2pdf call. The full check (and other) log is at https://api.travis-ci.org/jobs/46373922/log.txt?deansi=true if anybody is interested, and the package itself is here: https://github.com/metacran/r-builder/tree/bintex/rbuildertest Thanks, Best, Gabor
2020 Jan 03
10
Writing loop transformations on the right representation is more productive
In the 2018 LLVM DevMtg [1], I presented some shortcomings of how LLVM optimizes loops. In summary, the biggest issues are (a) the complexity of writing a new loop optimization pass (including needing to deal with a variety of low-level issues, a significant amount of required boilerplate, the difficulty of analysis preservation, etc.), (b) independent optimization heuristics and a fixed pass