search for: 20170507

Hi, I got a forced update when pulling today. If I merge master to a local branch, I get a bunch of add/add conflicts. This same commit exists under several hashes: https://github.com/llvm-project/llvm-project-20170507/commit/687841777ef505 https://github.com/llvm-project/llvm-project-20170507/commit/74725885552 Did someone push -f to the monorepo after doing branch surgery? Maybe there was a PSA somewhere that I missed? Thanks, Nico -------------- next part -------------- An HTML attachment was scrubbed... UR...

While playing with sanitizer in a downstream project, I found out this. /Users/davide/work/llvm-monorepo/llvm-project-20170507/llvm/tools/llvm-mc-assemble-fuzzer/llvm-mc-assemble-fuzzer.cpp:207:32: error: reference to type 'std::unique_ptr<MCCodeEmitter>' could not bind to an lvalue of type 'llvm::MCCodeEmitter *' UseDwarfDirectory, IP, CE, MAB, ShowInst)); ^~ /...

...d bitrot if it’s not built in any of the bots. George > On May 4, 2018, at 2:53 PM, Davide Italiano via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > While playing with sanitizer in a downstream project, I found out this. > > /Users/davide/work/llvm-monorepo/llvm-project-20170507/llvm/tools/llvm-mc-assemble-fuzzer/llvm-mc-assemble-fuzzer.cpp:207:32: > error: reference to type 'std::unique_ptr<MCCodeEmitter>' could not > bind to an > lvalue of type 'llvm::MCCodeEmitter *' > UseDwarfDirectory, IP, CE, MAB, ShowInst)); >...

As a follow up to https://reviews.llvm.org/D20217 I would like to use lto/thinlto to refine when a symbol is marked as local/preemptable. I'm not very familiar with lto though so would appreciate some guidance about how best to go about this. Regards Sean Fertile

...ny of the bots. > > George > >> On May 4, 2018, at 2:53 PM, Davide Italiano via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> While playing with sanitizer in a downstream project, I found out this. >> >> /Users/davide/work/llvm-monorepo/llvm-project-20170507/llvm/tools/llvm-mc-assemble-fuzzer/llvm-mc-assemble-fuzzer.cpp:207:32: >> error: reference to type 'std::unique_ptr<MCCodeEmitter>' could not >> bind to an >> lvalue of type 'llvm::MCCodeEmitter *' >> UseDwarfDirectory, IP, CE, MAB, ShowInst)); &...

I'm still somewhat unclear about what you mean by "metadata record entry at the beginning of the block". I understand that I can make a MetadataRecord that contains the pid/tid since a metadata record contains 16 bytes. However, I don't understand what do you mean by the "beginning of the block". Do you mean right after the file header? My understanding is that at

Hi folks, I recently started getting errors when I fetch from the github monorepo ( https://github.com/llvm-project/llvm-project-20170507). They look like this: $ git fetch error: cannot lock ref 'refs/tags/release_600': there is a non-empty directory '.git/refs/tags/release_600' blocking reference 'refs/tags/release_600' >From github.com:llvm-project/llvm-project-20170507 ! [new tag] re...

The monorepo prototype at https://github.com/llvm-project/llvm-project-20170507 is currently 9 hours behind. I forget who’s responsible for the script(s) updating the monorepo(s), and it would be great if we can inform them of the state of the monorepo. Cheers -- Dean

...n undefined, rather than zero, value. I can work around my ignorance in performDAGCombine but would prefer to add to the existing pattern matching. Thanks, Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170507/1fcc13ea/attachment.html>

...on top of > D40179 to emulate what happens with a monorepo after my proposal lands). > > Steps I took (starting with > https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo > ): > > === > % git clone https://github.com/llvm-project/llvm-project-20170507/ > llvm-project > % cd llvm-project > % cp llvm/.arcconfig . > % mkdir -p .git/info > % echo .arcconfig >> .git/info/exclude > # Manually apply D40179 into the clang-tools-extra directory > % arc export --revision D40179 --git | patch -d clang-tools-extra -p1 > patchin...

On Sun, May 7, 2017 at 12:07 AM, NAKAMURA Takumi via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I have done just now. 5 repos added including debuginfo-tests. > ATM, it includes 17 repos total. > > - Created the new repo; https://github.com/llvm- > project/llvm-project-20170507.git > Branches will come later. > - The previous repository has a merge commit that includes new repo. It > will stick to r302363. > Can you update http://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo with new instructions for how to get a monorepo that...

