Displaying 8 results from an estimated 8 matches for "hjort".
2005 Mar 10
3
two-dimensional integration?
...nsion?
Also, iterated one-dimensional integrations could
be attempted, but I find that messy, also because
things lose the g(many) = many(g) property, and
then R refuses to integrate g.)
(c) Will a thing like the above exist in R before
the Tromsoe Olympics in 2014? For which dimensions?
Nils Lid Hjort
[Professor of statistics at Oslo, but currently at Duke]
2020 Jun 08
2
Nested instruction patterns rejected by GlobalISel when having registers in Defs
...issue I'm having with
our patterns.
Best regards,
Gabriel
_____
From: Daniel Sanders <daniel_l_sanders at apple.com>
Sent: Friday, June 5, 2020 9:02 PM
To: Quentin Colombet <qcolombet at apple.com>
Cc: Dominik Montada <dominik.montada at hightec-rt.com>; Gabriel Hjort Åkerlund
<gabriel.hjort.akerlund at ericsson.com>; llvm-dev at lists.llvm.org
<llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev] Nested instruction patterns rejected by GlobalISel
when having registers in Defs
The implicit defs don't participate much in the patterns. For the...
2020 Jun 04
2
Nested instruction patterns rejected by GlobalISel when having registers in Defs
...as additional results. I am tempted to modify that part of the
code, but maybe Im missing some invariant thats not immediately evident
Cheers,
Gabriel
From: Dominik Montada <dominik.montada at hightec-rt.com>
Sent: den 4 juni 2020 14:51
To: llvm-dev at lists.llvm.org
Cc: Gabriel Hjort Åkerlund <gabriel.hjort.akerlund at ericsson.com>
Subject: Re: [llvm-dev] Nested instruction patterns rejected by GlobalISel
when having registers in Defs
Hi Gabriel,
I'm working on a downstream target which uses GlobalISel and we have many
patterns with instructions that also define...
2020 Jun 04
2
Nested instruction patterns rejected by GlobalISel when having registers in Defs
...So I wonder, how should registers appear in Defs be treated? Are they equal to those appearing in outs, and therefore interchangeable, or is it valid to disambiguate between them and therefore modify TableGen to only consider outs as the result of interest when processing the patterns?
Gabriel Hjort Åkerlund
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200604/91f46c50/attachment.html>
2011 Jul 16
1
How does locpoly (KernSmooth package) estimate densities?
...some trouble understanding how this estimation technique is implemented in R. My main concern comes from the fact that this function gives negative estimates when the bandwidth is sufficiently large (mainly in the tails of distributions). I have read some articles on this technique (C. Loader 1996,Hjort and Jones 1996) but from none have I managed to understand how this is possible.
Could anyone give me some insight on how this function works in R?
Thank you!
Roberto.
[[alternative HTML version deleted]]
2007 Oct 12
1
Differencing data by groups
...for
the second row of data).
I cannot seem to get diff to work the way I want it to - advice appreciated
Tom
Thomas J. Miller, Ph.D.
Professor
Chesapeake Biological Laboratory
University of Maryland Center for Environmental Science
Solomons, MD 20688
Tel: (410) 326-7276
Fax: (410) 326-7318
WWW: hjort.cbl.umces.edu
2020 Aug 03
5
TableGen trace facility
A question for those of you who have developed complex TableGen files: Do you think a trace facility would be useful during debugging? The idea is to add a new statement to TableGen along these lines:
trace tag : value1, value2, ... ;
When encountered, the TableGen parser would display the tag along with the values of the specified value1, value2, etc. The tag is an identifier that makes it
2020 Jun 16
3
Codifying our Brace rules-
I'm with Matt on this one. I much prefer the approach of ALWAYS use braces
for ifs and for loops, even if they're not needed, for basically the same
reasons as he put. The number of times I've added a statement inside an if
without braces and forget to add them is annoyingly high, especially as
it's not always an obvious error upfront. Similarly, being involved in a
downstream