On Tue, Aug 30, 2022 at 3:37 PM Terrence Lim <heuichan....@gmail.com> wrote:
> Hi Jakob,
>
> I came across a follow-up question regarding the optimization phases.
> What would happen (assume that we can) if we forcefully disable the
> mandatory phases, e.g., SimplifiedLowering?
> Will the JIT compiler fail (crash) during the compilation?
>
Yes.
Think of the different IR levels as different languages. They need to be
translated ("lowered") into each other, and that chain must be complete.
The translation steps in the middle are just as essential as translating
from the input format to a high-level IR graph at the beginning, and
translating from a low-level IR graph to machine code at the very end.
>
> Thanks! Regards
>
> On Fri, Aug 26, 2022 at 1:58 AM Jakob Kummerow <jkumme...@chromium.org>
> wrote:
>
>> No, some Turbofan passes cannot be disabled, because they are required.
>> SimplifiedLowering is a great example -- it changes ("lowers") the graph to
>> the format that subsequent passes require.
>>
>>
>> On Fri, Aug 26, 2022 at 4:18 AM TL <heuichan....@gmail.com> wrote:
>>
>>> I am curious whether there are any options for the 'd8' to disable
>>> specific TurboFan
>>> optimizations, e.g., simplified-lowering, type-lowering, etc, for *all* the
>>> optimization
>>> options or not. I know there are options for some optimizations, such as
>>> escape-analysis, loop-peeling, etc. But, can we have control of "all"
>>> the optimizations
>>> without actually modifying the v8 source code?
>>>
>>> --
>>> --
>>
>>
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/v8-users/CAKSzg3Td_OGV9gdJS%3DFsFSueko%2BEhQtygiYiVrOvw4UtVWJsjg%40mail.gmail.com.
