search for: strenuously

I'll be skimming the PRs to see if there are any really critical regressions, but so far it looks pretty good. If you are actively disabling the new vector shuffling and have some PR that blocks you, please reply here. Later this week, the flag will go away unless I hear strenuous objections. There is a really staggering amount of cleanup and tidying that needs to take place and can't

The Aspire One is one of those netbooks that have become so popular recently. I've installed CentOS on the hard drive model, and have been considering doing a wiki article about it, and probably will unless there are strenuous objections. The objections might come from the fact that outside drivers are required for wireless, webcam, sound, and even wired ethernet. I have an article on my

On Sun, Jan 4, 2015 at 3:20 PM, Simon Pilgrim <llvm-dev at redking.me.uk> wrote: > On 24 Nov 2014, at 17:53, Chandler Carruth <chandlerc at gmail.com> wrote: > > > I'll be skimming the PRs to see if there are any really critical > regressions, but so far it looks pretty good. > > > > If you are actively disabling the new vector shuffling and have some PR

Hi all, I have just received the following e-mail from an Asterisk user: "I just made a call via BT to a mobile. Then an incoming call came in and Ann else answered it - it made my call go completely fuzzy and I could hear what the woman on the other line was saying to Ann but I couldn't hear my conversation! When Ann's call finished - mine went even fuzzier and all I could hear

...iles. In particular, some people were arguing that if we output a .o file, that it should only contain native code. This means that these two commands would do very different things: llvmgcc x.c -o x.o # compile to native .o llvmgcc x.c -o x.bc # compile to bytecode I have to say that I *strenuously* object to this behavior. In particular, this would require all users to change their makefiles to get IPO/lifelong optzn support from LLVM, violating one of the main goals of the system. There are a couple of things that people brought up (including wrapping .bc files in ELF sections, generating...

Hi all, Just wanted to let you know that I''ve got a working implementation of win32-pathname checked into CVS at the moment. There are both C and pure Ruby versions, but at the moment, the pure Ruby version has a richer API. This is a version of the Pathname class specially tailored for Win32 platforms, with a few extra methods, and proper handling of paths on Win32, including UNC

Hi all, I''m in the process of building a home server with OpenSolaris 2009.06. It''s main function is to serve files (hence using OpenSolaris for some ZFS goodness), but I want to host some Windows x64 VMs on it as well. Given that there are currently no x64 Windows drivers for xVM, I was thinking of starting with VirtualBox (which does have x64 Windows drivers), and then

Is there already a way to read directly from the disk, perhaps via INT22/19h, using the COM32 open()/read() functions? If not, I'd like to propose adding the ability to do something like: int fd = open("//", O_RDONLY); to allow reading from the raw disk. I am working on building a COM32 module out of the checkisomd5 tool from isomd5sum, but I need a way to access the raw disk in

...native translation caching, we will just emit .so files eventually. It is no easier to attach a .so file to an existing ELF binary than it is to attach it to a .bc file. Also, we probably *don't* want to attach the cached translations to the executables, though I'm sure some will disagree strenuously with me :) In any case, this is still a way out. > o Optimization options > > I agree with the idea of using -O<number> for increasing levels of > optimization, with -O0 meaning no optimization. It's a pretty intuitive > scheme, and many Makefiles that use GCC use the -O...

I'm new to libtheora and video encoding in general, but I have worked hard to educate myself in the basics. I've working in image processing for many years, so I'm not starting entirely from scratch. I'm having an encoding problem and I'm looking for helpful suggestions. I'm using a very recent build of ffmpeg 0.6 to encode some image frames (+ audio) into

...llowed to do so with. The problem comes in when the user unmounts the share, then tries to remount it with the same krb ticket. Essentially, the client then tries to auth as "nobody". The only way to fix this is to do a kdestroy on the client and get a fresh ticket. Being told VERY strenuously that this wasn't a krb problem, I started digging in the samba HOW-TO docs and found this, in a section talking about the differences between "security = share, user, domain, server" ...etc: ? Why does server_validate() simply give up rather than re-establish its connection t...

...caching, we will just emit .so files eventually. > It is no easier to attach a .so file to an existing ELF binary than it is > to attach it to a .bc file. Also, we probably *don't* want to attach the > cached translations to the executables, though I'm sure some will disagree > strenuously with me :) In any case, this is still a way out. > > >>o Optimization options >> >>I agree with the idea of using -O<number> for increasing levels of >>optimization, with -O0 meaning no optimization. It's a pretty intuitive >>scheme, and many Makefi...

Hello I was wondering why there doesn't seem to a Windows version of Zaptel, making the Digium and its clones unavailable for a Windows PBX. Is the Zaptel/Zapata combo too *nix-centric? Thanks.

> On Jan 4, 2015, at 4:25 PM, Simon Pilgrim <llvm-dev at redking.me.uk> wrote: > > > On 4 Jan 2015, at 23:30, Chandler Carruth <chandlerc at gmail.com <mailto:chandlerc at gmail.com>> wrote: > >> On Sun, Jan 4, 2015 at 3:20 PM, Simon Pilgrim <llvm-dev at redking.me.uk <mailto:llvm-dev at redking.me.uk>> wrote: >> On 24 Nov 2014, at 17:53,

hi, I received this e-mail which contains a "ballad", at first I thought it was junk mail, but then I read through it, for the EE members of this list, it may be quite humorous. I don't know if the ballad is original, but at least it's the XMAS season, so it's something to lighten up your day, eh? -samudra """ How the Ground Loop Stole Christmas

sample report data that i want to forecast quarter quarter_index Revenue 2007 Q1 1 $3,856,799 2007 Q2 2 $4,243,328 2007 Q3 3 $4,930,369 2007 Q4 4 $5,443,579 2008 Q1 5 $5,164,830 2008 Q2 6 $5,104,413 2008 Q3 7

...e less stressful and less dangerous > *for an outside party* than engineering and maintaining a compatibility > library. That's as may be, but (a) I don't have to keep track of *either* OpenSSL or LibreSSL updates right now in general, (b) our distribution policy is generally that we strenuously avoid using bundled copies of code. Fedora has the same policy, and so far has opted to ship a ~3600-line patch to OpenSSH to use the 1.1 API. That patch will surely get substantially smaller once they're on 7.6p1 and can drop all the protocol 1 bits, but even so, I *really* dislike the option...

LLVMers, As part of my work on bug 353: Create Front End Framework And Compiler Driver (http://llvm.cs.uiuc.edu/PR353), I'm starting a discussion on the design and requirements of the compiler driver. If you have comments on this, by all means PLEASE chime in. This is by no means cast in stone. The results of the ensuing discussion will be documented in PR353 (and elsewhere) and I'll use

...> arguing that if we output a .o file, that it should only contain native > code. This means that these two commands would do very different > things: > > llvmgcc x.c -o x.o # compile to native .o > llvmgcc x.c -o x.bc # compile to bytecode > > I have to say that I *strenuously* object to this behavior. In > particular, this would require all users to change their makefiles to > get > IPO/lifelong optzn support from LLVM, violating one of the main goals > of > the system. > > There are a couple of things that people brought up (including wrapping &...

Olly and I have been discussing details of our policy for deprecating features, and we thought it would be useful to canvas users opinions on a particular aspect. From time to time, we remove features from the library (usually because we have a better replacement). To make life easier for users, we've been following a deprecation policy, so that users are given plenty of warning of