search for: subprojects

Hi Tanya, As discussed in the past few weeks in the llvm-dev thread “RFC: Proposing an LLVM subproject for parallelism runtime and support libraries”, we would like to start a new LLVM subproject called parallel-libs (a kind of a parallel cousin to compiler-rt), and I was told you were the one to contact in order to get it created. The charter for the project is included below. Are you able to

Thanks for your help, Tanya! I haven't created the project in SVN yet. Am I able to set it up myself on the LLVM servers, or does someone else need to do that part? I'll be glad to volunteer to moderate the new mailing lists. We will want a website. I think there will be a top-level docs directory for the project and a docs directory for each subproject. To begin with, StreamExecutor

...under Debian6-i386 (gcc/g++: 4.4.5). The compiler back trace is attached. Please fix it/them and repost. Or, 64b system is a requirement? Thank you Chuck llvm[4]: Compiling TypeRuntime.cpp for Release+Asserts build (PIC) cc1plus: warnings being treated as errors /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:52: error: integer constant is too large for ‘long’ type /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:99: error: integer constant is too large fo...

The parallel-libs LLVM subproject is now set up and ready for code development. This is the subproject that is meant to house the StreamExecutor parallel runtime library, possibly the OpenMP target runtime libraries, and other libraries devoted to handling parallelism in LLVM (see the README currently checked into the parallel-libs base directory for the project charter). The parallel-libs

...back trace is attached. > Please fix it/them and repost. > > Or, 64b system is a requirement? > > Thank you > > Chuck > > llvm[4]: Compiling TypeRuntime.cpp for Release+Asserts build (PIC) > cc1plus: warnings being treated as errors > /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:52: > error: integer constant is too large for ‘long’ type > /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:99: > error: integer constant is...

On 6/11/20 3:32 AM, Andrzej Warzynski wrote: > > > On 11/06/2020 00:49, Michael Kruse wrote: >> Am Mi., 10. Juni 2020 um 10:04 Uhr schrieb Doerfert, Johannes via >> flang-dev <flang-dev at lists.llvm.org>: >>> I'm not against a subproject *but* if we also move the existing >>> llvm/lib/Frontend stuff, that would introduce a dependence from

Am Mi., 10. Juni 2020 um 10:04 Uhr schrieb Doerfert, Johannes via flang-dev <flang-dev at lists.llvm.org>: > I'm not against a subproject *but* if we also move the existing > llvm/lib/Frontend stuff, that would introduce a dependence from > llvm-core to this project, which I think is uncommon. We could also have > both. At the end of the day it depends on the benefit we would

...t; trunk/llvm/... > trunk/stacker/... > trunk/java/... > Fortunately, with SVN, making such a change isn't hard and its tracked > in the commits. Anyone object or have other ideas in this realm? I strongly dislike this approach. This is particularly bad because we have many subprojects. Lots of these subprojects are only loosly coupled to LLVM: things like llvm-tv, llvm-java, llvm-poolalloc, etc. I think that it is natural for subprojects to go through various development phases and to sink or swim based on their own merits and the contributor base around them. Our goal sho...

Dear All, We have a new release of Clang with SAFECode technology for detecting memory safety errors. Memory safety checking (SAFECode for short) can be turned on with a single command line switch to clang/clang++. The SAFECode techniques do not change the behavior of the clang/clang++ compilers in any way when the switch is turned off, so this can be used as a drop-in replacement for

On 6/11/20 4:04 PM, James Y Knight wrote: > I think the expectation is that LLVM remains at the bottom of the > dependency tree, with frontend-support depending on LLVM, and Clang and > Flang depending on frontend-support (and LLVM). > > Not everything which makes sense to share between clang and flang makes > sense to be part of llvm core. E.g., implementation of a

...hecks. When running checks like check_c_compiler_flag, check_cxx_compiler_flag or check_library_exists, CMake caches the resulting variable and doesn't run the check again. The problem is that in LLVM, each subproject uses different variable names for results of these checks. For example, most subprojects check if pthread is available and store the result in: COMPILER_RT_HAS_LIBPTHREAD (compiler-rt) LIBCXX_HAS_PTHREAD_LIB (libc++) LIBCXXABI_HAS_PTHREAD_LIB (libc++abi) LIBUNWIND_HAS_PTHREAD_LIB (libunwind) HAVE_LIBPTHREAD (llvm) This means that even though this check would ideally be performed just...

Hi, I have tried to compile LLVM with Visual C++. Some subprojects work now. Other subprojects require the file "configure.lib". So I tried to compile the project "Configure". It could be built successfully, but the file "configure.lib" is not generated. So, what is the problem here ? Can somebody help me to fix that ? Thanks and re...

...ocument: https://reviews.llvm.org/D24167 <https://reviews.llvm.org/D24167> ? TLDR: The answer is no: you have to see it as it is today, i.e. a single SVN repo containing all the sub-projects, and “exports” in individual repositories. The same thing after: a single git repo containing all the subprojects side-by-side and the *same* “exports” in individual repositories. > If so that should work for us. I'm more > concerned about the case where the individual repositories' histories > were interwoven into a single repository and the individual repositories > went away. > &...

...tps://reviews.llvm.org/D24167 ? >> >> TLDR: The answer is no: you have to see it as it is today, i.e. a >> single SVN repo containing all the sub-projects, and “exports” in >> individual repositories. > >> The same thing after: a single git repo containing all the subprojects >> side-by-side and the *same* “exports” in individual repositories. > > Sorry, I sent my earlier reply today before I intended to. > > After going back and reading the proposal again, I think I understand > the plan. I haven't used the SVN repository for years so I was...

...for the llgo subproject. The frontend would live in the LLVM svn repository and if checked out into tools/llgo would build as part of the regular LLVM build (with CMake only). We would be keeping llgo compatible with top-of-tree LLVM, although I imagine this would be less burdensome than the other subprojects as llgo is written in Go and depends on the Go bindings previously contributed to LLVM. llgo depends on certain third-party components, namely a copy of the Go standard library (libgo), a Go program analysis library (go.tools) and two library dependencies of the standard library (libbacktrace and...

I've put together a proposed "charter" for this new project, which I am calling parallel_utils (although I'm very open to suggestions for a better name). The text of my charter is below, and I welcome any input on how it can be improved. ===================================================== LLVM Parallel Utils Subproject Charter

Hello, is it possible to compile just an subproject? For example, just llc or lli? Cheers. Beckert. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120503/c20aa7b1/attachment.html>

Dear all, I''m using redmine and in welcome page, it displays all projects and subprojects. I want to hide all subprojects and display parent projects only. Please help me! -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emai...

Hi all, Don't suppose VMKit could be added to the set of subprojects with official git mirrors? Please and thank you! :) ~Will

...nt* point to understand, so let me try to be really clear about the current state of the world and the state of the world under the two "move to git" proposals. Today, all commits ultimately end up in SVN. Our SVN is a effectively a monorepo, so today, a single commit can touch multiple subprojects. How you get the commit into SVN is your business. Maybe you can hack git-svn somehow to do the atomic commit. (If this is possible, it's beyond my ken.) Alternatively you can just commit via SVN. If you're a git user, I wrote a hacky script [1] that cherry-picks commits from the existi...