search for: codebases

Dear Developers, I compile a OpenCL kernel, FFT, in AMDAPP SDK v2.5 using clang 3.8 + libclc and assembling the code with lld (The LLVM linker). The assembly code contains the following assembly codes (and lots of other similar format assembly) that fails to be parsed by AMDGPUAsmParser. It seems to me that both are valid instructions after looking at the SI instruction spec. s_mov_b32 s0,

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, what is

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 Sanitizer less useful, because now the value

I am running Photomatix Pro 3 (trial version) on Unbuntu 10.04. no problem installing or opening. I have an issue in tone mapping. Sliders. replaced with red "X" in a white box. Below is the detailed text of the error: "Parameter is not valid" See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. **************

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',

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:

We''re working on rails application for a client that needs to be deployed under a variety of domain 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

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 w...

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 that, there were discussions about lower_case, camelCase, m_ prefix, and each argument seems as convincing as others. I'm not sure what is the

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.

Hi everyone, This is Ankit; currently final-year Computer Science undergrad at Panjab University, India. I am well versed in C++ and have a pretty decent understanding 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

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

On Jan 5, 2011, at 6:34 AM, Óscar Fuentes wrote: > arrowdodger <6yearold at gmail.com> writes: > >>> Or to say it with other words: patches welcome. >> >> So, how should i proceed? Make CMake-generated config to be identical to >> autotools one? > > That would be a good thing. > > Please note that some checks are a bit tricky. A function that

Hello, interesting to hear. What version of NUT, 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

On Mon, Jun 10, 2019 at 6:27 PM Michael Platings <Michael.Platings at arm.com> wrote: > Hi Rui, > > > > As per the provisional plan [1] we’re still at step 1: improving git > blame. The status of this is that there are some fairly mature patches in > the Git project’s queue [2], and I’m hopeful that it will be accepted in > something close to its current form. >

This looks really great to me Rui, and I’m also pleased to see the positive comments on the review thread. Thank you for driving this forward! -Chris > On Jul 4, 2019, at 9:50 PM, Rui Ueyama <ruiu at google.com> wrote: > > Hi all, > > I wrote a tool <https://reviews.llvm.org/D64123> to batch-rename variable names so that they are in camelCase, and I applied the

Eric Christopher <echristo at apple.com> writes: >>> 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

Hi Rui, Is your tool in a good state to be run on people's downstream repositories? It would be nice to be able to update variable names there too at the same time. James On Tue, 9 Jul 2019 at 08:24, Rui Ueyama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Thanks, Chris. > > Looks like everybody is at least mildly comfortable with my variable name > renaming change,

>> LLVM handles function pointers currently. It just overwrites the >> first >> instruction of the old code with an unconditional branch to the new >> implementation. Thus, any code branching to the old location will >> still >> work. > > yes, that works so long as one has write access to the text section > (or the > code is otherwise in a

Back from vacations, and before I dive into real-life work, I went over some ideas and notes from the NUT for Windows effort. Now they should be tracked at https://github.com/orgs/networkupstools/projects/2/views/1 and community help is welcome :) I probably forgot or missed some caveats - so feel free to post issues for this project if you think of some more... Jim On Thu, Jun 23, 2022, 23:52