Displaying 20 results from an estimated 1474 matches for "overals".
Did you mean:
overall
2005 Jul 08
1
Overlying a Normal Dist in a Barplot
R-Users,
Hopefully someone can shed some light on these questions as I had
little luck searching the archives (although I probably missed something
in my search due to the search phrase). I estimated multinomial
probabilities for some count data (number successful offspring) ranging
from 0 to 8 (9 possible response categories). I constructed a barplot
(using barplot2) and I want to
2011 Jul 29
2
[LLVMdev] Overly restrictive size argument to llvm.invariant.start
Why is it that @llvm.invariant.start requires the size argument to be a
constant integer literal and does not accept constant expressions? For
example the following IR:
declare {}* @llvm.invariant.start(i64,i8*)
define void @foo() {
%1 = call {}* @llvm.invariant.start(i64 ptrtoint(i8* getelementptr(i8*
%null, i32 1) to i64), i8* null)
ret void
}
gives the following error from llvm-as:
2011 Jul 29
0
[LLVMdev] Overly restrictive size argument to llvm.invariant.start
Geoff Reedy wrote:
> Why is it that @llvm.invariant.start requires the size argument to be a
> constant integer literal and does not accept constant expressions? For
> example the following IR:
>
> declare {}* @llvm.invariant.start(i64,i8*)
> define void @foo() {
> %1 = call {}* @llvm.invariant.start(i64 ptrtoint(i8* getelementptr(i8*
> %null, i32 1) to i64), i8*
2013 Nov 22
2
[LLVMdev] DAGCompiler::MergeConsecutiveStores Question
In DAGCombiner::MergeConsecutiveStores, there is this check:
if (Index->getAlignment() != St->getAlignment())
break;
Apparently this check ensures that all of the stores have the same
alignment. Why is that necessary? This seems very overly restrictive
to me.
-David
2016 Jan 01
0
Fix for CVE-2015-5299 denies access to ZFS snapshots due to overly strict condition checking
On Fri, Jan 01, 2016 at 09:38:09PM +0800, QIU Quan wrote:
> OS platform: FreeBSD 10.1-RELEASE-p25
> Filesystem: ZFS
> Samba version: upgraded from 4.1.17 to 4.1.22
>
> Problem:
>
> I have been using the shadow_copy2 and zfsacl VFS modules to enable
> access control and the Previous Versions feature for Windows clients.
> With /usr/local/etc/smb4.conf configured this
2006 Apr 05
2
Overring hidden_field_tag ?
Hi, I wonder how to override some tag generators, for example the
hidden_field_tag function.
By the way, I would be interested to learn how to extend
ActionView::Base so new functions would be available to all my views
(functions that need _erbout access, so a simple helper doesn''t...help)
Thanks
--
Posted via http://www.ruby-forum.com/.
2001 Nov 01
0
overly light printing HP 8000
Points, axes and axes labels on graphs printed from R are very
light- almost unreadable. I am using the gui interface on the windows
version to print the plot on the screen to an HP 8000 set as a postscript
printer or PCL printer; the postscript output is light and the PCL output
is very light. If I specify lwd =2 in the plot command, the lines are
readable, but the points (open circles, in
2012 Apr 05
1
2.1.3: Overly lax FETCH parsing
These commands both work in Dovecot (as of 2.1.3):
1 UID FETCH 1:* () (CHANGEDSINCE 1)
* 1 FETCH (UID 30097 MODSEQ (19554))
[...]
1 OK Fetch completed.
2 FETCH 1:* () (CHANGEDSINCE 1)
* 2 FETCH (MODSEQ (19554))
[...]
2 OK Fetch completed.
However, RFC 3501 indicates that an empty FETCH attribute list is incorrect:
fetch = "FETCH" SP sequence-set SP ("ALL" /
2012 Mar 07
1
.Internal(inspect(x)) gives overly verbose output for reference classes
Even for an extremely simple instance of a reference class
x <- setRefClass("x")
y <- x$new()
calling the internal inspect function
.Internal(inspect(y))
produces enough output that it takes several minutes to print to the
console.? (Actually I gave up and terminated the command after ~10
mins.? It isn't clear whether the output would eventually complete.)
Are reference
2010 Mar 02
2
Intel: Overly restrictive test for availablility of CPUID masking MSRs?
Hi,
http://xenbits.xensource.com/xen-unstable.hg?rev/aab9fbd6ffa0 from
http://lists.xensource.com/archives/html/xen-devel/2008-07/msg00518.html
restricts the CPUID masking feature to model 0x1d or model 0x17 with
stepping >=4:
if (!((model == 0x1d) || ((model == 0x17) && ((eax & 0xf) >=
4)))) {
/* fail ... */
A Xeon E5520 which is supposed to
2006 Feb 09
6
POLL: Does anyone actually use multiple passdb backends on the same server?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Folks,
We are discussing removing the capability to chaining passdb
backends. It's a decent idea but overly complicates things
IMO and unless it has wide spread use, we'll probably axe it
soon (voting is starting up on the samba-tecnnical ml now).
To give you an example of what I mean, is anyone using
something like:
passdb backend =
2016 Jul 19
6
[Bug 2599] New: Overly verbose partial authentication
https://bugzilla.mindrot.org/show_bug.cgi?id=2599
Bug ID: 2599
Summary: Overly verbose partial authentication
Product: Portable OpenSSH
Version: 7.2p1
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
Assignee: unassigned-bugs at
2011 Nov 02
1
overly long lines in pdf output of manual from package
In re-factoring my optimx package, I'm finding that the pdf output has some lines that are
outside the margins (and there are warnings in R CMD check optimx). Clearly I can fix this
by editing the tex file that is generated, but the build infrastructure would still get
things wrong in automatic processing. So that gives rise to 3 questions:
1) How do I adjust the DESCRIPTION file to avoid too
2013 Feb 19
0
[LLVMdev] [RFC] NoBuiltin Attribute
On Feb 18, 2013, at 4:49 PM, Bill Wendling <wendling at apple.com> wrote:
>> Hi Bill,
>>
>> I think the concept of this patch makes sense, but the implementation does not.
>>
>> I have:
>>
>> void foo() {
>> printf("hello\n");
>> }
>>
>> and I build with -fno-builtin-puts. If I understand correctly, *foo* will
2013 Nov 22
0
[LLVMdev] DAGCompiler::MergeConsecutiveStores Question
Hi David,
You are right. This check is overly restrictive. We can replace this check with code that uses the alignment of the first store.
Thanks,
Nadav
On Nov 22, 2013, at 9:31 AM, dag at cray.com wrote:
> In DAGCombiner::MergeConsecutiveStores, there is this check:
>
> if (Index->getAlignment() != St->getAlignment())
> break;
>
> Apparently this check
2013 Feb 19
2
[LLVMdev] [RFC] NoBuiltin Attribute
On Feb 19, 2013, at 10:18 AM, Chris Lattner <clattner at apple.com> wrote:
> On Feb 18, 2013, at 10:31 PM, Bill Wendling <wendling at apple.com> wrote:
>
>>>>>
>>>>> In the context of LTO, it makes sense for the attribute to be on function bodies, not on prototypes.
>>>>>
>>>> Yeah, I noticed that after sending this
2020 May 08
3
Noncapture use of locals disabling TailRecursionElimination
Hi,
I was looking into the implementation of TailRecursionElimination, and
noticed that we have the constrain that if any call uses a local, even
though it doesn't capture the local, it would still prohibit TCE. This
contain seems unnecessary and overly limiting? Relevant code is here:
2000 Jun 29
3
Overal plot title after mfrow and .Rhistory questions.
Hello everyone,
I had a few questions that I have not been able to figure out despite a lot of
reading.
1) Adding a title to a multiplot figure:
If I plot multiple plots with
>par(mfrow=c(2,6))
how do I add an overall title to the figure, not the individual plots?
2) Saving histories on the fly:
Is there a .Rhistory equivalent to
>save.image()
? I would like to be able to save the
2013 Feb 19
4
[LLVMdev] [RFC] NoBuiltin Attribute
On Feb 18, 2013, at 6:10 PM, Chris Lattner <clattner at apple.com> wrote:
> On Feb 18, 2013, at 4:49 PM, Bill Wendling <wendling at apple.com> wrote:
>>> Hi Bill,
>>>
>>> I think the concept of this patch makes sense, but the implementation does not.
>>>
>>> I have:
>>>
>>> void foo() {
>>>
2013 Feb 19
0
[LLVMdev] [RFC] NoBuiltin Attribute
On Feb 18, 2013, at 10:31 PM, Bill Wendling <wendling at apple.com> wrote:
>>>>
>>>> In the context of LTO, it makes sense for the attribute to be on function bodies, not on prototypes.
>>>>
>>> Yeah, I noticed that after sending this patch. I modified it to check the function CI is in for that attribute.
>>
>> Was that in the