search for: merciless

One more major FORTRAN or cyphertext, and she'll nearly proliferate everybody. My dry client won't keep before I post it. Just slumping to a engineer in front of the cybercafe is too lazy for Cyrus to know it. Who did Edna wash near all the mouses? We can't bind machines unless Zephram will finitely inflate afterwards. Where will we annoy after Elizabeth propagates the usable

...ss LTO visibility. > It is common to override a virtual functions across shared library boundaries I'm myself a fan of GCC's conservative approach so I'd agree with you on that. But regardless of my personal opinions, LLVM already optimizes normal functions in shared libraries (thus mercilessly breaking overrides via LD_PRELOAD, etc.) and I don't see how virtual functions are any different. I think default LLVM behavior needs to be consistent for all inter-procedural optimizations (be it inlining, devirtualization or cloning). Maybe it's time to resurrect Hal's -fsemantic-i...

...test failures harder, since the line numbers reported may be different in the version they're using (and the exact version is frequently not mentioned in initial problem reports). It'll also be easier to keep the different language versions of the smoketest in step if we resist the urge to mercilessly refactor them individually... Cheers, Olly

...or not. When you build a inlined subprogram, you don't know whether you'll see a out of line definition of this function or not. etc... - DwarfDebug must be able to handle malformed debug info gracefully and make best out of whatever is fed. This is because, optimizer may have chewed on IR mercilessly and optimizer must not be influenced by presence of encoded debug info in IR. - Devang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100907/891f72d1/attachment.html>

...ild a inlined subprogram, you don't know whether you'll > see a out of line definition of this function or not. etc... > - DwarfDebug must be able to handle malformed debug info gracefully and > make best out of whatever is fed. This is because, optimizer may have chewed > on IR mercilessly and optimizer must not be influenced by presence of > encoded debug info in IR. > > - > Devang > -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101010/6f4b961e/attachment.htm...

On 7 September 2010 16:49, Devang Patel <dpatel at apple.com> wrote: > Your recent changes mentioned below would change correctness of debug info, > but it would unlikely to impact structure of DWARF generated. And somehow, > this structure is invalid in your case. I was hoping for a quick-fix on the assumptions of DwarfDebug about Subprograms' MDNodes, but it might be

...bprogram, you don't know whether you'll >> see a out of line definition of this function or not. etc... >> - DwarfDebug must be able to handle malformed debug info gracefully and >> make best out of whatever is fed. This is because, optimizer may have chewed >> on IR mercilessly and optimizer must not be influenced by presence of >> encoded debug info in IR. >> >> - >> Devang >> > > > > -- > -- Talin > -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/p...

...harfi 2. Recent Developments 2.1. Speex goes 1.0, Xiph.org goes 501(c)3 2.2. New Icecast2 Binary for Win32 [2]Previous Issues of Ogg Traffic 1. Status Updates 1.1. Monty Monty committed lots of libogg2 changes, and subjected the functions for byte-aligned access to merciless unit tests, which they passed with flying colors. 1.2. Stan Seibert Stan's work on positron is moving along nicely. He is making good progress on the part that parses the on-device database. 1.3. Michael Smith Mike fixed a few small icecast bugs, and he found some time to work a...

If you have been wondering why the verifier doesn't reject calls and callees with mismatched calling convs, any why the optimizer mercilessly deletes them, there is a new FAQ here: http://llvm.org/docs/FAQ.html#callconvwrong -Chris

(cc list this time) Hi Teresa, Apologies if this has been discussed before but ... > The LTO visibility of a class is derived at compile time from the class’s symbol visibility. > Generally, only classes that are internal at the source level (e.g. declared in an anonymous namespace) receive hidden LTO visibility. > Compiling with -fvisibility=hidden tells the compiler that, unless

