en Copyright 2015 Java http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/llvm/test/CodeGen/Hexagon/vararg_double_onstack.ll#2208c97c1bec2512d4e47b6223db6d95a7037956 [Hexagon,test] Change llc -march= to -mtriple=Similar to 806761a7629df268c8aed49657aeccffa6bca449-mtriple= specifies the full target triple while -march= merely sets thearchitecture part of the default target triple, leaving a target triple whichmay not make sense.Therefore, -march= is error-prone and not recommended for tests without a targettriple. The issue has been benign as we recognize $unknown-apple-darwin as ELF insteadof rejecting it outrightly. List of files: /llvm-project/llvm/test/CodeGen/Hexagon/vararg_double_onstack.ll Sun, 15 Dec 2024 18:20:22 +0000 Fangrui Song <i@maskray.me> http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/llvm/test/CodeGen/Hexagon/vararg_double_onstack.ll#a96f691985c8546e826012fdc3481c88f034a194 [Hexagon] Convert some tests to opaque pointers (NFC) List of files: /llvm-project/llvm/test/CodeGen/Hexagon/vararg_double_onstack.ll Mon, 19 Dec 2022 11:52:45 +0000 Nikita Popov <npopov@redhat.com> http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/llvm/test/CodeGen/Hexagon/vararg_double_onstack.ll#06c192d454767376771e8fed4ddcf8a461723e32 OpaquePtr: Bulk update tests to use typed byvalUpgrade of the IR text tests should be the only thing blocking makingtyped byval mandatory. Partially done through regex and partiallymanual. List of files: /llvm-project/llvm/test/CodeGen/Hexagon/vararg_double_onstack.ll Fri, 20 Nov 2020 15:52:27 +0000 Matt Arsenault <Matthew.Arsenault@amd.com> http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/llvm/test/CodeGen/Hexagon/vararg_double_onstack.ll#7fee4fed4c75c13d0cec7ff3a043e0313a3abc55 Add support for Linux/Musl ABIDifferential revision: https://reviews.llvm.org/D72701The patch adds a new option ABI for Hexagon. It primary deals withthe way variable arguments are passed and is use in the Hexagon Linux Muslenvironment.If a callee function has a variable argument list, it must perform thefollowing operations to set up its function prologue: 1. Determine the number of registers which could have been used for passing unnamed arguments. This can be calculated by counting the number of registers used for passing named arguments. For example, if the callee function is as follows: int foo(int a, ...){ ... } ... then register R0 is used to access the argument ' a '. The registers available for passing unnamed arguments are R1, R2, R3, R4, and R5. 2. Determine the number and size of the named arguments on the stack. 3. If the callee has named arguments on the stack, it should copy all of these arguments to a location below the current position on the stack, and the difference should be the size of the register-saved area plus padding (if any is necessary). The register-saved area constitutes all the registers that could have been used to pass unnamed arguments. If the number of registers forming the register-saved area is odd, it requires 4 bytes of padding; if the number is even, no padding is required. This is done to ensure an 8-byte alignment on the stack. For example, if the callee is as follows: int foo(int a, ...){ ... } ... then the named arguments should be copied to the following location: current_position - 5 (for R1-R5) * 4 (bytes) - 4 (bytes of padding) If the callee is as follows: int foo(int a, int b, ...){ ... } ... then the named arguments should be copied to the following location: current_position - 4 (for R2-R5) * 4 (bytes) - 0 (bytes of padding) 4. After any named arguments have been copied, copy all the registers that could have been used to pass unnamed arguments on the stack. If the number of registers is odd, leave 4 bytes of padding and then start copying them on the stack; if the number is even, no padding is required. This constitutes the register-saved area. If padding is required, ensure that the start location of padding is 8-byte aligned. If no padding is required, ensure that the start location of the on-stack copy of the first register which might have a variable argument is 8-byte aligned. 5. Decrement the stack pointer by the size of register saved area plus the padding. For example, if the callee is as follows: int foo(int a, ...){ ... } ; ... then the decrement value should be the following: 5 (for R1-R5) * 4 (bytes) + 4 (bytes of padding) = 24 bytes The decrement should be performed before the allocframe instruction. Increment the stack-pointer back by the same amount before returning from the function. List of files: /llvm-project/llvm/test/CodeGen/Hexagon/vararg_double_onstack.ll Fri, 27 Dec 2019 19:03:01 +0000 Sid Manning <sidneym@quicinc.com>