search for: ctx2

...t main() { // vars string Message; raw_string_ostream Stream(Message); DiagnosticPrinterRawOStream DP(Stream); LLVMBool Result; // create blank modules and contexts LLVMContext *ctx1 = new LLVMContext; Module* module1 = new Module("module1", *ctx1); LLVMContext *ctx2 = new LLVMContext; Module* module2 = new Module("module2", *ctx2); LLVMContext *ctx3 = new LLVMContext; Module* module3 = new Module("module3", *ctx3); // fill modules llvm::Function::Create(llvm::FunctionType::get(Type::getInt32Ty(*ctx1), false), llvm::Function::Ex...

...ing Message; > raw_string_ostream Stream(Message); > DiagnosticPrinterRawOStream DP(Stream); > LLVMBool Result; > // create blank modules and contexts > LLVMContext *ctx1 = new LLVMContext; > Module* module1 = new Module("module1", *ctx1); > LLVMContext *ctx2 = new LLVMContext; > Module* module2 = new Module("module2", *ctx2); > LLVMContext *ctx3 = new LLVMContext; > Module* module3 = new Module("module3", *ctx3); > // fill modules > llvm::Function::Create(llvm::FunctionType::get(Type::getInt32Ty(*ctx1), false)...

Hello openssh@ I thought about sftp's reget/reput commands. Several days ago, Damien Miller write to tech at openbsd.org (it was reply for my letter): > Herein lies a problem which is not easy to detect or solve. For > performance reasons, the sftp client does pipelined reads/writes when > transferring files. The protocol spec allows for a server to process > these requests out

...Context(); // codes using only globa_context (get Int32ty() or StructType::create or etc...) } Q2) What situation do I need to create multiple `LLVMContext`s? I don't know the situation used multiple `LLVMContext`s. For example, { { llvm::LLVMContext ctx1; // some code } { llvm::LLVMContext ctx2; // some code } { llvm::LLVMContext ctx3; // some code } } or { llvm::LLVMContext ctxs[] = {....} // some code } I'd like to know the appropriate usage of LLVMContext. Thak you very much for reading. Sincerely, Ryo -------------- next part -------------- An HTML attachment was scrubbed......

...hirdMessage() } define i32 @main() nounwind { entry: ; alloca space for the contexts. %ctxSize = call i64 @llvm.context.size() %p0 = alloca i8, i64 %ctxSize %mainCtx = bitcast i8* %p0 to {}* %p1 = alloca i8, i64 %ctxSize %ctx1 = bitcast i8* %p1 to {}* %p2 = alloca i8, i64 %ctxSize %ctx2 = bitcast i8* %p2 to {}* ; Stacks for the contexts %stack1 = alloca i8, i64 4096 %stack2 = alloca i8, i64 4096 ; Create contexts for co1 and co2. call void @llvm.makecontext({}* %ctx1, void({}*, {}*)* @co1, i8* %stack1, i64 4096, {}* %mainCtx, {}* null) call void @llvm.makecontext({}...

Hi, I came up with the following patch while trying to figure out a good solution for the situation described in Debian bug #871987[1]. In short, OpenSSL in Debian unstable has disabled TLSv1.0 and TLSv1.1 *by default*. That means that unless an application requests otherwise, only TLSv1.2 is supported. In the world of e-mail this is seemingly an issue, as there are still way too many old clients

Hi, few months ago I started a thread about running PWGL under wine. PWGL is a " free cross-platform visual language based on Common Lisp, CLOS and OpenGL, specialized in computer aided composition and sound synthesis. " http://www2.siba.fi/PWGL/index.html However, because I had to use winetricks to install Microsoft Visual C++ 2005 (it's needed by PWGL), and the many errors that I

OpenSSH Developers, I'm researching whether or not OpenSSH is a viable commercial alternative to F-SECURE SSH or SSH.COM's ssh, but I'm not getting the kind of results that I expected from a "Non patent encumbered ssh client". When I attempt to build OpenSSH against an OpenSSL build without rc5, idea, or rsa it bombs since OpenSSL doesn't place the header files in the

...id } define i32 @main() nounwind { entry: ; alloca space for the context descriptors. %ctxSize = call i64 @llvm.context.size() %p0 = alloca i8, i64 %ctxSize %mainCtx = bitcast i8* %p0 to {}* %p1 = alloca i8, i64 %ctxSize %ctx1 = bitcast i8* %p1 to {}* %p2 = alloca i8, i64 %ctxSize %ctx2 = bitcast i8* %p2 to {}* ; Stacks for the contexts. If llvm.stackgrowsdown returns true, we need ; pointers to the highest addresses of the stack areas rather than the ; lowest addresses. %growsdown = call i1 @llvm.stackgrowsdown() %stackbuf1 = alloca i8, i64 4096 %stackhi1 = geteleme...

Kenneth Uildriks <kennethuil at gmail.com> wrote: > As I see it, the context switching mechanism itself needs to know > where to point the stack register when switching.  The C routines take > an initial stack pointer when creating the context, and keep track of > it from there.  If we don't actually need to interoperate with > contexts created from the C routines, we have

...break;=0A= + }=0A= + }=0A= + } else=0A= + DEBUG(1,("failed to lookup_usergroups for = %d\n",(*info)[i].user_rid));=0A= + } else /* force primary group */=0A= + (*info)[i].group_rid =3D lp_winbind_primary_group();=0A= + }=0A= }=0A= =0A= talloc_destroy(ctx2);=0A= @@ -263,10 +287,12 @@=0A= WINBIND_USERINFO *user_info)=0A= {=0A= CLI_POLICY_HND *hnd;=0A= - NTSTATUS result;=0A= + NTSTATUS result, status;=0A= POLICY_HND dom_pol, user_pol;=0A= BOOL got_dom_pol =3D False, got_user_pol =3D False;=0A= SAM_USERINFO_CTR *ctr;=0A= + uint32 num_gro...

Gerald, No worries. This patch is required if your using Rational ClearCase and you don't want everyone to have access to it. It's to fix a brokenness (IMO) within ClearCase, and maybe other programs. Our windows primary group has 10k+ users... I will shoot it off to Rational, so they can provide it to there customers. I was hoping it could be applied to the main tree so I could just