search for: meaty

"Daniels, Marcus G" <mdaniels at lanl.gov> writes: >> "Unfortunately, that does appear to be the case. I think MSVC 2010 is >> a reasonable requirement, but it seems like 2012 is the real target >> for C++11 features." IMO, the only meaty C++11 feature that VS2012 adds over VS2010 is range-based for-loops. > Bah, they can install Mingw binaries. Sure! Actually, I wonder why people care about Visual Studio at all. Not.

...finding out what associations exist from examining the lodel classes themselves or indeed any other way of finding out this information? There''s nothing obvious from looking at the RDOCs and Im poised to delve into the rails source but Id rather not because the association code is pretty meaty. Anyone got any clues? Thanks, -- Dan Webb http://www.danwebb.net

"Unfortunately, that does appear to be the case. I think MSVC 2010 is a reasonable requirement, but it seems like 2012 is the real target for C++11 features." Bah, they can install Mingw binaries. Marcus -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130110/eb78b89f/attachment.html>

I have a custom fact. It syncs correctly, works correctly everywhere when run via ''facter'', and works correctly from puppet on all but one machine. >From ''facter'': # export FACTERLIB=/var/puppet/facts # /opt/puppet/bin/facter itg_location mel But from within puppetd I get: Sep 13 14:54:29 hordac puppetd[768]: [ID 702911 daemon.warning] Could not load fa

Hello, I am trying to build up a pretty meaty Asterisk box after doing our initial testing and playing on a 1ghz system. Right now I have decided on a prebuilt system which I normally don't do but thought it seemed like a good deal. I have included the initial specs below, I will be adding another 1 GB of RAM for a total of 2 GB. My fi...

...me intervals (~3 days is sane); I think the most pings I've seen before an answer is Ping^4 ("Fix cmake for Hexagon cross compilers"), and the reviewers were very apologetic about the situation. Looking back at your submission history, it looks like your patches have been really "meaty" patches; by that I mean that they affect core functionality and need a careful review by one of a small number of people who really understand that part of the code; understandably, these patches are more likely to go unanswered, especially if you haven't gotten a foothold in that part of...

On 30-Apr-09, at 6:38 PM, Dan Gohman wrote: > On Apr 30, 2009, at 3:02 PM, David Greene wrote: >> As I've been going along I've added feature flags for SSE4a and >> SSE5. These >> really do need to be separate feature flags because having SSE4a and/ >> or SSE5 >> does not imply that you have SSE4.2 or SSE4.1. So they can't be >> part of the

I think the main benefit of a scheme like this would be that a pull request tells a code owner which patches require their attention. As a contributor it would be nice to see your patch in a queue somewhere rather than just be buried down the mailing list. When patches are sent to llvm-commits it can be hard to tell if a code owner has noticed the patch because it is a very high-volume list.

...Email Security Appliance(ESA), Security Management Appliance (SMA), Web Security Appliance (WSA)). CPT is responsible for the substrate of the Cisco IronPort product line. We do common hardware, low-level device drivers, user interface APIs, operating system architecture for AsyncOS, and all of the meaty components at the heart of Cisco IronPort's products. CPT is a fast-moving organization that requires a diverse set of skills. We live and breathe FreeBSD, python, and various other technologies. Technology is part of our name! Releasing on a very rapid cadence, CPT QA spends very little time v...

...or Hexagon cross compilers"), and the reviewers were very > apologetic about the situation. The reviewers are *always* very apologetic. That doesn't help the developer, unfortunately. > Looking back at your submission history, it looks like your > patches have been really "meaty" patches; by that I mean that they > affect core functionality and need a careful review by one of a small > number of people who really understand that part of the code; > understandably, these patches are more likely to go unanswered, > especially if you haven't gotten a foot...

...> open an xterm, cd to the setup directory, and > run the setup program from > there this way > > WINEDEBUG=+loaddll wine ThatProgram.exe > > that failing, try with this sort of thing > > WINEDEBUG=+loaddll wine > Z:\\media\\FORDCD\\Setup.exe > > Then you get meaty errors in the xterm, and > give us some of those. > -- > Declan Moriarty <junk_mail@iol.ie> > > This just an FYI. > > > > Yesterday I updated to top of trunk wine and > rebuilt and installed. > > > > I have a Ford Service CD (for 1999 models) >...

...some kind (which won't be until after the rest of the kit all works). I've been reading list archives and the wiki pages for weeks, but now that I'm starting actual implementation, there's a few things that I'm not sure how to go about. So. The questions: 1. Is the K6-2 meaty enough to do function in this enviroment? I don't ever anticipate doing any hefty compression, as this is all in-house (unless I get the remote Altigen box flying, which will add one potential g.723 connection...). Routing calls around between skinny phones and a single PSTN connection sh...

On Tue, Mar 17, 2015 at 6:14 PM, Tim Northover <t.p.northover at gmail.com> wrote: >> As a simplification, the compiler deals almost exclusively in pseudo >> instructions. By x86 analogy, using pseudos to unfold a TEST32rm into >> MOV32rm + TEST32rr means I can skip the complex operand fitting effort >> needed to pick specific machine instructions. There are many

Beta 2 is now available for testing. Problems Corrected since Beta 1: 1) References to the obsolete USE_ACTIONS option have been removed from the manpages. 2) NFLOG has been documented for some time as a valid ACTION in the rules files but support for that action was never implemented until this release. 3) The Checksum Target capability detection in the rules compiler was

Beta 2 is now available for testing. Problems Corrected since Beta 1: 1) References to the obsolete USE_ACTIONS option have been removed from the manpages. 2) NFLOG has been documented for some time as a valid ACTION in the rules files but support for that action was never implemented until this release. 3) The Checksum Target capability detection in the rules compiler was

This just an FYI. Yesterday I updated to top of trunk wine and rebuilt and installed. I have a Ford Service CD (for 1999 models) and wine on the exe does not work (on an old Windows ME laptop it all works). The startup.exe sort of seems to work AFAICT, but when it's done and the app exe started the app exe ( installed on disk) cannot seem to find the cd (the app needs the CD, the install

David A. Green wrote: > I find llvm-commits daunting. So much that I hesitate to do reviews. > As Chris commented, I am not very active on that list. There's a reason > for that beyond lack of time. So the goal is to make it easier for a member of the community to review only commits to a sub-tree that interests them? Let's say it may or may not be easier for reviewers to

Hi, I bougth the Agile Web Development with rails First Edition and now want buy rails recipes but what is the best decision buy rails recipes or the new edition de Agile Web Development With Rails? Jean Carlo Schechnner www.idvirtual.com -------------- next part -------------- An HTML attachment was scrubbed... URL:

Sean Silva <silvas at purdue.edu> writes: >> - I have to *remember* I submitted the patch (not hard, but it is a >> cost). > > If you forgot, the chances are high that the patch was unimportant. I > do my development on local git branches, so every time I do `git > branch`, I'm reminded. There's really no overhead. Every time you have to check it's