search for: u999

...<jonathan at codesourcery.com> wrote: > Even further off topic, in phab wishlist land: It'd be awesome if it > were capable of inferring extended patch context by looking at the svn > repo/git mirrors (rather than requiring the person submitting the patch > to re-upload with -U999). > Yea, this is hard, because detecting which path a patch goes against is hard (for example, if the patch path is a pure add for a new tools/sometool directory, is it in clang or llvm?) and requiring people to do global top-level llvm patches seems rather problematic. The workaround is to us...

...te: >> >>> Even further off topic, in phab wishlist land: It'd be awesome if it >>> were capable of inferring extended patch context by looking at the svn >>> repo/git mirrors (rather than requiring the person submitting the patch >>> to re-upload with -U999). >>> >> >> Yea, this is hard, because detecting which path a patch goes against is >> hard (for example, if the patch path is a pure add for a new tools/sometool >> directory, is it in clang or llvm?) and requiring people to do global >> top-level llvm patche...

This might be slightly off topic, but I'd really like a way to be able to run the buildbots off a Phabricator Diff before committing. On Thu, Jul 2, 2015 at 9:01 AM, Manuel Klimek <klimek at google.com> wrote: > Unfortunately threading will be broken for changes currently under review > (new patches shouldn't have the problem). > I'm very sorry for this inconvenience

...tached below for reference. Thanks, Terence --------------------- exten => 74928,1,Answer exten => 74928,2,Wait(1) exten => 74928,3,Playback(welcomemsg) exten => 74928,4,Dial(SIP/TerenceParker&SIP/DavidLiu&SIP/GardenVista&SIP/PeterLiu,90,tm) exten => 74928,5,Voicemail,u999 exten => 74928,6,Hangup exten => 74928,102,Voicemail,b999 exten => 74928,103,Hangup exten => 75160,1,Answer exten => 75160,2,Dial(SIP/DavidLiu,180,tm) exten => 75160,3,Voicemail,u1000 exten => 75160,4,Hangup exten => 75160,102,Voicemail,b1000 exten => 75160,103,Hangup e...

...; Even further off topic, in phab wishlist land: It'd be awesome if it >>>>> were capable of inferring extended patch context by looking at the svn >>>>> repo/git mirrors (rather than requiring the person submitting the patch >>>>> to re-upload with -U999). >>>>> >>>> >>>> Yea, this is hard, because detecting which path a patch goes against is >>>> hard (for example, if the patch path is a pure add for a new tools/sometool >>>> directory, is it in clang or llvm?) and requiring people to...

Hello, find enclosed a first patch for adding tail call optimizations for thumb1 targets. I assume that this list is the right place for publishing patches for review? Since this is my first proposal for LLVM, I'd very much appreciate your feedback. What the patch is meant to do: For Tail calls identified during DAG generation, the target address will be loaded into a register by use

Hi, I am sending this proposal to get feedbacks on how we could make the tagging of bug fixes and regressions more obvious. The idea is to provide easily accessible information to help deciding what to cherry-pick in a release branch. * Context * People shipping compilers based on LLVM may not completely align with the official releases of LLVM. Thus, the stabilization of each custom release