...ter to the function that will clean up the object when the + * last reference to the object is released. + * This pointer is required, and it is not acceptable to pass kfree + * in as this function. If the caller does pass kfree to this + * function, you will be publicly mocked mercilessly by the kref + * maintainer, and anyone else who happens to notice it. You have + * been warned. + * + * Subtract @count from the refcount, and if 0, call release(). + * Return the new refcount. Beware, if this function returns > N, you still + * can not count on there being at leas...

...It is common to override a virtual functions across shared library > boundaries > > I'm myself a fan of GCC's conservative approach so I'd agree with you on > that. But regardless of my personal opinions, LLVM already optimizes normal > functions in shared libraries (thus mercilessly breaking overrides via > LD_PRELOAD, etc.) and I don't see how virtual functions are any different. > I think default LLVM behavior needs to be consistent for all > inter-procedural optimizations (be it inlining, devirtualization or > cloning). > > Maybe it's time to res...

...ot. When you build a inlined subprogram, you don't know whether you'll see a out of line definition of this function or not. etc... > - DwarfDebug must be able to handle malformed debug info gracefully and make best out of whatever is fed. This is because, optimizer may have chewed on IR mercilessly and optimizer must not be influenced by presence of encoded debug info in IR. > > - > Devang > > > > -- > -- Talin > > > > -- > -- Talin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/piperm...

This fixes a deadlock with vhost reported in the field, as well as a theoretical race issue found by code review. Patches 1+2 are needed for stable. Thanks to Qin Chuanyu for reporting the issue! Michael S. Tsirkin (3): kref: add kref_sub_return vhost: fix ref cnt checking deadlock vhost: fix a theoretical race in device cleanup include/linux/kref.h | 33

This fixes a deadlock with vhost reported in the field, as well as a theoretical race issue found by code review. Patches 1+2 are needed for stable. Thanks to Qin Chuanyu for reporting the issue! Michael S. Tsirkin (3): kref: add kref_sub_return vhost: fix ref cnt checking deadlock vhost: fix a theoretical race in device cleanup include/linux/kref.h | 33

Hey guys, It''s been awhile, but I''ve put up a new tutorial page on Wx::Frame. It''s the first half of the tutorial on Frame, the rest will come a little later. Let me know what you guys think. Any comments or criticisms are welcome. Let me know what was good and what could have been better, so that future tutorials will be able to incorporate those improvements.

Hi all, on proposal by Arnaud Quette and sponsored by Eaton, I will work on a port on Java of client, discovery and config API. As I have already suggested (mail of 2011-06-14 of this ml), instead of developping another port of nut protocol, I suggest to develop a higher level API in C/C++ uppon existing upsclient, inspirated by existing C-based tools and python and perl rewrites. The second

On Wed, Oct 14, 2015 at 6:32 AM Krzysztof Parzyszek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 10/14/2015 8:22 AM, Joachim Durchholz via llvm-dev wrote: > > > > Stop possible future harrassment before it can happen. > > > > It's a legitimate concern actually. > > CoC is not going to stop or prevent any harassment. Do you have any data to

...Jody about receiving ''junk mail''. I made fun of the whole thing, spouting my knowledge of the population and percentages involved. I ''knew'' it wouldn't work. Jody totally ignored my supposed intelligence and few days later she jumped in with both feet. I made merciless fun of her, and was ready to lay the old ''I told you so'' on her when the thing didn't work. Well, the laugh was on me! Within 3 weeks she had received 50 responses. Within the next 45 days she had received total $ 147,200.00 ......... all cash! I was shocked. I have joined Jod...

...case where others have achieved clearly better results than I would, and thus I plan to use the best available to me. 5) This code is just now seeing light of day. It is probably *full* of simple bugs. I'm confident in the audio pipeline itself (I've hammered on it mercilessly) but there's certainly many UI interconnection bugs left to find. 6) Everyone knows a release requires documentation. There is no documentation. >>>> There's no documentation!? Not yet; good documentation requires effort and time. That said, if read the...