missing features related to static chain
We have __builtin_call_with_static_chain, but I am missing builtins to get the address of the nested function itself (not of a trampoline) and the value one has to pass as static chain. Martin
How to test Arm cross compiler?
To my surprise, I have just found out that Arm simulator has been deprecated: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=aec7815b4b78d4dcd2261f1dab1092dbf4a9e0be. Taking that into account what is the "official" way to test the Arm cross compiler? Are there any documents? /J.D.
Re: How to test Arm cross compiler?
On 2/23/25 9:18 AM, Jan Dubiec via Gcc wrote: To my surprise, I have just found out that Arm simulator has been deprecated: https://sourceware.org/git/?p=binutils- gdb.git;a=commit;h=aec7815b4b78d4dcd2261f1dab1092dbf4a9e0be. Taking that into account what is the "official" way to test the Arm cross compiler? Are there any documents? These days I'd be QEMU is the best approach if you don't have hardware. Not sure if there's any reasonable documentation on it. The embecosm folks might have suitable docs on their web page along with the dejagnu configuration files. I personally prefer to use binfmt handlers since it doesn't require any dejagnu hackery and once the binfmt handlers are set up you can do so much more than just run individual tests in the testsuite easily. For example, if you have a RFS you can do full bootstraps rather than just testing crosses. jeff
gcc-15-20250223 is now available
Snapshot gcc-15-20250223 is now available on https://gcc.gnu.org/pub/gcc/snapshots/15-20250223/ and on various mirrors, see https://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 15 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch master revision bf0aa9dc8826b1d2a71e52754c117228134825b5 You'll find: gcc-15-20250223.tar.xz Complete GCC SHA256=075ea91e749bc73524c9fcaccabc96189bf40f7dc428e29a09effac5f73838b5 SHA1=3ef76b6a846a672c74ff024051d34122d0450f55 Diffs from 15-20250216 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-15 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
