search for: concessions

...cified value? > Constant folding undefined expressions is sort of silly, but I appreciate that it makes undefined behavior problems in frontends immediately apparent with trivial cases before they creep up on you in more complicated optimized code. After all, even if the backend makes practical concessions to trivial cases, the underlying semantic problem is still there and will bite you eventually. For high-level languages like Julia that want to provide efficiency but also give defined behavior to all user-exposed cases, I think adding an LLVM intrinsic to represent division that's defined to t...

I'm also not fully happy with LLVM's behavior here. There is another undefined case too, which is the minimum integer divided by -1. In Julia I can get "random" answers by doing: julia> sdiv_int(-9223372036854775808, -1) 87106304 julia> sdiv_int(-9223372036854775808, -1) 87108096 In other contexts where the arguments are not constant, this typically gives an FPE trap.

...deling in the vectorizer, inliner, etc. Like min/max, this is another case where the sum of the IR parts is greater than the actual cost. Beyond that, it seems odd to me that we'd choose the longer IR expression of something that could be represented in a minimal form. I know we make practical concessions in IR based on backend deficiencies, but in this case I think the fix would be easy - if we're in contract=fast mode, just split all of these intrinsics at DAG creation time and let the DAG or other passes behave exactly like they do today to fuse them back together again? On Sat, Nov 19, 2016...

On Tue, 22 Feb 2005, Jeff Cohen wrote: > Chris Lattner wrote: >> On Tue, 22 Feb 2005, Jeff Cohen wrote: >>> Also, some of what LSR needs to decide is architecture dependent. For >>> example, it may not want to strength reduce a multiplication which >>> multiplies by a small power of two, as this is handled by addressing modes >>> on some

Chris Lattner wrote: > On Tue, 22 Feb 2005, Jeff Cohen wrote: > >> Also, some of what LSR needs to decide is architecture dependent. >> For example, it may not want to strength reduce a multiplication >> which multiplies by a small power of two, as this is handled by >> addressing modes on some architectures. > > > You're right. However, we can

Hi all, I have just successfully ported openssh-2.1.0p3 to Cygwin. As you may know, Cygwin is a GPLed POSIX layer for Windows OSes. To be serious: I don't _like_ Windows systems and sometimes I really hate that STUPID concessions which are necessary when trying to get U*X software working on Windoze but for some reason that's exactly the reason, why I love to work on Cygwin! Porting to Cygwin has two major goals: - Care for all file access to differ `text mode' (files may have \n or \r\n line endings) from `bina...

Well, this is a bit stronger than a proposal; this is "what I plan to do unless people see obvious flaws I missed"... The text comment header is the second (of three) header packets that begin a Vorbis bitstream. It is meant for short, text comments, not arbitrary metadata; arbitrary metadata will be put in a metadata stream, likely an XML stream type. We've discussed this in

...attitude. I run an online radio station. We're drooling to move to ogg, but there are major tradeoffs: - Most listeners will have to upgrade to a new client or install a plugin. - Most WinAMPers connect with v.3, which won't work with ogg principally because the icecast developers make no concessions for its mistaken mime-typing. - Mac users have to give up iTunes and install Whamb. - Effectively no hardware device support. I realize all this is changing, and I'm doing whatever I can to get it there, but you can only force new standards and technologies on people if you're Steve Jobs....

...too-large values (64-bit int on 32-bit machine), but that's error prone and inefficient. You should emit the best types per architecture. * Your language's ABI: C++ has an ABI which defines the layout of classes and objects that can be different between targets. You may want to make special concessions due to speed and code-size concerns. Pretty much everything else should be dealt with by the IR passes and lowering. But the biggest benefit of lowering to LLVM IR is safety. Lowering to C will actually be lowering to "strings", not proper C. Unless you write your own C validation engi...

...easonable to accept, which is why we do some aggregation in userspace; this aggregation should probably be tuned better, but it's important that icecast control it, not the kernel. You want TCP_CORK, it seems, because of bugs in your target devices - well, whilst we're willing to make some concessions to broken clients, an inability to speak TCP correctly is well outside what I consider sensible, particularly given that it will degrade icecast's performance for working clients (you remain welcome, of course, to hack up your local copy). It's also very unportable. Mike

