search for: thellvm

> On Jun 22, 2017, at 12:00 PM, Tom Stellard <tstellar at redhat.com> wrote: > > On 06/21/2017 03:22 PM, Tanya Lattner via llvm-dev wrote: >> LLVMers, >> >> >> >> TheLLVM.org <http://LLVM.org>server which hosts SVN, GIT mirror, documentation, and the mainLLVM.org <http://LLVM.org>website is moving to a new server on June 24th. As a result of the move commit access will be locked out beginning 09:00PDT on the 24th. We hope to have the move complete and...

...ck frame of the currently executing function, to be automatically released when this function returns to its caller. when using come c code like void myfunc(void){ int i=4; double d[i]; } the ir shows enclosing llvm.stackSave & restore constructs, enclosing the alloca related to 'd'. thellvm.stacksafe reference explains: This intrinsic is used to remember the current state of the function stack... In practice, this pops any alloca blocks from the stack that were allocated after the llvm.stacksave was executed. shouldn't the alloca block related to 'd' be automatically rele...

LLVMers, The LLVM.org <http://llvm.org/> server which hosts SVN, GIT mirror, documentation, and the main LLVM.org <http://llvm.org/> website is moving to a new server on June 24th. As a result of the move commit access will be locked out beginning 09:00PDT on the 24th. We hope to have the move complete and commit access restored to everyone in a timely manner, however, a move of

Hi Amara, My reasons for preferring the switch to happen after the release branch is based on the following observations: * As far as I can see, the projects and products following top-of-trunk tend to test much more extensively than the testing that happens for llvm.org<http://llvm.org> releases. I expect that the llvm.org<http://llvm.org> release testing won’t find potential