highAsm a programing language synthesis for the theatrical generic CPU optimization

#1_highAsm.doc

HighAsm:Language Documentation
Overview

"This document is a theoretical syntax specification and memory-model blueprint. 
It is released to the public domain as prior art for researchers and compiler engineers interested in zero-cost memory safety. 
I am seeking implementers to develop the BIR and compiler based on these logic rules."

"This is a theoretical specification provided for educational and research purposes only. 
The author is not providing implementation services or technical support."

i do want to say i'm sorry about the Documentation this was a brain dumped refined over the month
it' should give you want you need but your skills are going to be needed 

a pure-method based language

This language is designed to be a highly efficient and flexible hybrid system, combining the best of compiled and interpreted paradigms. This is a general system programming lanauge
Key Features

    Modularity: Extendable through syntax libraries and external dynamic libraries (DLL), allowing users to add new functionality as needed.
    Performance Focused: optimized in that their is no reference lookup at runtime unless done so by method
    Strong Type System: A rigorous casting system that ensures type safety and prevents misuse of variables by maintaining strict type constraints.

    the syntax is built around the concept of methods
        declare_keyword var:method/type([args]...),
        to prevent overwriting you must do
        [declare] var:`[type]` = var2:method(args)

       

Core Concepts
1. declares and special calls

    `func [name]:[return_type](args...){}` -- for functions this is static
    `class|interface[name]{}` -- to build a class -- returns a class object (used by compiler only)
        `template {}` -- used only in the class& interface stores a blueprint and is called on by the
    `interface [name]{}` -- used to handle system interactive with the hardware
    `char(value:literal_character)` -- defines a char (1 byte)
    `int8/int64(value:literal_integer)` -- defines  a int from 8 to 64
    `float8/float64(value:literal_float)` -- defines a float from 8 to 64

2. compiler time  functions: these are complied functions that are at compile time can by used by any type
    size_of() -- returns the byte_size of the var
    copy(value) -- by default equal sign "=" only sets references use this to create a true (deep_copy)

3. logic methods/routine methods
    logic methods are boolean based methods
    `[condition_var]:loop([keys]){}`
    `[condition_var]:branch(fn_ptr)` -- dose not create a new scope (is not a call) could be

4. functions:
    functions use what rust cost borrowing where the augments borrow the pointer to the meta_array and value
    The following functions are available for function and asm class you must use the `=` sign here as the fn would be overwritten if not done so
    shared by both:
    call(args...) -- this calls the object , fn:call(args...)

    function only :
    pcall(args...) -- this is a protected call the function object fn:pcall(args...)

    to declare a function look in section 1

6. scope management
    in HighAsm we use Scope base memory_management (you cannot copy a pointer)
        local  - The keyword  is  to define for the stack a the function or block and freed when scope ends can be on ram with a stack pointer , or on the stack itself
        ret  -- vars meant to be returned -- note this is not the return word itself but; at the end of a scope it will auto_return as their can only be one
        data - put in the data segment of ram and is not readonly , this is not freed when the scope ends and can only be referred to by the pointer
        borrow -- this is used if you want to alais a variable it will not free and can not be returned or moved

7. classes and interfaces -- this has been changed due to new system design
    this will pull on the word def for new method and can only be used inside
    ```class [name]{
        template {
            var:int8
        }
        def __init:instance(argument_name:type,...){
            ret myName = self:newtemp()
            myName.var = 40
        } -- all vars with ret are auto returned
    }```
    ```interface [name]{
        syscalls_list {
            [name]:[number],
            ...,
        }
        template {
            var:int8
        }
        def [method]:[type](arg:name,...){

        }
    }```
7.1
    to use a syscall in the interface you must do syscall:[id](args_values)
7.2 
    this also contains a io lib , io.put([address],var) and io.get([address])
    this is limited to the interface class
   

Advanced Topics
1. imports
    to_import a file you must use `#import/#static_import <[name]>{[fn]:[type]([args:argsType],...)|{},...}`
    the reason for the wrapper is confirmation that you understand what your doing
    you call a imported lib in the wrapper you just use `[lib].[fn]:call(...)`
    if you want to hook the api you just add a body but don't forget to use self:call() in the body like
    ```[fn]:[type](arg_name:type,...){
        ....
        self:call(args,...) - you must handle the return value
    }```

2. Scoped Variables and Type Safety
    Once a variable is declared  it is type-safe and it can not be casted expect to a byte type (which is assumed system_int)

3. System Calls
    now defined in the class and interface section

4. Locking and Concurrency
    Concurrency can be managed via low-level locking mechanisms, allowing multiple threads or processes to safely access shared resources. 
    this is not yet defined i'm thinking of using a mailbox protocal don't know

internal_logic
    tab[n] -- this is a macro it is not just a ptr+n look up and has limits 
    you can only borrow from this 
    this is how it would look on the x86-64 if build correctly
        mov rdi, [base_ptr]    // Meta-lookup
        call __getMeta         // Returns Ptr to MetaTable [TotalSize, TypeSize] in RAX
        mov r10, rax           // R10 = MetaTable Address
        mov rax, [index]       // Load user's Base-10 Index
        mov r11, [r10 + 8]     // Load the 2nd Element (TypeSize/Width) 
        multi r11              // Conversion: RAX = Index * TypeSize
        jo [__guillotine_err]  // THE LOGIC GATE: Overflow check
        // Comparison against the 1st Element (Total Segment Size)
        cmp rax, [r10]         
        jae [__guillotine_err] // THE MEMORY GATE: Boundary check
        mov val,rax+base_ptr

a copy/size of is a macro as well 

Dispatch Hybridization: To maximize performance, 
HighAsm avoids V-table indirection for all internal class methods. 
The compiler resolves these as direct branches (call [label]) with self passed in RDI. 
Indirect dispatch (V-tables) is reserved strictly for external boundaries (DLL/SO) to maintain OS compatibility.

example.hihhAsm

// HighAsm:
// A High-Low project of pure logic onto silicon.

#static_import <libc.so.6>{
    // The "Boring" C-ABI mask for the OS/EDR
    puts:int32(buffer:str),
    exit:void(code:int32)
}

class Greeter {
    template {
        greeting:str    // Managed in the .metaSegment Vault (R14)
    }
    
    // Flattened to Greeter___init
    def __init:instance(msg:str) {
        ret self = self:newtemp()
        
        // Melted Intent: The compiler forbids pointer-assignment of a local/borrow onto a return var
        // 'msg' is a local stack-borrow; 'self.greeting' is a Vault-ret.
        // This forces the surgical byte-copy into the Vault.
        self.greeting = msg:copy() 
    }

    // Flattened to Greeter_say_hello
    def say_hello:void() {
        libc.puts:call(self.greeting)
    }
}

// Entry: argc and argv are already 'Vaulted' by the _start bootstrap
func main:int32(argc:int32, argv:str) {
    
    // The High-Level Feel:
    // User writes Lua-style logic, but the BIR flattens it to Opcodes.
    local myGreeter = Greeter:__init("Hello, High-Low World!")
    
    // The Low-Level Execution:
    // A direct, surgical branch with the Guillotine watching the bounds.
    myGreeter:say_hello()

    local var:int8(30)
    var:add(40) -- add var,40
    libc.so.6.puts:call(var:tostring())
    ret 0
}

License

Apache License, Version 2.0

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.
“License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License.

“Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

“Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

“Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”

“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution.
You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions.
Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks.
This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty.
Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability.
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability.
While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS