[llvm-dev] Need help with code generation
Rui Ueyama via llvm-dev
llvm-dev at lists.llvm.org
Mon Mar 21 17:36:10 PDT 2016
On Tue, Mar 22, 2016 at 1:22 AM, Lang Hames via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi Rui,
>
> In such a hostile environment, do you really run any linker in an
>> unprotected environment?
>
>
> Not that I know of, but it's not an unreasonable thing to want to do: Run
> a linker on 3rd party input and have it link (or error out), not execute
> arbitrary code.
>
> Before it comes up yet again - I'm know that it is practically impossible
> to be fully bug-free, but that goes for any software project, and other
> software projects don't use it as an excuse not to try at all. LLVM's
> policy should be to try to detect errors in user input and exit cleanly.
> Exactly how we prioritize work on that is a challenge, but again - it's a
> challenge on any project.
>
If you are arguing that it is a universal policy among all programs that it
should never crash for any input and we are making excuse, I can't agree.
If you are arguing that any LLVM subproject should have a policy of
no-crash-for-any-input, I'd argue that that is sometimes not directly
applicable because every subproject vary. Our goal as a whole is, as I
believe, to provide value to users, and LLD development speed is
accelerating and it is about to be providing real (and possibly large)
values to users. By thinking of that, it seems that the stance that any
LLVM subproject should never crash for any reason whatever the type of
subproject is is probably a bit dogmatic.
> Cheers,
> Lang.
>
> On Mon, Mar 21, 2016 at 5:17 PM, Rafael Espíndola <
> rafael.espindola at gmail.com> wrote:
>
>> :
>> >>
>> >
>> > Great example!
>> > I believe users generating this kind of IR would prefer an error on why
>> the code is invalid to realize what they missed in their “frontend”.
>> >
>> > Could you file a PR?
>>
>> The example is already from another thread. The point is that it is an
>> example. Look at most variable length allocations in llvm and you should be
>> able to write another crasher.
>>
>> Cheers,
>> Rafael
>>
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160322/e37599d4/attachment.html>
More information about the llvm-dev
mailing list