search for: misconstrue

Either you're being disingenuous are truly looking to confuse a situation only someone ignorant of what LLVM could ever misconstrue. Why would Apple dump hundreds of millions in R&D with Clang/LLVM, create Swift and introduce it to everyone and the press for WWDC 2014, followed up by posting on the LLVM list only to be moving away from LLVM? More importantly, who appointed you e-mail monitor on what is or is not appro...

...uot;..." in the first place? Surely it's better to define the function as function(x,ylim=default,...) within which you do your special ylim stuff, then call plot(x, ylim=ylim,...))?? Can anyone come up with a good reason not to follow that principle? I think my earlier post may have been misconstrued: I'm not saying "never write functions that use ...", I'm just saying "never write functions that depend on a particular argument being passed via ...". Simon Fear Senior Statistician Syne qua non Ltd Tel: +44 (0) 1379 644449 Fax: +44 (0) 1379 644445 email: Simon.F...

On Fri, Jul 27, 2012 at 2:37 PM, Michael Gottesman <mgottesman at apple.com> wrote: ... > I have actually timed said instructions in the past and reproduced Agner > Fog's results. I just prefer to speak by referring to facts that can not be > misconstrued as hearsay = ). That would be great. Also, can you point me to the Agner Fog table that you are referring to? Thanks.

Don't want the opening line of my post to be misconstrued. "Anyone familiar with the BrookTrout TR1034 Fax Board, supports T.38 and PSTN fax in an Asterisk environment?" That's a question, not a statement. Curious if anyone has played with one of these as an extension of an Asterisk server for T.38 faxing, did not mean to imply it could,...

I have a number simple R functions written for the biologists I work with. These functions will evolve, and the documentation will get steadily better. I hope to put them in a package on a local webserver, along with lots of help files, so that the users can easily update their installation. The functions are pure R, with no compiled code, but alias, I cannot figure out how to build this

...awyer wrote an article for LinuxInsider criticizing the GPL. PJ rebuts the article in http://www.groklaw.net/article.php?story=2004072110004290 One thing to realize about legal discussions of the GPL is that the whole concept is so foreign to the typical corporate lawyer that they frequently misconstrue it, as you will see in PJ's comments about the article. Also, some proprietary software companies have taken to spreading FUD (Fear, Uncertainty, and Doubt) about the GPL and many people take such material at face value.

I was misconstrued as having insulted Minister Mentor Lee Kuan Yew. My words were twisted and misinterpreted and I feel that there is a need to explain myself and set the record straight. [b]What really happened[/b] It was sometime in Aug/Sep in the year 2009. The setting was in the Tampines Central office of A...

...cache, this savings may be enough to keep the other cores more busy. Not to mention the stack space saved. But, I cannot say for sure right now. I have actually timed said instructions in the past and reproduced Agner Fog's results. I just prefer to speak by referring to facts that can not be misconstrued as hearsay = ). But if you don't believe me, time the instructions yourself (its an important thing to have in your toolbox anyways since sometimes Intel's documentation can be non-specific). I have a small instruction timing project lying around somewhere, if you want it I can send it t...

...nform the location of arguments. > Agreed. My concern is mostly about naming and documentation of intended usages. Speaking as someone who's likely to be using this in the very near future, I'd like to make sure I understand how you intend it to be used. The last thing I want to do is misconstrue your intent and become reliant on a quirk of the implementation you later want to change. I don't think the intrinsic names will be able to capture their semantics. I think that's why we need documentation, which I've been working on: http://llvm-reviews.chandlerc.com/D1981. For examp...

I think this entire conversation is going a bit off the rails. Let's try to stay focused on the specific request, and why there (may) be problems with it. On Sun, Apr 7, 2013 at 11:50 AM, Cameron McInally <cameron.mcinally at nyu.edu>wrote: > To be clear, you're asking to turn off a set of optimizations. That >> is, you're asking to make code in general run slower, so

...leased tarballs over my and other developers objections. > Everytime this has been do we have been 'tared and feathered' and > quite rightly so. Unfortunately each new manager needs to learn > this lesson. Perhaps not, but it seems that in the age of social coding and IRC one can misconstrue the allowance to make other changes to changing the tarball. For that reason I agree, it should be spelled out in bold letters at the end of the document, once we are done *do not change the tarballs!*. > > Yes it would be nice to get feedback that something broke on some > platform befo...

...eing used to stop the output when we've temporarily run out of input, which is fine. But the SAME eos flag is used to stop the outer loop. I feel that either eos should be reset after the inner loop, or that there should be a separate eos-like flag used for the inner loop. Am I right of havs I misconstrued things. Certainly when I' getting short track rips: - the input raw data is _not_ all consumed - oggenc exits "normally", with a "Done encoding file message" just like it"s seen end of input I'm off to rebuild oggenc to test this theory...

Hey again, Thank you for your opinions. I will take them into consideration. A few comments... On Sun, Apr 7, 2013 at 1:39 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: ... > If the performance penalty is unclear to you, that means you haven't > measured it. Until you measure, you have absolutely no business > complaining about a potential performance problem. Measure,

Dear All, Historically, we *have* permitted job announcements for jobs that require or desire expertise with LLVM or one of it's sub-projects. To the best of my knowledge, we've never required that the position announcement state that the job will contribute directly to the LLVM project (or its sub-projects) or that the code created by the position be open source. As an example,

...broadcasters and their competition. Granted, broadcasters get their own statistics with more detail than just a simple number - so the information is still there - but I think it's a bit of a stretch to go as far as to say that the number is irrelevant, rather, it's relevance has been misconstrued to mean other things. My personal reason for paying attention to this statistic when faced with thousands of possible streams is that I am looking for music of a specific genre and stand a better chance of landing in a stream that actually falls in to that category when it's being listene...

...>> Agreed. My concern is mostly about naming and documentation of >> intended usages. Speaking as someone who's likely to be using this in >> the very near future, I'd like to make sure I understand how you >> intend it to be used. The last thing I want to do is misconstrue >> your intent and become reliant on a quirk of the implementation you >> later want to change. > > I don't think the intrinsic names will be able to capture their > semantics. I think that's why we need documentation, which I've been > working on: http://llv...

Hello everybody. I've been learning R for about a month to do a econometric study and now i'm stuck with some problems to make R do the things I want. Here I give the list of things I wanna do from the most simple to the more complex (for me of course): 1. Make a log. I've been using Stata and there i have a great tool to register what the program do: the log file, wich it's a

In some cases we do want to make the decision based on the target. For Hexagon, we don't support GDB anymore, only LLDB, so we always want LLDB tuning. The clang driver should have a way to specify that. -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -----Original Message----- From:

Hey Michael, Thanks for the legwork! It appears that the stats you listed are for movaps [SSE], not vmovaps [AVX]. I would *assume* that vmovaps(m128) is closer to vmovaps(m256), since they are both AVX instructions. Although, yes, I agree that this is not clear from Agner's report. Please correct me if I am misunderstanding. As I am sure you are aware, we cannot use SSE (movaps)

Well put, Chandler! On Sun, Apr 7, 2013 at 6:23 PM, Chandler Carruth <chandlerc at google.com>wrote: > I think this entire conversation is going a bit off the rails. Let's try > to stay focused on the specific request, and why there (may) be problems > with it. > > On Sun, Apr 7, 2013 at 11:50 AM, Cameron McInally < > cameron.mcinally at nyu.edu> wrote: >