search for: concession

...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...

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, 201...

...achine code generation time. That's a good point. Currently, given a target-independent input, we only do target independent transformations on the code (and this breaks that premise somewhat). I think that you're right that we should eventually do this in the code generator, but as a concession to what is easiest in the short term and will have the biggest performance impact, I still think doing it at the LLVM level is the way to go. -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/

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 `bin...

...h 0x7A inclusive (a-z). The field name is immediately followed by ascii 0x3D ('='); this equals sign is used to terminate the field name. 0x3D is followed by 8 bit clean field contents to the end of the field. Implications: field names should not be 'internationalized'; this is a concession to simplicity not an attempt to piss off the majority of the world that doesn't speak English. Field *contents*, however, should be internationalizable... suggestions on the proper encoding for that? We have the length of the entirety of the field and restrictions on the field name so that th...

...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 eng...

...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

...etimes selectively, as in doing glibc* and kernel stuff first and then re-booting to do the rest) and then return to the normally scheduled programming. I like it that way - it's secure, keeps me aware of what is going on on my machines w/o having to rummage through logs, mail, or worse. As a concession to the now broken runlevel/X multiple session processing, I remain in run level 5 and do the backups etc. Not the way I would prefer. And now since I filed a bug and reported the crash and provided narrative and files and have seen 0 movement on the bug, I wonder why I wasted my time reporting it....

...h images is likely to break non-libvorbis-based decoders since those don't expect muxed streams. I know, because I have been testing around Vorbis+Skeleton files. Rules are not set in stone. We are supposed to bend them a little when it's necessary and, truth be told, this is a very small concession to please an audience. -Ivo

...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 insta...

...- is it much of a headache to have an > icecast server be able to relay mp3 and WMA9 streams at the same time? Our primary aim is to have excellent support for free formats (primarily, this means the xiph codecs - we'd be happy to help out with any other freely usable formats, though). As a concession to existing icecast users, we have basic mp3 support (basically we just pass it through untouched), and this mechanism works for some other codecs as well. However, we will not add explicit support for any other formats, nor will we support usage of icecast with other formats (i.e. if it breaks, yo...

...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/at...

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/...

...> 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 th...

...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...

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 >