...orepo after my proposal lands). >>> >>> Steps I took (starting with >>> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo >>> ): >>> >>> === >>> % git clone https://github.com/llvm-project/llvm-project-20170507/ >>> llvm-project >>> % cd llvm-project >>> % cp llvm/.arcconfig . >>> % mkdir -p .git/info >>> % echo .arcconfig >> .git/info/exclude >>> # Manually apply D40179 into the clang-tools-extra directory >>> % arc export --revision D4...

...out on top of D40179 > to emulate what happens with a monorepo after my proposal lands). > > Steps I took (starting with https://llvm.org/docs/Get > tingStarted.html#for-developers-to-work-with-a-git-monorepo): > > === > % git clone https://github.com/llvm-project/llvm-project-20170507/ > llvm-project > % cd llvm-project > % cp llvm/.arcconfig . > % mkdir -p .git/info > % echo .arcconfig >> .git/info/exclude > # Manually apply D40179 into the clang-tools-extra directory > % arc export --revision D40179 --git | patch -d clang-tools-extra -p1 > patchin...

I am planing to add projects into https://github.com/llvm-project/llvm-project in near future, possibly this week. Before doing that, I would like to ask users of it. 1st option is my preference in each paragraph. Let me know if you have other suggestions. * What is added? I will add; libunwind, llgo, openmp and parallel-libs. May I also add debuginfo-tests? * Will inactive projects be

I've noticed that there are no tags in any of the Git mirrors [1], [2] or [3]. Would it be possible to add the tags? [1] https://git.llvm.org/git/llvm.git [2] https://github.com/llvm-mirror/llvm [3] https://github.com/llvm-project/llvm-project-20170507 -- /Jacob Carlborg

...orepo after my proposal lands). >>> >>> Steps I took (starting with >>> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo >>> ): >>> >>> === >>> % git clone https://github.com/llvm-project/llvm-project-20170507/ >>> llvm-project >>> % cd llvm-project >>> % cp llvm/.arcconfig . >>> % mkdir -p .git/info >>> % echo .arcconfig >> .git/info/exclude >>> # Manually apply D40179 into the clang-tools-extra directory >>> % arc export --revision D4...

...official docs suggest the following tree. http://llvm.org/docs/GettingStarted.html#git-mirror llvm (llvm repo) -> tools -> clang (clang repo) -> lld (lld repo) etc. However various llvm-project repos, suggest a different layout: https://github.com/llvm-project/llvm-project-20170507 https://github.com/chapuni/llvm-project-submodule Also, the official SVN hints at a similar layout (although not strictly the same): http://llvm.org/svn/llvm-project/ llvm-project -> llvm (llvm repo) -> clang (clang repo) -> lld (lld repo) etc. It seems like the CMake files support...

On Sat, Jun 24, 2017 at 9:57 AM Chandler Carruth <chandlerc at gmail.com> wrote: > But now git-svn will be unable to rebuild revisions without switching URL > and breaking git hashes. Have folks tried this? What commands should > git-svn and hit mirror users use to update? > It's possible I'm off base here, but a couple of things: a) This shouldn't be a problem if

Possibly unrelated but since someone asked, I wonder why we don’t have monorepo for releases? For example a .tar.s containing all LLVM6.0 components placed at correct location Zhang > 在 2018年8月30日，18:16，Dean Michael Berris via llvm-dev <llvm-dev at lists.llvm.org> 写道： > > Thanks! >> On Thu, Aug 30, 2018 at 7:31 PM NAKAMURA Takumi <geek4civic at gmail.com> wrote:

...David > On 7 May 2017, at 08:07, NAKAMURA Takumi via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I have done just now. 5 repos added including debuginfo-tests. > ATM, it includes 17 repos total. > > - Created the new repo; https://github.com/llvm-project/llvm-project-20170507.git > Branches will come later. > - The previous repository has a merge commit that includes new repo. It will stick to r302363. > - Submodule repo has been pushed with -f. > > Rebasing to new branch(es) will take a few minutes. Please be patient. > > Thanks, Takumi > &...