search for: bikescheding

...can't be aggregated back because of padding. > - memcpy only work memory to memory. It is certainly usable in some > cases, but certainly do not cover all uses. > > I'm willing to do the memcpy optimization in InstCombine (in fact, things > would not degenerate into so much bikescheding, that would already be done). > > > Calling out “bikescheding” what other devs think is what keeps the quality > of the project high is unlikely to help your patch go through, it’s > probably quite the opposite actually. > > > I understand the desire to keep quality high. Th...

...padding. >>> - memcpy only work memory to memory. It is certainly usable in some >>> cases, but certainly do not cover all uses. >>> >>> I'm willing to do the memcpy optimization in InstCombine (in fact, >>> things would not degenerate into so much bikescheding, that would already >>> be done). >>> >>> >>> Calling out “bikescheding” what other devs think is what keeps the >>> quality of the project high is unlikely to help your patch go through, it’s >>> probably quite the opposite actually. >>&g...

...ary in many cases. These can't be aggregated back because of padding. - memcpy only work memory to memory. It is certainly usable in some cases, but certainly do not cover all uses. I'm willing to do the memcpy optimization in InstCombine (in fact, things would not degenerate into so much bikescheding, that would already be done). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150817/4a727fcc/attachment.html>

...t;> - memcpy only work memory to memory. It is certainly usable in some >>>> cases, but certainly do not cover all uses. >>>> >>>> I'm willing to do the memcpy optimization in InstCombine (in fact, >>>> things would not degenerate into so much bikescheding, that would already >>>> be done). >>>> >>>> >>>> Calling out “bikescheding” what other devs think is what keeps the >>>> quality of the project high is unlikely to help your patch go through, it’s >>>> probably quite the oppos...

...down in a way that I'm not comfortable with - I think it has already gone too far. -eric > I'd like also to remind all to not fall into the hypothetical nirvana > fallacy, ie comparing proposed solution with an idealized and unrealized > one. That's a good recipe for endless bikescheding when pretty much > anythign would be better than the status quo. > > 2015-07-17 12:36 GMT-07:00 Juergen Ributzka <juergen at apple.com>: > >> Hi @ll, >> >> a few of us had recently a discussion about how to manage the C API and >> possible policies regardin...

Hi @ll, a few of us had recently a discussion about how to manage the C API and possible policies regarding addition, maintenance, deprecation, and removal of API. Even thought there is a strong agreement in the community that we shouldn't break released C API and should be backwards compatible, there doesn’t seem to be a developer policy that backs that up. This is something we should fix.

2015-08-16 22:10 GMT-07:00 David Majnemer <david.majnemer at gmail.com>: > > > I would argue that a fix in the wrong direction is worse than the status > quo. > How is proposed change worse than status quo ? > > >> >> The argument that target are relying on InstCombine to mitigate IR >> requiring legalization seems dubious to me. First, because both