Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-09-27T12:54:21+00:00 2019-09-27T12:54:21+00:00 Guillaume Chatelet gchatelet@google.com 2019-09-27T12:54:21+00:00 urn:sha1:18f805a7ea5f369ef523821693f1176b40bcfc7e llvm-svn: 373081 2019-09-12T15:20:36+00:00 Guillaume Chatelet gchatelet@google.com 2019-09-12T15:20:36+00:00 urn:sha1:af11cc7eb5da320066d88a8f6d015e6296f0da25 Summary: This is patch is part of a series to introduce an Alignment type. See this thread for context: http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html See this patch for the introduction of the type: https://reviews.llvm.org/D64790 Reviewers: courbet, JDevlieghere, alexshap, rupprecht, jhenderson Subscribers: sdardis, nemanjai, hiraditya, kbarton, jakehehrlich, jrtc27, MaskRay, atanasyan, jsji, seiya, cfe-commits, llvm-commits Tags: #clang, #llvm Differential Revision: https://reviews.llvm.org/D67499 llvm-svn: 371742 2019-07-23T14:44:21+00:00 Owen Reynolds gbreynoo@gmail.com 2019-07-23T14:44:21+00:00 urn:sha1:24f3e102a678e2d102ac5660371fba1c2cfccd25 llvm-ar outputs a strange error message when handling archives with members larger than 4GB due to not checking file size when passing the value as an unsigned 32 bit integer. This overflow issue caused malformed archives to be created.: https://bugs.llvm.org/show_bug.cgi?id=38058 This change allows for members above 4GB and will error in a case that is over the formats size limit, a 10 digit decimal integer. Differential Revision: https://reviews.llvm.org/D65093 llvm-svn: 366813 2019-07-10T00:34:13+00:00 Reid Kleckner rnk@google.com 2019-07-10T00:34:13+00:00 urn:sha1:cc418a3af45adbe740f868a31bde6155083f0b9d Summary: On Windows, Posix integer file descriptors are a compatibility layer over native file handles provided by the C runtime. There is a hard limit on the maximum number of file descriptors that a process can open, and the limit is 8192. LLD typically doesn't run into this limit because it opens input files, maps them into memory, and then immediately closes the file descriptor. This prevents it from running out of FDs. For various reasons, I'd like to open handles to every input file and keep them open during linking. That requires migrating MemoryBuffer over to taking open native file handles instead of integer FDs. Reviewers: aganea, Bigcheese Reviewed By: aganea Subscribers: smeenai, silvas, mehdi_amini, hiraditya, steven_wu, dexonsmith, dang, llvm-commits, zturner Tags: #llvm Differential Revision: https://reviews.llvm.org/D63453 llvm-svn: 365588 2019-06-04T10:13:03+00:00 Owen Reynolds gbreynoo@gmail.com 2019-06-04T10:13:03+00:00 urn:sha1:5d5078e341f593944d9badd53e374e6b319282da Includes a fix for an introduced build failure due to a post c++11 use of std::mismatch. This fixes some thin archive relative path issues, paths are shortened where possible and paths are output correctly when using the display table command. Differential Revision: https://reviews.llvm.org/D59491 llvm-svn: 362484 2019-06-03T16:21:37+00:00 Dmitri Gribenko gribozavr@gmail.com 2019-06-03T16:21:37+00:00 urn:sha1:857de979a7e43f26973351931b93a3879a09ec5a This reverts commit r362407. It broke compilation of llvm/lib/Object/ArchiveWriter.cpp: error: type 'llvm::sys::path::const_iterator' does not provide a call operator llvm-svn: 362413 2019-06-03T15:26:07+00:00 Owen Reynolds gbreynoo@gmail.com 2019-06-03T15:26:07+00:00 urn:sha1:fade9cbed76343c1e63657c4d425d3c47b0d73bf This fixes some thin archive relative path issues, paths are shortened where possible and paths are output correctly when using the display table command. Differential Revision: https://reviews.llvm.org/D59491 llvm-svn: 362407 2019-05-10T09:59:04+00:00 Fangrui Song maskray@google.com 2019-05-10T09:59:04+00:00 urn:sha1:e357ca82311ff40a0be1a80c8513f37aff93a0a2 llvm-svn: 360414 2019-02-19T18:14:44+00:00 Jordan Rupprecht rupprecht@google.com 2019-02-19T18:14:44+00:00 urn:sha1:d138b1266a6a8852641d7dd505900c938ee04c1f Summary: As suggested in rL353995 Reviewers: compnerd Reviewed By: compnerd Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D58298 llvm-svn: 354364 2019-02-13T23:39:41+00:00 Jordan Rupprecht rupprecht@google.com 2019-02-13T23:39:41+00:00 urn:sha1:451c2ef199e9c5163007ac32e2d426fbfb37e664 Summary: When adding one thin archive to another, we currently chop off the relative path to the flattened members. For instance, when adding `foo/child.a` (which contains `x.txt`) to `parent.a`, when flattening it we should add it as `foo/x.txt` (which exists) instead of `x.txt` (which does not exist). As a note, this also undoes the `IsNew` parameter of handling relative paths in r288280. The unit test there still passes. This was reported as part of testing the kernel build with llvm-ar: https://patchwork.kernel.org/patch/10767545/ (see the second point). Reviewers: mstorsjo, pcc, ruiu, davide, david2050, inglorion Reviewed By: ruiu Subscribers: void, jdoerfert, tpimh, mgorny, hans, nickdesaulniers, hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D57842 llvm-svn: 353995