gcc-12-20240606 is now available

Snapshot gcc-12-20240606 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20240606/ and on various mirrors, see https://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 12 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: How to target a processor with very primitive addressing modes?

On Thu, Jun 06, 2024 at 08:28:57PM +0200, Mikael Pettersson via Gcc wrote: > I'm working on a GCC backend for an older processor with very > primitive addressing support. The only way to load from or store to > memory is to compute the address into a register, and then use that > register in the lo

How to target a processor with very primitive addressing modes?

I'm working on a GCC backend for an older processor with very primitive addressing support. The only way to load from or store to memory is to compute the address into a register, and then use that register in the load or store instruction. There are no immediate or register offsets in memory acces

libgcov on a standalone platform embedded controller

Guy, I have been trying to get libgcov working. Will you please give me some guidance with a working example? I could really use some good old fashion hand holding to gcov to work in a standalone environment. I have tried the following 1. invoke __gcov_dump() but then i get this error lib

Re: What is the purpose of these two fixincludes?

> On 6 Jun 2024, at 12:41, Sam James via Gcc wrote: > > Andi Kleen via Gcc writes: > >> FX Coudert via Gcc writes: >> >>> I am trying to reduce the number of unneeded fixincludes that are used >>> on darwin (because fixincluded headers make it impossible to change >>> SDK once the compile

Re: What is the purpose of these two fixincludes?

Andi Kleen via Gcc writes: > FX Coudert via Gcc writes: > >> Hi, >> >> I am trying to reduce the number of unneeded fixincludes that are used >> on darwin (because fixincluded headers make it impossible to change >> SDK once the compiler is built, which is common practice in the macOS >> world,

Re: What is the purpose of these two fixincludes?

Hi, > I usually just install with install-no-fixedincludes, but really this > should probably be a configure option and default to on. It would be great if we could measure what fixincludes are still needed, on which targets. Could we possibly modify contrib/test_summary to list the fixincluded