You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently we've noticed some naming inconsistency in the Chromium codebase that apparently can be traced to the earliest in-house LoongArch ports. For example this one: the name "loongarch64" / "LOONGARCH64" (!!!) is still being used despite the proper V8/GN name being "loong64", and new references are going to pop up.
It will be appreciated that someone steps up and fixes the problem upstream.
The text was updated successfully, but these errors were encountered:
Recently we've noticed some naming inconsistency in the Chromium codebase that apparently can be traced to the earliest in-house LoongArch ports. For example this one: the name "loongarch64" / "LOONGARCH64" (!!!) is still being used despite the proper V8/GN name being "loong64", and new references are going to pop up.
It will be appreciated that someone steps up and fixes the problem upstream.
The text was updated successfully, but these errors were encountered: