Displaying 6 results from an estimated 6 matches for "r259831".
Did you mean:
259831
2016 Dec 18
3
LLD status update and performance chart
...asn't been written because most
> object files we've seen so far seem to come from a small number of
> well-tested codepaths that always (as in the `assert` meaning of "always")
> create valid ELF files. In fact, we've added graceful recovery as
> appropriate (e.g. r259831), which is a step above error handling!
>
> Also, I'd like to point out that Clang, even when it does run the LLVM
> verifier (which is not the default except in development builds), runs it
> with fatal error handling. Is anybody aware of a program that uses LLVM as
> a library,...
2016 Dec 18
0
LLD status update and performance chart
...s for LLD; it just hasn't been written because most
object files we've seen so far seem to come from a small number of
well-tested codepaths that always (as in the `assert` meaning of "always")
create valid ELF files. In fact, we've added graceful recovery as
appropriate (e.g. r259831), which is a step above error handling!
Also, I'd like to point out that Clang, even when it does run the LLVM
verifier (which is not the default except in development builds), runs it
with fatal error handling. Is anybody aware of a program that uses LLVM as
a library, produces IR in memory,...
2016 Dec 18
2
LLD status update and performance chart
...s for LLD; it just hasn't been written because most object files we've seen so far seem to come from a small number of well-tested codepaths that always (as in the `assert` meaning of "always") create valid ELF files. In fact, we've added graceful recovery as appropriate (e.g. r259831), which is a step above error handling!
>
> Also, I'd like to point out that Clang, even when it does run the LLVM verifier (which is not the default except in development builds), runs it with fatal error handling. Is anybody aware of a program that uses LLVM as a library, produces IR i...
2016 Dec 18
0
LLD status update and performance chart
...ust hasn't been written because most object files we've seen so far
> seem to come from a small number of well-tested codepaths that always (as
> in the `assert` meaning of "always") create valid ELF files. In fact, we've
> added graceful recovery as appropriate (e.g. r259831), which is a step
> above error handling!
>
> Also, I'd like to point out that Clang, even when it does run the LLVM
> verifier (which is not the default except in development builds), runs it
> with fatal error handling. Is anybody aware of a program that uses LLVM as
> a lib...
2016 Dec 18
1
LLD status update and performance chart
...s for LLD; it just hasn't been written because most object files we've seen so far seem to come from a small number of well-tested codepaths that always (as in the `assert` meaning of "always") create valid ELF files. In fact, we've added graceful recovery as appropriate (e.g. r259831), which is a step above error handling!
>>
>> Also, I'd like to point out that Clang, even when it does run the LLVM verifier (which is not the default except in development builds), runs it with fatal error handling. Is anybody aware of a program that uses LLVM as a library, produ...
2016 Dec 16
4
LLD status update and performance chart
> On Dec 16, 2016, at 11:46 AM, Rui Ueyama <ruiu at google.com> wrote:
>
> On Fri, Dec 16, 2016 at 11:18 AM, Pete Cooper <peter_cooper at apple.com <mailto:peter_cooper at apple.com>> wrote:
> Hi Rui
>
> I agree separating the components out in to libraries only makes sense when there is a clear reason to do so. However, just this year there was a very