search for: baggage

Older targets like Mips had/have assemblers and ABIs that carry a lot of baggage. The small bit of baggage that is giving me fits is that MipsELFObjectWriter needs to know the relocation model (static,pic,cpic), whether we are using xgot (-mgot), which abi (old,new), which architecture (32r[123],64[123]), which if any coprocessor or extention instructions are used (mips16,micr...

On 6 December 2012 17:49, Carter, Jack <jcarter at mips.com> wrote: > Older targets like Mips had/have assemblers and ABIs that carry a lot of > baggage. > > The small bit of baggage that is giving me fits is that MipsELFObjectWriter > needs to know the relocation model (static,pic,cpic), whether we are using > xgot (-mgot), which abi (old,new), which architecture (32r[123],64[123]), > which if any coprocessor or extention instructio...

...39;t disable the audio device in my BIOS, so the system finds it in the PCI device list and configures it on each boot. Yes, I know I can blacklist specific device driver modules, but I've got a minimum of 11 audio-related kernel modules loaded on a default C7 configuration, and untold dbus baggage to go with them So.. what can I do to have CentOS7 completely ignore the audio hardware it finds? Thanks.

...y toolchain uses clang but not libc++/abi/unwind, we have our own, and we don't currently include them in our tree. We do include compiler-rt. If we should change our minds later we can opt-in to anything else we want (libcxx etc, lld? lldb? who knows) but in the meantime they are unnecessary baggage for my purposes. --paulr

os x comes with openssh, and some other nixy goodness. the rest you can get at brew.sh. when i ssh -Y into the host, ill just virt-manager or virt-viewer, but the x server on os x comes with some baggage and silly annoyances like "helpfully" trapping the mouse with a release combo thats hard to deal with from os x. running a vnc client over os x would still come with baggage and redundantly layering protocols. my virt host is already painfully slow from all the virtual machines its runnin...

...We're kind of in a frozen state where making intmax_t larger than 64 bits will break more programs than expected because it has ABI implications: https://stackoverflow.com/questions/21265462/why-in-g-stdintmax-t-is-not-a-int128-t My personal preference is to avoid intmax_t, as it has too much baggage (the risk of future widening, vs. NOT being the widest type after all), similar to how size_t already has baggage. In short, having something that is not platform specific is easier to reason about (for the same way that using size_t gives me more grief than directly using int32_t or int64_t; even...

...;>> + /* FIXME: for historical reasons, we force a notify here if >>> + * there are outgoing parts to the buffer. Presumably the >>> + * host should service the ring ASAP. */ >> I don't think we have a reason to do this for packed ring. >> No historical baggage there, right? > Based on the original commit log, it seems that the notify here > is just an "optimization". But I don't quite understand what does > the "the heuristics which KVM uses" refer to. If it's safe to drop > this in packed ring, I'd like to do...

...;>> + /* FIXME: for historical reasons, we force a notify here if >>> + * there are outgoing parts to the buffer. Presumably the >>> + * host should service the ring ASAP. */ >> I don't think we have a reason to do this for packed ring. >> No historical baggage there, right? > Based on the original commit log, it seems that the notify here > is just an "optimization". But I don't quite understand what does > the "the heuristics which KVM uses" refer to. If it's safe to drop > this in packed ring, I'd like to do...

...Is there any reason why functions (such as PromoteMemToReg) accept parameters of types DominatorTree and DominanceFrontier instead of types DominatorTreeBase and DominanceFrontierBase? It seems to me that they should accept the abstract interface instead of the implementation (and avoid the extra baggage of a pass). Having said that, I'm willing to hack llvm and submit a patch; I just wanted to see if its been done already... Thank you, -- Nick Johnson

Dear R People I figured it out. I should RTFM before asking questions, particularly on Saturday nights! Thanks for your patience. Sincerely, Erin -- Erin Hodgess Associate Professor Department of Computer and Mathematical Sciences University of Houston - Downtown mailto: erinm.hodgess at gmail.com

..., it looks like it is really intended to be more of a softphone running on a Linux machine, and will take some heavy mods to get it running in an embedded DSP environment. Running something like AstLinux on the DSP along with iaxClient may be a possibility but it seems like an awfully lot of baggage to carry around just to get the IAX part of the project. Any pointers would be greatly appreciated. Best, Bill

On 02/01/18 16:33, Ben Lindstrom wrote: > And how many annoying "Do you really want to do this?" type questions > do you prompt the user and assume it is "fine"? I think zero.? I think the warning goes in the man page: ? --allow-insecure-short-key? This option allows use of keys shorter than 1024 bits, however, it is known that such keys can be broken quite

...tions have in common with many others is the lack of testing. I want to change that. I''d like to help lead an effort to make the facebooker tests better. One thing that I think would help is a little better organization and cleanup of the existing test suite. Part of it is just baggage from lots of copying and pasting, but some of it is just inherent to Test::Unit. Would anyone be opposed to moving towards using Shoulda or RSpec for the tests? I think they would allow us to clean up the test suite and make it more accessible to contributors. I''ve personally be...

...cult issue except we require the ELF portion to work from the same sketch book for the 2 assemblers. I am experimenting putting in a std::set into the MCSubtargetInfo base class that is for target use and see if I can end my ordeal ;-) Probably only useful for the older targets which have a lot of baggage to support. If that works I can convert it to work with Feature, but that is a bit of overkill at this point. Cheers, Jack ________________________________________ From: Rafael Espíndola [rafael.espindola at gmail.com] Sent: Friday, December 07, 2012 1:52 PM To: Carter, Jack Cc: List Subject: Re:...

