search for: downthread

...fference of opinion. With my documentation writer hat on, I can say that I wrote my page that way out of convenience (rather hastily I might add :) and in the absence of official style guidelines it was easiest to copy directly from the screen. Perhaps we can adopt some of the guidelines suggested downthread by Karsten that will make things more clear. In the meantime I'll work on generalizing the centpkg page. --Brian

...where and having to spend 10 minutes waiting > for a build leads to a lot of wasted developer time. > > > > The real culprit here is tablegen. Can we split support and ADT into > two - the parts that tablegen depends on and the parts that it doesn’t? > > In all the comments downthread, I think there is one thing that hasn't > been mentioned: doing a split like this makes tblgen evolution more > difficult. If libsupport was split into “used by tblgen” and “not used by > tblgen” sections, and then a new tblgen feature needs to use other parts of > libsupport, they...

...issues > that the rewrite is meant to address. I've definitely seen various > discussions here and there from time to time, but nothing that a person > could look at and get a big picture view of what's happening and why. > > -- Sean Silva > Do'h, just saw you mention downthread of the "Pass Manager Redux" you posted like a year ago ("redux" was apparently the word that was missing from all my mail searches). (It's been a year, can you blame me for not remembering? ;) ) -- Sean Silva -------------- next part -------------- An HTML attachment was sc...

...file somewhere and having to spend 10 minutes waiting for a build leads to a lot of wasted developer time. > > > > The real culprit here is tablegen. Can we split support and ADT into two - the parts that tablegen depends on and the parts that it doesn’t? > > In all the comments downthread, I think there is one thing that hasn't been mentioned: doing a split like this makes tblgen evolution more difficult. If libsupport was split into “used by tblgen” and “not used by tblgen” sections, and then a new tblgen feature needs to use other parts of libsupport, they’d have to be moved...

...nd having to spend 10 minutes waiting for a build leads to a lot of wasted developer time. >> > >> > The real culprit here is tablegen. Can we split support and ADT into two - the parts that tablegen depends on and the parts that it doesn’t? >> >> In all the comments downthread, I think there is one thing that hasn't been mentioned: doing a split like this makes tblgen evolution more difficult. If libsupport was split into “used by tblgen” and “not used by tblgen” sections, and then a new tblgen feature needs to use other parts of libsupport, they’d have to be moved...

...; > With my documentation writer hat on, I can say that I wrote my page that > way out of convenience (rather hastily I might add :) and in the absence > of official style guidelines it was easiest to copy directly from the > screen. Perhaps we can adopt some of the guidelines suggested downthread > by Karsten that will make things more clear. In the meantime I'll work > on generalizing the centpkg page. > > --Brian > Excellent! Thank you. One page at a time is as fast as we can work. -------------- next part -------------- An HTML attachment was scrubbed... URL: <htt...

...am at android.com > Cc: stable at vger.kernel.org [4.9+] > Signed-off-by: Jorge E. Moreira <jemoreira at google.com> > --- > net/vmw_vsock/virtio_transport.c | 13 ++++++------- > 1 file changed, 6 insertions(+), 7 deletions(-) This patch is good to go, I've posted my R-b downthread. Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20190516/fd08311f/attachment.sig>

...my documentation writer hat on, I can say that I wrote my page that >> way out of convenience (rather hastily I might add :) and in the absence >> of official style guidelines it was easiest to copy directly from the >> screen. Perhaps we can adopt some of the guidelines suggested downthread >> by Karsten that will make things more clear. In the meantime I'll work >> on generalizing the centpkg page. >> >> --Brian >> > > Excellent! Thank you. > > One page at a time is as fast as we can work. > That's interesting. It appears this exc...

...wasted developer time. >>>>> > >>>>> > The real culprit here is tablegen. Can we split support and ADT >>>>> into two - the parts that tablegen depends on and the parts that it doesn’t? >>>>> >>>>> In all the comments downthread, I think there is one thing that hasn't >>>>> been mentioned: doing a split like this makes tblgen evolution more >>>>> difficult. If libsupport was split into “used by tblgen” and “not used by >>>>> tblgen” sections, and then a new tblgen feature n...

