search for: howtoreleasellvm

...e release process. See >> docs/SphinxQuickstartTemplate.rst to get up and running fast. >> > > I sure can. I thought there was already a doc on that at LLVM about that. > If there is, would be good to start there. > > AFAIK, the closest we have is <http://llvm.org/docs/HowToReleaseLLVM.html>, which details basically what the release manager has to do (i.e., the audience is LLVM developers, and release managers in particular). I really liked the article you linked because it seemed to be targeted at an audience of external developers and packagers, for whom we don't (AFAIK)...

...gt; second fixes the CPU cache incoherency problem. Without this patch, XRay > will intermittently fail to patch or unpatch some sleds (depending on > whether their code is in CPU cache or not). > > Is there any chance we can get these patches to 4.0? This page > http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules says that > "release manager, the official release testers or the code owners" may > approve cherry-picking to release branch from trunk. AFAIK, you are code > owners for XRay and ARM. I don't know who are the release manager or > official release...

Folks, I'm in the process of updating this page: http://llvm.org/docs/HowToReleaseLLVM.html which had its last review in the middle ages. In particular, I'm removing "dragonegg" from the list of requirements, changing the "build" instructions to use the test-release script (by pointing it to the right doc [1]), and updating the list of requirements. CMake i...

...urage someone in the community who knows git better than me to create the branches. Testers: If you wish to volunteer to be a tester, please let me know! :-) The release tags are now available for check-out. The branch and tag structure in SVN is detailed on this webpage: http://llvm.org/docs/HowToReleaseLLVM.html There is a script which you can run to build the compiler and have it ready to run the nightly tests: utils/release/test-release.sh Testers need to verify that there are no regressions with respect to LLVM 2.8. Please run the test suite to verify this. (Tanya, I lost the script that does t...

Vedant, Thanks for building the packages before. Could you detail what's required to build these binaries on macOS so that someone else could replicate it? Thanks, Tobias On Mon, Oct 14, 2019 at 8:29 PM Vedant Kumar via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Gio, > > I prepared the macOS packages for the past few releases, but have less time to keep up with

...cy problem. Without this patch, XRay >>> will intermittently fail to patch or unpatch some sleds (depending on >>> whether their code is in CPU cache or not). >>> >>> Is there any chance we can get these patches to 4.0? This page >>> http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules says that >>> "release manager, the official release testers or the code owners" may >>> approve cherry-picking to release branch from trunk. AFAIK, you are code >>> owners for XRay and ARM. I don't know who are the release manager o...

Hi Bill, > The release tags are now available for check-out. The branch and tag structure > in SVN is detailed on this webpage: > > http://llvm.org/docs/HowToReleaseLLVM.html can you please explain explicitly where to get hold of the branch and tags. The branch seems to live at http://llvm.org/svn/llvm-project/llvm/branches/release_29 but there seems to be nothing relevant under http://llvm.org/svn/llvm-project/llvm/tags Thanks, Duncan.

Compiling LLVM with gcc, 4.3 and upwards, seems to give compile warnings. Is there any canonical gcc version that should be used (for building trunk)? >From http://llvm.org/docs/HowToReleaseLLVM.html#release-build: The builds of llvm, clang, and dragonegg must be free of errors and warnings in Debug, Release+Asserts, and Release builds. The table below specifies which compilers are used for each Arch/OS combination when qualifying the build of llvm, clang, and dragonegg. [...] x86...

On 26 May 2013 03:03, Sean Silva <silvas at purdue.edu> wrote: > AFAIK, the closest we have is <http://llvm.org/docs/HowToReleaseLLVM.html>, > which details basically what the release manager has to do (i.e., the > audience is LLVM developers, and release managers in particular). I really > liked the article you linked because it seemed to be targeted at an > audience of external developers and packagers, for whom...

Hello, I'm converting HowToReleaseLLVM.html, expect to finish today. -- Alexander Zinenko On 6 December 2012 21:14, Sean Silva <silvas at purdue.edu> wrote: > FYI I am bout to convert LangRef. it should be done by the end of > today. Please keep me up to date with any work you do on the other > documents. > > --...

