Displaying 20 results from an estimated 64 matches for "unwarrented".
Did you mean:
unwarranted
2010 Oct 30
0
[LLVMdev] Running "make check" on Windows yields lots of unwarrented unexpected failures
<body bgcolor="#ffffff" background="https://img.web.de/v/p.gif" class="bgRepeatYes" style="background-repeat: repeat; background-color: rgb(255, 255, 255); color: rgb(0, 0, 0); font-family: verdana,geneva; font-size: 9pt; padding-left: 0px;"><div style="min-height: 200px; background-image: url(https://img.web.de/v/p.gif); background-repeat:
2010 Oct 31
0
[LLVMdev] Running "make check" on Windows yields lots of unwarrented unexpected failures (HTML free this time:-)
Dirk,
I am working on tests/win32(s) too.
I can let all tests pass on msvc10 and cygming with my patches,
thought, my patches are incomplete (several of them hide potential problems)
Please see threads below in llvm-commits.
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20100927/109077.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20101004/109271.html
If you are
2010 Oct 31
2
[LLVMdev] Running "make check" on Windows yields lots of unwarrented unexpected failures (HTML free this time:-)
Hi,
sorry, in my last mail, I didn't check in time that HTML e-mails would
be turned off.
So, checking out llvm/clang yesterday under Win32, building it, and
running the "check"-project using MS Visual Studio yielded 177
unexpected failures, many of which happen because of the different
registers used in passing arguments under Win64 and everybody else
on x86-64.
I would be
2006 Nov 10
3
unwarranted warning from hist.default (PR#9356)
> x = rnorm(100)
> b = seq(min(x) - 1, max(x) + 1, length = 11)
> b
[1] -3.4038769 -2.7451072 -2.0863375 -1.4275678 -0.7687980 -0.1100283
[7] 0.5487414 1.2075111 1.8662808 2.5250506 3.1838203
>
> invisible(hist(x, breaks = b, include.lowest = TRUE, plot = FALSE))
Warning message:
argument 'include.lowest' is not made use of in: hist.default(x,
breaks = b,
2019 Jun 19
5
[RFC] Documentation clarification: Phabricator, not the lists is the main entry point for new patches
The current documentation talks about both the Phabricator review, and review
as mail replies on -commits lists. It also talks about submitting
patches to lists,
with the subtext that it may be friendlier for outsiders.
It is true that Phabricator has some entry threshold, larger than
github, or maillists,
so the attempt is not unwarranted. But from what i can tell, 99.9% patches go
via
2015 Jan 29
7
[LLVMdev] Adding PDB support to lib\DebugInfo
I've been working on adding pdb reading support to llvm. This started as a
tool for dumping info from a pdb (similar to llvm-dwarfdump), which has
been checked in and currently has limited support for dumping pdb.
There's still more to be done on the pdb dumping tool, but at this point --
to reduce duplicated effort -- I think it makes the most sense to start
moving some of this logic
2007 Aug 31
1
gsub warning message
Hi.
I am using R 2.5.1 on a Windows XP machine. Here is an example of a piece
of code I was running in older versions of R on the same machine. I am
looking for underscores and replacing them with periods. This result is
from R 2.4.1:
>gsub ( "\\_+","\.","AAA_I")
[1] "AAA.I"
>
Here is what I get in R 2.5.1:
>gsub (
2004 Oct 02
1
Bug#270019: 270018, 270019 should remain open
I object to the closing of these bugs on all of the following grounds:
1. They are wishlist items, and the wish has not been resolved, simply
dismissed.
2. They are closed on the grounds that the messages are startup
messages. Some are, but some are not.
3. The suggestion that startup messages should not be filtered out
seems unwarranted.
4. I responded to earlier requests for exact log lines,
2015 Jan 29
0
[LLVMdev] Adding PDB support to lib\DebugInfo
On Thu Jan 29 2015 at 10:22:17 AM Zachary Turner <zturner at google.com> wrote:
> I've been working on adding pdb reading support to llvm. This started as
> a tool for dumping info from a pdb (similar to llvm-dwarfdump), which has
> been checked in and currently has limited support for dumping pdb.
>
> There's still more to be done on the pdb dumping tool, but at
2019 Jun 19
2
[RFC] Documentation clarification: Phabricator, not the lists is the main entry point for new patches
On 6/19/19 12:50 PM, Reid Kleckner via llvm-dev wrote:
I believe the history is that when Phab was initially introduced, we wrote the documentation this way to make things easy for reviewers who didn't want to change their workflow. But, I agree with your observations. The majority of code review seems to happen on Phabricator, and the best way to get traction on a new patch is to upload it to
2010 Jul 02
3
Attributes of 1st argument in ...
R-Devel:
I am trying to get an attribute of the first argument in a call to a
function whose formal arguments consist of dots only and do something, e.g.,
call 'cbind', based on the attribute
f<- function(...) {get first attribute; maybe or maybe not call 'cbind'}
I thought of (ignoring "deparse.level" for the moment)
f<-function(...) {x <-
2015 Jan 29
2
[LLVMdev] Adding PDB support to lib\DebugInfo
See my earlier response to Adrian. But I'll rehash the point here, which
is that basically in the short term, I think it makes the most sense to
keep them separate. In the future, if / when we decide to provide a
unified interface (e.g libDebugInfo as you suggest), there will be
additional machinery required to wrap the two interfaces, so we could move
the DIContext class at that time.
Does
2015 Jan 29
0
[LLVMdev] Adding PDB support to lib\DebugInfo
> On Jan 29, 2015, at 10:20 AM, Zachary Turner <zturner at google.com> wrote:
>
> I've been working on adding pdb reading support to llvm. This started as a tool for dumping info from a pdb (similar to llvm-dwarfdump), which has been checked in and currently has limited support for dumping pdb.
>
> There's still more to be done on the pdb dumping tool, but at this
2015 Jan 29
0
[LLVMdev] Adding PDB support to lib\DebugInfo
>The pdb reading code relies *very heavily* on Windows APIs
can you make shure not to have any windows api stuff in the pdb-reader interface
so its easy to - if someone wants to - implement an windows-api independent version (support reading under linux etc.)
because the pdb format needs to be analysed anyway for writing pdb information on compile/link (in the future)
Am 29.01.2015 um 19:20
2017 Jun 21
2
[LLD][COFF] Zero linker-version header field breaks Authenticode on Windows 7
Hello llvm-dev,
I've recently been using clang-cl and lld-link to build Windows PE executables, which I then code-sign with Authenticode. I've found that although the resulting signed executables seem to validate successfully on Windows 10, they don't on Windows 7: right-clicking on one and bringing up the Windows Properties dialog shows either no 'Digital Signatures' tab at
2019 Apr 24
1
Bug in "stats4" package - "confint" method
Dear R developers,
I noticed a bug in the stats4 package, specifically in the confint method applied to ?mle? objects.
In particular, when some ?fixed? parameters define the log likelihood, these parameters are stored within the mle object but they are not used by the ?confint" method, which retrieves their value from the global environment (whenever they still exist).
Sample code:
>
2015 Jan 29
0
[LLVMdev] Adding PDB support to lib\DebugInfo
> On Jan 29, 2015, at 11:08 AM, Zachary Turner <zturner at google.com> wrote:
>
> See my earlier response to Adrian. But I'll rehash the point here, which is that basically in the short term, I think it makes the most sense to keep them separate. In the future, if / when we decide to provide a unified interface (e.g libDebugInfo as you suggest), there will be additional
2015 Jan 29
2
[LLVMdev] Adding PDB support to lib\DebugInfo
> On Jan 29, 2015, at 10:24 AM, Eric Christopher <echristo at gmail.com> wrote:
>
>
>
> On Thu Jan 29 2015 at 10:22:17 AM Zachary Turner <zturner at google.com <mailto:zturner at google.com>> wrote:
> I've been working on adding pdb reading support to llvm. This started as a tool for dumping info from a pdb (similar to llvm-dwarfdump), which has been
2005 May 05
2
CNAM lookup: new method for Caller ID Name delivery
[cross-posted to -biz and -users since it could fall into either category]
Interesting new product that has been introduced that I think some
would be interested in here (at least, those users in the United
States and perhaps Canada): CNAM delivery via IP lookup.
The problem: inbound calls on many PRI connections, and also over
many VoIP providers, do not include caller name. This means that
2006 Feb 07
2
Browser Detection
How can I detect the user''s browser in Rails?
Thanks.