similar to: apt.llvm.org has the wrong binaries/headers for llvm-toolchain-xenial-7

It appears that there was an out-of-band patch from Samuel Thibault: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/blob/7/debian/patches/D54378-hurd-triple.diff Although the patch was approved here https://reviews.llvm.org/D54378 Is this patch going to land in 7.0.1 or 8? kristopher > Here's further proof: > > wget >

Hi, The 7.0.1-rc2 release has been tagged and is ready for testing. I forgot to bump the version number to 7.0.1 before I tagged -rc1, which is why we are now on -rc2. Remember, you can continue to submit merge requests up until Nov, 21, so keep testing and submitting fixes. Thanks, Tom

On 11/28/18 8:46 PM, Friedman, Eli via llvm-dev wrote: > On 11/28/2018 5:28 PM, Kristopher Tate via llvm-dev wrote: >> Although the patch was approved here https://reviews.llvm.org/D54378 >> >> Is this patch going to land in 7.0.1 or 8? > > For trunk (and therefore 8), looks like it was approved, and it's just > waiting for someone with commit rights to merge it.

Hello, I’m working on porting llvm to build for 65816, and I wanted to use a value of e_machine for this. I was wondering if there is a process for getting a value reserved. I’ve seen some information but its from many years ago, and seems to be well out of date? Just wanted to ask people who would likely know. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Op 25-11-2024 om 17:06 schreef Hoefle, Marco (Avnet Silica): > >>Op 25-11-2024 om 11:57 schreef Rowland Penny via samba: > >>> On Mon, 25 Nov 2024 11:44:28 +0100 > >>> Kees van Vloten via samba <samba at lists.samba.org> wrote: > >>> > >>>> Op 25-11-2024 om 11:35 schreef Rowland Penny via samba: > >>>>> On Mon, 25

Hello, Recently Jonathan Blow posted a short screencast discussing build time of his compiler with when no optimizations are run on the user's code. Part 1: https://www.youtube.com/watch?v=HLk4eiGUic8 Part 2: https://www.youtube.com/watch?v=mIjGYbol0O4 He discusses what parts are taking the longest to compile, and the ultimately shows this: http://i.imgur.com/BkbKcJK.png ...which shows that

>>>>> On Mon, 25 Nov 2024 11:44:28 +0100 >>>>> Kees van Vloten via samba <samba at lists.samba.org>?wrote: >>>>> >>>>>> Op 25-11-2024 om 11:35 schreef Rowland Penny via samba: >>>>>>> On Mon, 25 Nov 2024 09:48:19 +0000 >>>>>>> "Hoefle, Marco \(Avnet Silica\) via samba" <samba

I've got a patched LLD 5.0.0 like this: diff --git a/deps/lld/COFF/Driver.cpp b/deps/lld/COFF/Driver.cpp index 854c3e69..8bab1c11 100644 --- a/deps/lld/COFF/Driver.cpp +++ b/deps/lld/COFF/Driver.cpp @@ -1030,7 +1030,7 @@ void LinkerDriver::link(ArrayRef<const char *> ArgsArr) { if (!Args.hasArgNoClaim(OPT_INPUT)) { fixupExports(); createImportLibrary(/*AsLib=*/true); -

On Sun, Mar 22, 2020 at 9:05 PM Andrew Kelley <andrew at ziglang.org> wrote: > > On 3/19/20 9:51 AM, Hans Wennborg via llvm-dev wrote: > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > > release branch at 35627038123. > > > > Source code and docs are available at > > https://prereleases.llvm.org/10.0.0/#rc5 and > >

On 2018-09-20 10:01, Hans Wennborg via llvm-dev wrote: > Yes, it's a manual process. The binaries are build and tested by > volunteers, and the set of folks who volunteers differs a little > between releases. I would assume LLVM has some kind of CI infrastructure. That should be able to build the release binaries. > The pre-built binaries are really mostly for users who want to

I think you want to call freeArena() before returning from lld::coff::link. On Sun, Oct 15, 2017 at 6:57 PM, Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I believe this line is the culprit: > > COFF/Driver.cpp:102: > make<std::unique_ptr<MemoryBuffer>>(std::move(MB)); // take ownership > > Patch forthcoming. > > > On Sun, Oct

I'd be interested in the existence of a high-quality, open-source, portable linker for apple platforms, but not enough to help make that happen. If I _was_ gonna work on something related to that, I'd probably be inclined to instead add any required features to allow an ELF linker to target a notional darwin-elf target, and to have clang emit darwin-elf object files, and then write a

On Mon, Jun 3, 2019 at 8:04 PM Duncan Murdoch wrote: > I don't recall anyone asking for the zip in the 17 years after that > change, until now (though I haven't been paying attention lately, since > I retired from building the binaries a couple of years ago). > > If you think it's worthwhile to do it, then I don't think anyone would > object if you went ahead and

If you call lld::coff::link twice, the second time gives this backtrace: msvcp140d.dll!00007ffc35830806() Unknown > zig.exe!std::_Debug_pointer<lld::coff::Chunk * __ptr64 const>(lld::coff::Chunk * const * _Ptr, const wchar_t * _File, unsigned int _Line) Line 926 C++ zig.exe!std::_Debug_range2<lld::coff::Chunk * __ptr64 const * __ptr64>(lld::coff::Chunk * const *

+Rui and Peter On Wed, Jul 25, 2018 at 8:34 AM, Andrew Kelley via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Here's a fix: > > --- a/lld/COFF/Driver.cpp > +++ b/lld/COFF/Driver.cpp > @@ -72,6 +72,9 @@ bool link(ArrayRef<const char *> Args, bool CanExitEarly, > raw_ostream &Diag) { > exitLld(errorCount() ? 1 : 0); > > freeArena(); > +

Thank you for this exciting update about LLD. I will start experimenting with using liblld in Zig (http://ziglang.org/) instead of starting a child process to invoke the system linker. Once liblld makes it into the various package managers out there, this will be a big step toward painless cross-platform compilation. It should also reduce one of the compilation speed bottlenecks, since I could

Hello llvm-dev! We are currently building a tool using LLVM which statically computes the worst-case stack depth for programs whose call-graphs are statically constrained. While this task is undecidable for general programs, we specifically plan to use it to analyze all entry points into Zircon’s kernel and the vDSO. Currently, without such a tool, the best option for allocating kernel memory in

I'm copying some LLD code into my codebase like this: // workaround for LLD not exposing ability to convert .def to .lib #include <set> namespace lld { namespace coff { class SymbolBody; class StringChunk; struct Symbol; struct Export { StringRef Name; // N in /export:N or /export:E=N StringRef ExtName; // E in /export:E=N SymbolBody *Sym = nullptr; uint16_t Ordinal

Zig Programming Language Zig <http://ziglang.org/> is a system programming language which prioritizes optimality, safety, and readability. It integrates closely with C and is intended to eventually take the place of C. It uses LLVM to produce highly optimized native code and to cross-compile for any target out of the box. Zig is in alpha; progress toward a beta release is underway.

On 03/06/2019 9:16 p.m., Steven Penny wrote: > On Mon, Jun 3, 2019 at 8:04 PM Duncan Murdoch wrote: >> I don't recall anyone asking for the zip in the 17 years after that >> change, until now (though I haven't been paying attention lately, since >> I retired from building the binaries a couple of years ago). >> >> If you think it's worthwhile to do it,