search for: codebase

...legal s_mov_b32 s0, 0xfe5163ab ^ sop1-playground.s:1:25: error: failed parsing operand. s_mov_b32 s0, 0xfe5163ab ^ The part of stack dump: ... #9 0x4711ee (anonymous namespace)::AMDGPUOperand::setModifiers(unsigned int) /mnt/dm-0/codebase/Compilers/LLVM/llvm/lib/Target/AMDGPU/AsmParser/AMDGPUAsmParser.cpp:185:21 #10 0x46ff6a (anonymous namespace)::AMDGPUAsmParser::parseOperand(llvm::SmallVectorImpl<std::unique_ptr<llvm::MCParsedAsmOperand, std::default_delete<llvm::MCParsedAsmOperand> > >&, llvm::StringRef) /mn...

I am attempting to bring R-3.0.2 functionality into a project with a very large C++ codebase. The existing codebase already has a LENGTH function defined. R also defines a LENGTH function. I first compiled R as a shared library and linked it into this existing codebase, along with RInside. When I run a parseEvalQ with a linear model command it will stack dump. Looking at the backtrace,...

Hi Apelete, Thanks for trying to help cleanup the LLVM codebase of Clang Static Analyzer warnings. But it seems a lot of the fixes that are being proposed are somewhat mechanical and may be doing the wrong thing in a few ways. * Initializing variables that are only used when initialized through some existing codepath - this can make tools like Memory Sanitize...

...Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- Photomatix Assembly Version: 3.0.3799.2763 Win32 Version: 3.0.3799.2763 CodeBase: file:///C:/Program%20Files/PhotomatixPro3/PhotomatixPro.exe ------------------------------------...

Hi, I am trying to test my project and get the code coverage with a version of clang compiler that was built from the latest llvm/clang codebase. It worked for a while. But today, after I updated my local checkout, and re-build llvm, clang and compiler-rt, when I test my project again, I got the errors with undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs', 'llvm_gcda_emit_function', and 'llvm...

Hi folks, Git is on its way to learning how to ignore commits, allowing us to do variable renaming and other small refactorings without breaking git blame. It's like git-hyper-blame [1] but significantly more powerful as it uses fuzzy matching to match lines, including lines that may have been split or joined. A preview release of Git with this new feature is at:

...main names and needs the ability to load custom configurations for the database, parts of the docroot, caching, etc. based on the site we''re serving. We use mongrel to host some other single domain apps and would like to do so here too. We''d like to not have to deploy the codebase multiple times either (since it''s identical) so we''re trying to figure out a way maybe to load each instance into mongrel with different params and then let the instance configure itself. Does anyone have experience using mongrel in this way or similar? Thanks, John