...so fails > to build with gcc 4.9). > > 2. Accidental change of libLLVM's DT_SONAME from libLLVM-3.4 > libLLVM-3.4.1.so > > I will also accept any other bug-fixes that people want to submit as > long as they conform to the rules of stable releases: > http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules > > In order to get these fixes out quickly, we will have a very short period > for nominating bug-fixes, followed by our usually stable release testing > phase. > > Here is an approximate schedule: > > Monday, May 12 to Thursday, May 15: Nominate bu...

...>>> will intermittently fail to patch or unpatch some sleds (depending on >> >>> whether their code is in CPU cache or not). >> >>> >> >>> Is there any chance we can get these patches to 4.0? This page >> >>> http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules says >> >>> that >> >>> "release manager, the official release testers or the code owners" may >> >>> approve cherry-picking to release branch from trunk. AFAIK, you are >> >>> code >> >>>...

FYI I am bout to convert LangRef. it should be done by the end of today. Please keep me up to date with any work you do on the other documents. -- Sean Silva On Thu, Dec 6, 2012 at 12:12 PM, Sean Silva <silvas at purdue.edu> wrote: > Thanks for doing this. > > I was planning on finishing these by this weekend. If you are planning > on taking significantly longer than that I

Hi, I would like to propose a few changes to the LLVM release process. The current process is documented here: https://llvm.org/docs/HowToReleaseLLVM.html There are two parts to this proposal. The first is a list of clarifications, which are things we are currently doing that aren't documented. The second is a list of changes which would actually modify how releases are currently managed. *** Proposed Clarifications *** ** Release m...

On Sun, May 26, 2013 at 5:57 AM, Renato Golin <renato.golin at linaro.org>wrote: > On 26 May 2013 03:03, Sean Silva <silvas at purdue.edu> wrote: > >> AFAIK, the closest we have is <http://llvm.org/docs/HowToReleaseLLVM.html>, >> which details basically what the release manager has to do (i.e., the >> audience is LLVM developers, and release managers in particular). I really >> liked the article you linked because it seemed to be targeted at an >> audience of external developers and pack...

...4.9 (This is not a regression, 3.4 also fails to build with gcc 4.9). 2. Accidental change of libLLVM's DT_SONAME from libLLVM-3.4 libLLVM-3.4.1.so I will also accept any other bug-fixes that people want to submit as long as they conform to the rules of stable releases: http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules In order to get these fixes out quickly, we will have a very short period for nominating bug-fixes, followed by our usually stable release testing phase. Here is an approximate schedule: Monday, May 12 to Thursday, May 15: Nominate bug-fixes for the 3.4 branch. Friday, M...

The usual procedure is to make time-based releases. So - "release trunk and make sure it's stable enough" plus - fix any outstanding regressions. There is some text wrt this: http://llvm.org/docs/HowToReleaseLLVM.html#release-qualification-criteria On Fri, Dec 13, 2013 at 11:08 AM, "C. Bergström" <cbergstrom at pathscale.com> wrote: > On 12/13/13 01:58 PM, Bill Wendling wrote: >> >> That’s a long laundry list of bugs there. It would be great to have them >> fixed, but t...

...bit to get the release out soon since its been delayed so far. The release team has done our qualifications and we think its of high quality and ready to go. As this is the last pre-release, we only accept fixes for absolutely critical bugs as defined by our release criteria: http://llvm.org/docs/HowToReleaseLLVM.html#release-qualify If you are able to test this pre-release, we ask that you try the following: To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre-compiled llvm-gcc or re-compile it yourself. 2)...

Hi all, I'm working up some changes in the way LLVM is released. Attached is the latest HTML file for HowToReleaseLLVM.html. The major change is in how we do branching and tagging. I want to use a hierarchical version of tags for the various release candidates and final release. The structure of the tags would be something like this. The 2.9 release branch: https://llvm.org/svn/llvm-project/llvm/branch/release_2...

...ds (depending >> >> >>> on >> >> >>> whether their code is in CPU cache or not). >> >> >>> >> >> >>> Is there any chance we can get these patches to 4.0? This page >> >> >>> http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules says >> >> >>> that >> >> >>> "release manager, the official release testers or the code owners" >> >> >>> may >> >> >>> approve cherry-picking to release branch from trunk. AFAIK,...