search for: terrifying

Whenever I format a flash drive I'm always terrified that I'm going to fat-finger something in the terminal and accidentally blow away a partition on one of my hard drives. *shudder* Is gparted the best gui to handle this task? Or is there something better? I'd really prefer something more limited that just allows me to select whatever it sees as a removable drive and disallows any

I am currently (still) running Fedora 17 --- having not managed to screw my courage to the sticking place and upgrade. Even though we are now up to Fedora 20, I think. The traffic on the Fedora mailing list on the upgrading issue is a bit terrifying. I would just like to confirm that: It is ***NOT*** possible to download a binary of R for Fedora 17. Is this correct? My efforts to obtain a binary using yum install resulted in a binary for version 2.15.2. (Whereas of course the source version available from CRAN is 3.0.1. I just wa...

...nice segue to Swift ! :-), but... The question is what should LLVM do with UB in general, saying that we are going to change one specific idiom from undefined to defined glosses over the real question: why should we ever optimize / delete any UB at all ? This “depressing and faintly terrifying thing” as you call it, should be viewed not as an opportunity for optimization, but rather as the source of bugs that need to be warned about at the very least. The current action is to delete UB (without warning), is that really right ? Who can possibly benefit from this optimization ? And how...

On 02/24/2016 08:10 PM, Duncan P. N. Exon Smith via llvm-dev wrote: >> On 2016-Feb-24, at 19:46, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: >> >> On Wed, Feb 24, 2016 at 7:38 PM, Chandler Carruth <chandlerc at google.com> wrote: >>> On Wed, Feb 24, 2016 at 7:34 PM Duncan P. N. Exon Smith >>> <dexonsmith at apple.com> wrote:

Yea, I'm pretty sad about all of this. I'm also not seeing a lot of awesome paths forward. Here is the least bad strategy I can come up with. Curious if folks think this is sufficient: 1) Stop deducing function attributes within comdats by examining the bodies of the functions (so that we remain free to transform the bodies of functions). 2) Teach frontends to emit (even at O0!!!)

I purchased the cwRsync for windows to help a client backup her USB key after using it. I want the cwRsync_GUI_CLIENT to execute the equivalent of this command: rsync -rave "ssh -p 922" /cygdrive/e user at machine.domain.com:USBKey Can anyone tell me how to do so?? Like most windows users, my client is terrified of the command prompt. Thanks Richard -- LinuxCabal Asociación

> On Jul 6, 2017, at 3:07 PM, Chris Lattner <clattner at nondot.org> wrote: > > >> On Jul 6, 2017, at 2:05 PM, Peter Lawrence via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> >>> On Jul 6, 2017, at 1:00 PM, via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>>

...hive search for this list, so please forgive me if this has been discussed before. Has any thought been given to supporting websockets in the ssh client? I'm talking about solely using a websocket as the transport layer, and leaving the actual protocol intact, as opposed to the (to me, frankly terrifying) idea of allowing a web server to act as an ssh client to a regular sshd and providing a terminal interface. I'm weighing up the pros and cons of this idea in my own mind at the moment, and whilst I like the idea for providing another transport to services such as git-over-ssh, I can't hel...

...ere surrounded by beckoning skeletons, sometimes leading them in a dance to their own graves. ok, thanks for your work man. And, knowing his past success with science, one further imagines that this is the device that will finally destroy New Orleans. Wagoner's languid delivery of the song is terrifying: he genuinely sounds as though he were fighting the urge to gibber by phrasing his words with exaggerated care. Or is that FRIED and eaten? They both abused our Bill of Rights. You can sample the tracks there at Amazon. Mysterian many hours of pleasure. You know I had forgotten this song. If you...

...ere surrounded by beckoning skeletons, sometimes leading them in a dance to their own graves. ok, thanks for your work man. And, knowing his past success with science, one further imagines that this is the device that will finally destroy New Orleans. Wagoner's languid delivery of the song is terrifying: he genuinely sounds as though he were fighting the urge to gibber by phrasing his words with exaggerated care. Or is that FRIED and eaten? They both abused our Bill of Rights. You can sample the tracks there at Amazon. Mysterian many hours of pleasure. You know I had forgotten this song. If you...

Does anyone have suggestions for either extending operators or adding intrinsics that support multiple return values? Or is packaging everything into a derived types the only way? I have an idea for supporting floating-point exception flags and modes in a flexible way by making the data dependencies explicit, but I've become quite lost poking around. I suspect this will end up involving

----- Original Message ----- > From: "Chandler Carruth via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Philip Reames" <listmail at philipreames.com>, "Duncan P. N. Exon > Smith" <dexonsmith at apple.com>, "Sanjoy Das" > <sanjoy at playingwithpointers.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>

A clarification pointed out by David Majnemer: what I"m really talking about is "comdat or comdat-semantic-equivalents" which include linkonce_odr and available_externally. As a further strategy to recover optimizations: On platforms with comdat support, we could also teach function attrs that deduction is safe for functions which are only called from within their own comdat. And

Hi, as a language front end developer I am a bit terrified by any "unwind here will call terminate" semantics in the IR. I'd prefer the LLVM IR to be free from any assumptions about the languages compiled to it and this looks like C++ semantics sneaking into LLVM. Thus I'm under the expression the calling terminate semantics should be implemented by the front end.

...bout that particular wording. If we can find wording which rephrases that to address the concern while retaining the intent, that seems like an obvious thing to fix. > > Again, I don't doubt the good intentions of the people working on > this, but as written this is one of the most terrifying documents I > have seen. > > Cheers, > Rafael > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

I don't know anybody who has S-plus these days, but I expect some of you might, and perhaps you won't mind telling me something. I'm working on my presentation about R for the general audience. As I survey the suggestions from this list about that project, I find myself wondering whether S-plus benefits from R. Does S-plus syntax change like R's does. I can take code for S and

On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> wrote: > On 08/08/2013 02:02 AM, Justin Holewinski wrote: >> This worries me a bit. This would introduce language-specific >> processing into SelectionDAG. OpenCL maps address spaces one way, other >> languages map them in other ways. Currently, it is the job of the >> front-end to map

On Wed, Feb 24, 2016 at 9:35 PM Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > > From: "Chandler Carruth via llvm-dev" <llvm-dev at lists.llvm.org> > > To: "Philip Reames" <listmail at philipreames.com>, "Duncan P. N. Exon > > Smith" <dexonsmith at apple.com>, "Sanjoy Das" > >

LLVM Friends, First time attempting a build of dragonegg, using our shiny new install of clang-3.3. I'm clearly off to a terrifying start! dragonegg-3.3.src$ CXX=/usr/bin/gcc GCC=/usr/bin/gcc ENABLE_LLVM_PLUGINS=1 LLVM_CONFIG=/usr/bin/llvm-config CFLAGS=-I/usr/clang/3.3/lib/clang/3.3/include CXXFLAGS="-I/usr/clang/3.3/lib/clang/3.3/include" make Compiling utils/TargetInfo.cpp In file included from /usr/clan...

Hello, http://pasik.reaktio.net/xen/patches/xen-pvscsi-drivers-linux-2.6.32.27-pvops-v01.diff This is the first version of Xen PVSCSI drivers, both the scsiback backend and scsifront frontend, ported from Novell SLES11SP1 2.6.32 Xenlinux kernel to pvops xen/stable-2.6.32.x branch. At the moment it''s *only* compile-tested with the latest xen/stable-2.6.32.x git kernel as of today