Hi all, MenuEngine is a small Rails engine that can generate templated drop-down DHTML menus commonly used for web site navigation. Supports creation of menus from a YAML file, from code and from pre-configured HTML. Optionally integrates with UserEngine for authorization. http://www.muermann.org/ruby/menu_engine Project page: http://rubyforge.org/projects/menuengine This is my first attempt

Well here's a suggestion - a little crazy - but works... Most equipment is taking the 120vac and converting it into DC voltage. So why not just feed it DC voltage directly??? We had a situation where our field techs needed to test dsl circuits and voip ata from the demarcation point outside a house or business. A UPS might have worked - but the down conversion of 12v dc battery in ups up to

id like to access libvirt kvm consoles from my macbook. i tried realvnc, which just crashes immediately, and the built in "screen sharing" client, which insists on a password, which i havent set. does anyone here do this? which vnc client do you use?

...e of templates, macros, where you have generated code within a function whose original source lines are from a different source file. It means that a source location (which is attached to every expression node) can't consist of merely [file, offset, length] but now has to carry other contextual baggage around as well, since conceivably any subtree of an expression could originate from outside the function. Alternatively, passing in the compile unit makes sense, except that now there's no way to tell the IRBuilder about regions. Also, even though my code now assembles correctly, gdb gets very...

...we force a notify here if > > > > > + * there are outgoing parts to the buffer. Presumably the > > > > > + * host should service the ring ASAP. */ > > > > I don't think we have a reason to do this for packed ring. > > > > No historical baggage there, right? > > > Based on the original commit log, it seems that the notify here > > > is just an "optimization". But I don't quite understand what does > > > the "the heuristics which KVM uses" refer to. If it's safe to drop > > >...

...we force a notify here if > > > > > + * there are outgoing parts to the buffer. Presumably the > > > > > + * host should service the ring ASAP. */ > > > > I don't think we have a reason to do this for packed ring. > > > > No historical baggage there, right? > > > Based on the original commit log, it seems that the notify here > > > is just an "optimization". But I don't quite understand what does > > > the "the heuristics which KVM uses" refer to. If it's safe to drop > > >...