`obc` and `obi`: add a switch to force all methods to be `native`

`obc` and `obi`: add a switch to force all methods to be `native`

[objeck]

Is this for source and libraries? I feel libraries need their existing flags (i.e. native) for consistent performance.

[objeck]

I will look into this for the next release. This is more of a runtime vs. compiler issue. The compiler may link libraries that use the native keyword. If so, the JIT compiler must be disabled within the VM. I am also concerned with overall performance.

I will look into this for the next release. This is more of a runtime vs. compiler issue. The compiler may link libraries that use the native keyword. If so, the JIT compiler must be disabled within the VM. I am also concerned with overall performance.

Don't think too much. It's source-level and only affects the source files being compiled. There is nothing to do with the runtime. When I proposed this, I didn't think you would think that far. My opinion is that everything should be JIT-ed. The keyword native sounds redundant to me. I am afraid to tell this straight to you. I only want my usage of Objeck to be easier, but I don't want to clash with you, so I made this suggestion.

[objeck]

No impact on the source programmer's source code. The idea is to empower the programmer to let them decide to want they want JIT compiled in their code. On the otherhand, JIT compiling everything is efficient.

No impact on the source programmer's source code. The idea is to empower the programmer to let them decide to want they want JIT compiled in their code. On the otherhand, JIT compiling everything is efficient.

I don't get this idea. We disagreed with each other again. Btw, this suggestion is about a compiler switch, not about forcing JIT by default with no options to customize. It's just a shortcut to make the programmer's life easier so he doesn't have to write native everywhere. His ability to customize everything is not affected, just don't use the compiler switch.

[objeck]

So, the programmer should not use the native keyword. What am I missing? Are you asking for a compiler switch to override the programmer's use of the keyword native? This is not about disagreement, as I am trying to understand your request.

So, the programmer should not use the native keyword. What am I missing? Are you asking for a compiler switch to disable the programmer's use of the keyword native?

Regardless of the source code use native or not, a compiler switch will force native so everything be JIT-ed (this issue, #387). My main usage for this is that I don't have to write native everywhere. Issue #388 is the reverse of this, as it will force everything to be not JIT-ed.

[objeck]

Thanks, I will look into it. However, performance may suffer. Not all code needs to be JIT compiled. The compiler optimizes all code, rather JIT compiler or not. At runtime, the JIT compiler flag is honored.

Do you have metrics, programs, or data that you can share for testing?

Thanks, I will look into it. However, performance may suffer. Not all code needs to be JIT compiled. The compiler optimizes all code, rather JIT compiler or not. At runtime, the JIT compiler flag is honored.

Now it's me who struggles to understand what you are talking about. OK. I don't expect it to be that complicated. I'm not a professional programmer, and I tend to think the simple way. Java and C# offer no such control. I think they let the VM decide whether to JIT or not. Everything is fine. Why is it too complicated with Objeck?

[objeck]

JIT comping all methods/functions has a runtime hit which is not justified in most cases. It is justified if the methods/functions are computationally intensive and are called multiple times within the code.

Simple calls like getters/setters are optimized to avoid function/method calls, and more aggressive inlining is done after that.

Please send me a code sample so that I can test and benchmark your request. Implementing your request is easy, but I worry about side effects.

Refer: https://en.wikipedia.org/wiki/Just-in-time_compilation

Please close this issue and remove it from the roadmap. I don't need this feature anymore. Thank you.

[objeck]

Okay, thank you for the feedback.

For reference, this is the optimization pipeline.

Optimizations in list order:

1. Jump optimizations
2. Constant folding
3. Getter/Setting inlining
4. Dead store removal
5. Constant propagation
6. Method inlining
7. Strength reduction
8. Instruction optimization

Additionally, at runtime, bytecode may be translated to machine code at the programmer's request.

Additionally, at runtime, bytecode may be translated to machine code at the programmer's request.

Isn't this AOT?

[objeck]

Additionally, at runtime, bytecode may be translated to machine code at the programmer's request.

Isn't this AOT?

No, that is compiling bytecode into machine code before runtime vs. at runtime.