search for: threadbar

...ne that I > think Doug is going to post. > > I think the safe thing is to revert for now and we can discuss all > of the semantics and what's going on in a more leisurely fashion and > let poor Bill get his project building :) > Imagine me standing in the snow, wearing a threadbare coat, selling matchsticks in front of city hall, my face dirty, my shoes have holes, a taxi cab drives by and splashes me, a solitary tear leaves a trail down my face. Cue violins. -bw :-)

Compile the following functions with "-O3 -target amd64" (see <https://godbolt.org/z/5xqYhH>): __int128 div(__int128 foo, __int128 bar) { return foo / bar; } On the left the generated code; on the right the expected, properly optimised code: div: # @div push rbp | mov rbp, rsp | call __divti3 | jmp __divti3 pop rbp | ret

...k the time to report these bugs! > you should expect that to become less frequent. > People are willing to assume the best of new contributors, but by the > time you reach a dozen threads without actually engaging with the > community's procedures that goodwill starts to look a bit threadbare. > > Cheers. > > Tim. > > [*] https://llvm.org/docs/Contributing.html | If you are working with LLVM and run into a bug, we definitely want | to know about it. I DONT WORK WITH LLVM. I was just curious whether it shows bugs and deficiencies I saw in two other C compilers, an...

...s they are entrenched in the various verticals. Please bear with me. I have dedicated last five years of my bread and butter earning career to FLOSS solutions but have difficulty in gaining traction in the enterprises working alone. Of course there are commercials involved. Which can be discussed threadbare. Perhaps another list for that. I was having a "Single window Solutions" in mind wherein the members/prospective customers can pick and choose services they want. Modalities/details can be worked out. Soliciting opinions from the esteemed members of this list. Regards, Rajagopal

>> > Only "_Z11dummysymbolv" should be there. Here's Doug's explanation of > why this should be so: > > Here's what it *looks* like is happening, and where the FE is probably > getting it wrong. First of all, the constructor in question is defined > outside of the basic_string class template as a non-inline definition: > >

On Dec 4, 2009, at 12:40 PM, Duncan Sands wrote: > Hi Bill, > >> Here's what I get with TOT compiling with -Os. The orig.ll is what >> I get before r72619. Notice that orig.ll has only one function in >> it. Both the one you sent and duncan.ll have more than one >> function. It's not the fact that more than one function is showing >> up, but

What unmitigated bullshit. Your attempt at logic is laughable. You hold up threadbare stereotypes as the norm, when in reality they are little more than characters straight out of Central Casting. The "genius hermit who can't associate with people" is dumb and false. It's meant to excuse behavior that is unacceptable, when in reality a person who cannot interact w...

...here, and I’d strongly recommend that people resist the urge to respond and just ignore the trolls. -Chris > On May 7, 2018, at 12:45 AM, Bill Wendling via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > What unmitigated bullshit. Your attempt at logic is laughable. You hold up threadbare stereotypes as the norm, when in reality they are little more than characters straight out of Central Casting. The "genius hermit who can't associate with people" is dumb and false. It's meant to excuse behavior that is unacceptable, when in reality a person who cannot interact w...

Hello everyone, A long time ago, I posted the Stanford Best Practices and I''ve gone through and updated it today. I''d like to have people go through it and see if we can strip out some Stanford specific stuff and tag this as an official best practice. I think an official best practice will be important as more and more people consider making shareable modules, etc (mostly