...gt;>> and adds a requirement for using clang in this mode that wasn't there >>> before when using clang for -O2. We are trying to make the transition >>> from clang -O2 to clang -O2 + ThinLTO as seamless as possible. >> >> I'd just like the point out that downthread serious suggestions are being >> fielded to use a nonstandard ELF header or nonstandard bits marking the >> header. This "adds a requirement". >> >> At this point at least 1 (the only?) concrete deployment use case (besides >> yours) that has been brought up...

Hi all.. I new in Ruby/Rails.. Where could i get some good tutorial about SOAP using Rails? I''ve been googling yet still did''nt find good tutorial. Thank you in advance.. :) -- Regards, Ananda Putra

...t all call graphs of compilers include edges for > indirect calls and external functions, so they are already quadratic in > this sense. > > if what you state is correct, and we don't have a conservatively correct > call graph, that would be ... interesting. > Mehdi clarified downthread the situation (at least for me). Now that I look more closely at the comments in https://github.com/llvm-mirror/llvm/blob/master/include/llvm/Analysis/LazyCallGraph.h it intentionally does not model a call graph in this sense. I.e. - in a traditional CG, an edge means something like "at runti...

...gt;>> > >>>>>>> > The real culprit here is tablegen. Can we split support and ADT >>>>>>> into two - the parts that tablegen depends on and the parts that it doesn’t? >>>>>>> >>>>>>> In all the comments downthread, I think there is one thing that >>>>>>> hasn't been mentioned: doing a split like this makes tblgen evolution more >>>>>>> difficult. If libsupport was split into “used by tblgen” and “not used by >>>>>>> tblgen” sections, and the...

On Sat, Sep 14, 2013 at 7:05 PM, Chandler Carruth <chandlerc at google.com>wrote: > On Sat, Sep 14, 2013 at 3:57 PM, Reed Kotler <rkotler at mips.com> wrote: > >> Hi Chandler, >> >> What changes are you planning to make? >> >> Are you going to submit a proposal and RFC? >> > > There have been several RFCs... > > What's your

...clude edges for >> indirect calls and external functions, so they are already quadratic in >> this sense. >> >> if what you state is correct, and we don't have a conservatively correct >> call graph, that would be ... interesting. >> > > Mehdi clarified downthread the situation (at least for me). > > Now that I look more closely at the comments in > https://github.com/llvm-mirror/llvm/blob/master/include/llvm/Analysis/LazyCallGraph.h > it intentionally does not model a call graph in this sense. I.e. > - in a traditional CG, an edge means some...

Changing a header file somewhere and having to spend 10 minutes waiting for a build leads to a lot of wasted developer time. The real culprit here is tablegen. Can we split support and ADT into two - the parts that tablegen depends on and the parts that it doesn't? >From what I can gather, Tablegen currently depends on these headers and all of their transitive dependencies. #include

...;>>>>> > The real culprit here is tablegen. Can we split support and ADT >>>>>>>>> into two - the parts that tablegen depends on and the parts that it doesn’t? >>>>>>>>> >>>>>>>>> In all the comments downthread, I think there is one thing that >>>>>>>>> hasn't been mentioned: doing a split like this makes tblgen evolution more >>>>>>>>> difficult. If libsupport was split into “used by tblgen” and “not used by >>>>>>>>> t...

On Dec 23 16:29, PatrickD Garvey wrote: > On Tue, Dec 23, 2014 at 4:18 PM, Karsten Wade <kwade at redhat.com> wrote: > > > On 12/23/2014 03:56 PM, Yves Bellefeuille wrote: > > > On Tuesday 23 December 2014, PatrickD Garvey > > > <patrickdgarveyt at gmail.com> wrote: > > > > > >> In > > >>

On a VPS I wanted to add to IP tables:- iptables -A XXXX -p tcp -m string --algo bm --string 'login' -j DROP I got: iptables: Unknown error 18446744073709551615 uname -a = 2.6.35.4 #2 (don't know how this got installed) lsmod | grep ipt = ipt_LOG 5419 2 yum upgrade iptables* = nothing to install. --------------------------------------- On a standalone server (C 5.6)

Hello all, LangRef says it is undefined behavior to pass null to a nonnull argument (`call f(nonnull null);`), but the semantics is too strong for a few existing optimizations. To support these, we can relax the semantics so `f(nonnull null)` is equivalent to `f(poison)`, but (A) it again blocks another set of optimizations, and (B) this makes the semantics of nonnull deviate from other