Whar's the different between non-aarch label and with aarch label?

[wnffldktm]

Hi, I just started to checking this repositories (?) of Zen Browser.

I notice that both release and twilight build has non-aarch label and aarch label.
What's the different between the two?
If by any chance we install the release one in non-aarch label, then repatch it with the twilight in aarch label, is it alright?
I mean, it's like four option, no?
And I believe that's it has it's after-effect.
Will the newest one that I patched on, without uninstalling previous, it will replacing all of the file inside our device?
And then.. nah nah, that's all for now that I wanted to know hehe.

Thank you 🙏🏼

[dosubot[bot]]

Hey @ROUwnffldktm! I'm here to help you with any issues or questions you have about the Zen Browser repositories. I can provide assistance with bug fixes, answer any questions you may have, and guide you on becoming a contributor. Let me know how I can assist you today! 🤖

The difference between 'aarch' and 'non-aarch' labels in the Zen Browser releases primarily relates to the target architecture and optimization settings:

1. Target Architecture:

   • 'aarch' builds are for ARM architecture (aarch64).
   • 'non-aarch' builds are for x86_64 architecture.

2. Optimization and Compiler Flags:

   • 'aarch' builds use specific optimization flags for ARM architecture, such as -O2 -mtune=cortex-a55 -march=armv8.2-a+simd.
   • 'non-aarch' builds use different optimization flags suitable for x86_64, like -O3 -w -ftree-vectorize -mfpmath=sse.

3. Link Time Optimization (LTO) and Profile-Guided Optimization (PGO):

   • 'aarch' builds have specific LTO settings and generally do not use PGO unless specified.
   • 'non-aarch' builds enable PGO with specific configurations ^[1][2].

Regarding installing a release with a 'non-aarch' label and then patching it with a 'twilight' build with an 'aarch' label, there is no specific documentation in the repository about the consequences of mixing these builds. However, due to the differences in architecture and optimization settings, it is generally not advisable to mix them, as it could lead to compatibility issues or unexpected behavior.

As for whether the installation process replaces all files or only updates specific components, there is no specific information available in the repository about this process ^[3][4].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}