[AArch64] Storing a copy of all function arguments on the stack for debug/instrumentation?

To aid in debugging and instrumentation (we would like to look at a stopped program and unwind while recording all argument values), I would like to either store a copy of all register arguments on the caller's stack or record them in the callee's stack on function entry. Both options are straight

Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Aripl 07, 2022)

Please note that the Zc* extension family did not make it to ratification last year. To my knowledge, the specification contents are not frozen and still subject to change. Thanks, Philipp. On Wed, 6 Apr 2022 at 14:11, wrote: > Hi all, > > Here is the agenda for tomorrow's meeting. If you have

Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Jan 27, 2022)

Hi all, I won't be able to attend, as the IOMMU TG is convening in the same timeslot tomorrow. However, please be advised that (to my knowledge and after checking with Stephano) the Zcea is on-hold and not frozen. Thanks, Philipp. On Wed, 26 Jan 2022 at 14:05, wrote: > Hi all, > > There is an

Re: GCC optimizations with O3

ptomsich@android:~/riscv/gcc/gcc$ git grep OPT_LEVELS_3 common/common-target.h: OPT_LEVELS_3_PLUS, /* -O3 and above. */ common/common-target.h: OPT_LEVELS_3_PLUS_AND_SIZE, /* -O3 and above and -Os. */ common/config/arc/arc-common.c:#define OPT_LEVELS_3_PLUS_SPEED_ONLY OPT_LEVELS_3_PLUS common