John, > This is not categorically true, no. When we make changes that require large-scale updates for downstream codebases, we do so because there’s a real expected benefit to it. For the most part, we do make some effort to keep existing source interfaces stable. While I’m at a loss to find a documented policy, I recall this thread (http://lists.llvm.org/pipermail/llvm-dev/2020-February/139207.html) where this claim...

...ed to get at least a rough consensus to do that. What is a way to proceed? On Sat, May 25, 2019 at 3:00 PM Chris Lattner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Michael, > > I’m still very interested in seeing a change here. If someone is > interested in seeing a codebase using the proposed camelBack convention for > variables names, the MLIR codebase is public > <https://github.com/tensorflow/mlir> and uses it. > > If you’re curious to see what this looks like in practice, there are lots > of examples in the codebase, here is an example .cpp fi...

Does anyone know what version of Asterisk Switchvox uses, and if it is modified in any way? FWIW, I am dealing with a provider that claims compatibility with Switchvox but not Asterisk for their SIP trunking service.

...ng of sockets. I successfully completed GSoC last year for IDI, project titled - Google App Module for ATutor. Quite recently, I have been working on the project idea - Replacing Xapian socket code with ZeroMQ. This is to inquire about what do I do next? Is there some documentation for the Socket codebase that I can use as a reference or any open tickets/patches, that I can work on? Any help/suggestions is highly appreciated. -- *Wishes.* *Ankit Bhatnagar.* *IRC Nick : ankit* *GTalk : ankitbhatnagar2012* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://li...

Hi, I am writing tool to simplify automated refactorings. One of prerequisites is have clean codebase, so a refactorer can be simple and created formatting inconsistencies can be eliminated by formatter. My plan to keep codebase clean is first run a cleanup systemwide, then keep it by hook/ periodicaly rerunning cleanup. I put it for now here. https://github.com/neleai/stylepp I ran a scripts t...

...Or cleanup both headers from unused stuff by Eric's >> suggestion? > > I'm not sure this is a good idea (not that it is bad either). Murphy's > Law says that a function that you remove today will be used tomorrow. I meant literally functions that aren't used in the codebase. No need to look for them if we're not using them. -eric

...UT, what way of installation on Windows, what sort of UPS (USB or some other)? Asking because this info is lacking and currently there are a few variants to consider: * an MSI package based on NUT v2.6.5 (last released about 9 years ago as "2.6.5-6"), * results of re-integration of that codebase into current NUT master (some months after 2.8.0 release), with regular CI-made archives of binary build "installation" directories which so far lack an installer (nobody looked at it yet) and have some other caveats and bits of known-missing code. In particular, lack of the installer may...

....com> > *Sent:* 07 June 2019 08:42 > *To:* Chris Lattner <clattner at nondot.org> > *Cc:* Michael Platings <Michael.Platings at arm.com>; llvm-dev at lists.llvm.org; > nd <nd at arm.com> > *Subject:* Re: [llvm-dev] RFC: changing variable naming rules in LLVM > codebase > > > > This thread is not active for a while, but I'm still interested in seeing > a change. > > > > Reading through this thread, looks like we can agree that we want to > change the local variable naming scheme so that they start with a lowercase > letter. Bes...

...; Cc: Michael Platings <Michael.Platings at arm.com <mailto:Michael.Platings at arm.com>>; llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>; nd <nd at arm.com <mailto:nd at arm.com>> > Subject: Re: [llvm-dev] RFC: changing variable naming rules in LLVM codebase > > > > This thread is not active for a while, but I'm still interested in seeing a change. > > > > Reading through this thread, looks like we can agree that we want to change the local variable naming scheme so that they start with a lowercase letter. Besides th...

...from unused stuff by Eric's >>> suggestion? >> >> I'm not sure this is a good idea (not that it is bad either). Murphy's >> Law says that a function that you remove today will be used tomorrow. > > I meant literally functions that aren't used in the codebase. No need to > look for them if we're not using them. Sorry, bad wording. What I'm trying to say is that if you remove a function check just because it is not used by the codebase today maybe some programmer will need that function tomorrow. And adding an autoconf check is far from trivi...

...y variable name > renaming change, so I'll to submit that change to lld subdirectory soon. If > you have any objections, please let me know. Note that this is not the end > of my effort but actually the beginning of it. As Chris said, I believe we > should do this to the entire LLVM codebase. I'm planning to do that > directory-by-directory basis. > > On Tue, Jul 9, 2019 at 2:03 PM Chris Lattner <clattner at nondot.org> wrote: > >> This looks really great to me Rui, and I’m also pleased to see the >> positive comments on the review thread. Thank you f...

...usly had access to write it there. In any case, the JIT can use mprotect to map the page writable if it has to. > a major detractor at this point for me and LLVM, is that it is > written in > C++, and I am not so good with C++, and I am otherwise not so > fammiliar with > the codebase... That sounds like an excellent reason to get more familiar with C++ and the LLVM code base. It's usually better to try to grow your capabilities than to limit what you can do by avoiding learning new things ;-) LLVM has extensive documentation at http://llvm.org/docs > (as for my...

...ues for this project if you think of some more... Jim On Thu, Jun 23, 2022, 23:52 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Hello all, > > After a hectic month in private life, as a byproduct I've got a viable > merger of last released NUT 2.6.5 based Windows-ready codebase (thanks to > the giants active a dozen years ago, on whose shoulders I stood today) and > modern 2.8.x/master, fixing the merge conflicts and build warnings. Some > details were tracked in discussion of > https://github.com/networkupstools/nut/issues/5 > > There are caveats, e.g...