Hello everyone, I sent the last email prematurely - I had a few more questions. I don't wish to start a holy war here, but are there certain OSs / Distros that are preferred for running very busy icecast servers? We're a Solaris shop currently, but don't mind using linux or BSD if that would make things easier. I see there is a Fedora Core RPM on the icecast page - does that

On Fri, 2015-01-23 at 13:32 -0800, Keith Keller wrote: > <snip> > But (getting back a little to the original topic) getting to the 3ware > web interface should not require root privileges on the client, since > it's just the browser connecting to the 3ware http(s) listener. The OP > seemed to be ranting about a prompt for an administrative password from > the desktop

On Fri, Apr 11, 2008 at 10:11 PM, Conrad Parker <conrad at metadecks.org> wrote: > No, vorbiscomments are meant to be human-readable. But I CAN read base64! ... Seriously now, this is a good idea. Just the right (if not perfect) solution for this issue. See, those players that can read Vorbis Comments already limit what the user sees to the basic ones like Artist, Album, Comment,

...ayback, and it looks like it will be quite a while before we get streaming in Apple's tools. All of the other players I'm aware of pretty much already support Ogg. > - Most WinAMPers connect with v.3, which won't work with ogg > principally because the icecast developers make no concessions > for its mistaken mime-typing. What? Last I checked, the ogg plugin for winamp 3 threadlocked just after connect. As far as I know, any bugs there are not our fault. If they are, we'd appreciate a detailed description on icecast-dev. > - Mac users have to give up iTunes and instal...

On 8/31/05, Michael Hale <giftculture@gmail.com> wrote: > Hello everyone, > > I sent the last email prematurely - I had a few more questions. I > don't wish to start a holy war here, but are there certain OSs / > Distros that are preferred for running very busy icecast servers? > We're a Solaris shop currently, but don't mind using linux or BSD if > that

...t has a lot of late to resorb) to merge the USB improvements from the CVS Development branch. That means that the updated newhidups, as well as tripplite_usb and bcmxcp_usb if these are fine. To Charles and Wolfgang: any comments, objections, last things to be done, ...? However, there will be no concessions to stability. So once 2.0.3-pre2 is out, I'll call for a massive test and feedback. Arnaud <http://arnaud.quette.free.fr/> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20051001/a9ff8f7a/att...

Take delivery of a great concession on your Meds-RX Name brands, Finest quality. Vast variety, including Difficult to find drugs 0 RX needed. Private with No waiting quarters or appointments required Shipped within 21 hours or under, discrete boxing Purchase in bulk and Save! Still additional http://uk.geocities.com/hanho_keeffes/?ms=05No prescription needed. Have you ze luggage? No; but

...> Constant folding undefined expressions is sort of silly, but I appreciate > that it makes undefined behavior problems in frontends immediately apparent > with trivial cases before they creep up on you in more complicated optimized > code. After all, even if the backend makes practical concessions to trivial > cases, the underlying semantic problem is still there and will bite you > eventually. For high-level languages like Julia that want to provide > efficiency but also give defined behavior to all user-exposed cases, I think > adding an LLVM intrinsic to represent division tha...

...P/IP stack, and that doesnt seem usefull? > You want TCP_CORK, it seems, because of bugs in your target > devices That is my main motivation indeed, however, imho there are more valid reasons to want TCP_CORK, as i tried to explain above. >- well, whilst we're willing to make some concessions > to broken clients, an inability to speak TCP correctly is > well outside what I consider sensible, In your justification for nodelay, you state "(many clients don't care, but some do)", isn't that the same thing? > that it will degrade icecast's performance for w...

On Fri, Sep 29, 2017 at 7:51 PM, Andrew Trick via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > > On Sep 22, 2017, at 10:34 AM, Thorsten Schütt via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > > > > #define GET_REGINFO_ENUM > > #include "AArch64GenRegisterInfo.inc" > > > > #define GET_INSTRINFO_ENUM >