search for: internalise

...re? Tail >> pages don't have individual refcounts; all the refcounts are actually I had stuck with using the page because none of this stuff (yet) supports compound pages anyway so we shouldn't see a tail page anyway. But point taken, I admit I need to find some time to get a deeper internalised understanding of folios than just s/page/folio. > ohh, and I really should have caught that too. I plead spending too much > time recently in a somewhat more driver-centric mindset, and failing to > mentally shift gears properly for this case. > > Sorry for missing that! > >...

Has anyone used Puppet to manage Solaris Patches? If so could you pass on any tips. For those without Solaris experience, you can only describe the configuration of a Solaris system with the full combination of Installed Packages Installed Patches Applied Configuration

Hi , Given the following LLVM IR : define i32 @foo(i32 %l) #0 { entry: %add = add nsw i32 %l, 3 ret i32 %add } ; Function Attrs: nounwind ssp uwtable define i32 @boo(i32 %k) #0 { entry: %call = call i32 @foo(i32 %k) ret i32 %call } ; Function Attrs: nounwind ssp uwtable define i32 @main() #0 { entry: %add = add nsw i32 1, 2 %add2 = add nsw i32 2, %add ret i32 %add2 } I want to be able

...commonly done. I've seen it described internally as 'poor man's LTO', which seemed a bit sad to me as it's far more flexible. The process I use for compiling projects is roughly: - clang *.cpp -emit-llvm -o *.bc - llvm-link directory/* -o directory.tmp.bc - opt directory.tmp.bc -internalise -internalize-public-api-list=foo -globaldce -O3 -o directory.bc - recurse Compile each source file to bitcode, each directory to a linked & optimised bitcode file. The internalize stuff effectively renders some functions static partway through the process and isn't necessary. This is recur...

...ave any predecessors or successors , such that > I can make a cfg to figure out who’s calling whom ? > > > > Is there a way I can achieve this ? > > The fact that main is the entry point is not known to LLVM (except in a > couple of places that special-case main, such as the internalise pass), > because it is an artefact of C/C++, not a generic property. On most *NIX > platforms, the real entry point for a program is something like __start or > _start, which then call main. In most compilation units, there is no > single entry point, because they do not contain the p...

On 3/28/23 20:16, Matthew Wilcox wrote: ... >> + if (!get_page_unless_zero(vmf->page)) >> + return 0; > > From a folio point of view: what the hell are you doing here? Tail > pages don't have individual refcounts; all the refcounts are actually ohh, and I really should have caught that too. I plead spending too much time recently in a somewhat more driver-centric

...successors , such >> that I can make a cfg to figure out who’s calling whom ? >> > >> > Is there a way I can achieve this ? >> >> The fact that main is the entry point is not known to LLVM (except in a >> couple of places that special-case main, such as the internalise pass), >> because it is an artefact of C/C++, not a generic property. On most *NIX >> platforms, the real entry point for a program is something like __start or >> _start, which then call main. In most compilation units, there is no >> single entry point, because they do n...

> I’m just wondering why not have a ‘br’ to an exit basic block instead of ‘ret’ mid-stream of instructions. > Have you considered this approach instead? Thanks for bringing this up. Yes. In fact, I tried that approach/pattern first. Simply, you create default exit block and a local return variable (to track return value) per function, but it requires extra flags and variables to track

Hi everyone, I thought long and hard (ok, not *that* long) about whether or not to crosspost this to icecast-dev. In the end I decided not to since this isn't about an Icecast or Xiph project. My name is Geoff Shang and I've been an enthusiastic user of Icecast for a long time. I am also the chief tech guy for a project called ACB Radio (http://www.acbradio.org), which is run by

...fixed bugs in that >area of the code. (-: > >>In any case a lot of this stuff will move around a bit as the >>authenticaion subsystem starts passing back info - like the >>unix_username they got and everything they need for a vuser token. >>With that change I'll internalise all this behind the interface. >> >>I'll have a look at all of this when I've got a little less on my plate. >> > >OK - I'll send you any patches if I get around to it over the >next couple of days. > > >Tim. > -- Simon Travers-Jones Network Eng...