The GNU Compiler Collection version 10.5 has been released.
GCC 10.5 is a bug-fix release from the GCC 10 branch
containing important fixes for regressions and serious bugs in
GCC 10.4 with more than 155 bugs fixed since the previous release.
This is also the last release from the GCC 10 branch,
After the GCC 10.5 release the GCC 10 branch is now closed.
Thanks,
Richard.
On 07/07/2023 00:27, André Albergaria Coelho via Gcc wrote:
What if the user chooses in own ABI, say specifying a config file like
My abi
" Parameters = pushed in stack"
say
gcc -abi "My abi" some.c -o some
what would be the problems of specifying an ABI?? would that improve the
usage of u
On Thu, Jul 6, 2023 at 11:15 PM Daria Shatalinska via Gcc
wrote:
>
> Hello,
>
> My name is Daria Shatalinska and I am a Project Manager at Freelancer. I am
> contacting you to see if you might be interested in collaborating with us
> on a project for NASA's Open Innovation Services program (NOIS2)
Hi all,
Am 7/3/2023 um 9:20 PM schrieb Olivier Dion:
Hi all,
This is a request for comments on extending the atomic builtins API to
help avoiding redundant memory barriers. Indeed, there are
discrepancies between the Linux kernel consistency memory model (LKMM)
and the C11/C++11 memory consis
On Tue, 04 Jul 2023, Peter Zijlstra wrote:
> On Mon, Jul 03, 2023 at 03:20:31PM -0400, Olivier Dion wrote:
[...]
>> On x86-64 (gcc 13.1 -O2) we get:
>>
>> t0():
>> movl$1, x(%rip)
>> movl$1, %eax
>> xchgl dummy(%rip), %eax
>> lock orq $0, (%rsp)
Another related tool is mcdc-checker. This tool analyses code for
conditions that require mcdc analysis based on some research
that proves it isn't needed if the logic is properly structured. It can
suggest alternatives that avoid the need for mcdc analysis.
Research papers are linked there also.
Hi,
I would like to know what is the official stand of GCC on optimization
of atomic builtins? More precisely, optimization of redundant memory
fences.
I am aware that Clang does some peephole optimization on redundant
fences, but this seem to be limited to a single basic block and does not
reco
On 7/4/23 06:23, Jonathan Wakely wrote:
On Tue, 4 Jul 2023 at 10:47, Peter Zijlstra wrote:
On Mon, Jul 03, 2023 at 03:20:31PM -0400, Olivier Dion wrote:
int x = 0;
int y = 0;
int r0, r1;
int dummy;
void t0(void)
{
__atomic_store_n(&x, 1, __ATOMIC_RELAXED);
On Fri, Jul 07, 2023 at 10:04:06AM -0400, Olivier Dion wrote:
> On Tue, 04 Jul 2023, Peter Zijlstra wrote:
> > On Mon, Jul 03, 2023 at 03:20:31PM -0400, Olivier Dion wrote:
> [...]
> >> On x86-64 (gcc 13.1 -O2) we get:
> >>
> >> t0():
> >> movl$1, x(%rip)
> >> movl$1
On Fri, 07 Jul 2023, Jonas Oberhauser wrote:
[...]
>> This is a request for comments on extending the atomic builtins API to
>> help avoiding redundant memory barriers. Indeed, there are
>> discrepancies between the Linux kernel consistency memory model (LKMM)
>> and the C11/C++11 memory consiste
Snapshot gcc-12-20230707 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20230707/
and on various mirrors, see http://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
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Congratulations on the new release. May it be as boring as we hope.
--
Dr Richard
13 matches
Mail list logo
