I have been looking and looking until my eyes have started to cross.
Here's my problem.
The only way I have been able to affect an entire build of GCC, for
example in order to do a "-ggdb -O0" build of the entire compiler and its
libraries, has been to do something like this:
mkdir build
Krister Walfridsson via Gcc writes:
> I have continued working on my translation validator, smtgcc [1]. Here
> is an update of what I have done since the end-of-year update.
>
>
> smtgcc-tv-backend
> -
> The main focus has been improving the smtgcc-tv-backend tool which
> checks t
Hello,
it seems that the variants without a _1, _2, ... are explicitly provided
(libatomic_i.h):
/* And the generic sized versions. */
void libat_load (size_t, void *, void *, int) MAN(load);
void libat_store (size_t, void *, void *, int) MAN(store);
void libat_exchange (size_t, void *, void *,
Snapshot gcc-12-20250702 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250702/
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
I am pleased to announce that the GCC Steering Committee has appointed
Tamar Christina as AArch64 maintainer. I am pleased to announce that the
GCC Steering Committee has appointed Alex Coplan, Alice Carlotti, Andrew
Pinski, and Wilco Dijkstra as AArch64 reviewers.
Please join me in congratulatin
Hello,
for the RISC-V target, I would like to use the -march=rv64imc ISA variant.
However, there is an issue with the libatomic for this target in the RTEMS
configuration. For this test code:
#include
bool tas(atomic_flag *f)
{
return atomic_flag_test_and_set(f);
}
GCC 15 generates:
On Tue, 2025-07-01 at 23:04 +0100, Joern Wolfgang Rennecke wrote:
> Quite often I see a test quickly written to test some new feature
> (bug
> fix, extension or optimization) that has a couple of functions to
> cover
> various aspects of the feature, checked all together with a single
> scan-tre
