> From: Thomas Schwinge
> Date: Thu, 19 Oct 2023 12:42:26 +0200
> It's just GCC and Binutils/GDB, or are the top-level files also shared
> with additional projects?
Not sure if that counts as "shared", but I regularly drop
in* newlib to build simulator targets (*-elf, *-newabi).
That's git://sou
(Looks like this was committed as r14-3580-g597b9ec69bca8a)
> Cc: gcc@gcc.gnu.org, gcc-patc...@gcc.gnu.org, Eric Feng
> From: Eric Feng via Gcc
> gcc/testsuite/ChangeLog:
> PR analyzer/107646
> * gcc.dg/plugin/analyzer_cpython_plugin.c: Implements reference count
> * checking for PyOb
> From: Hans-Peter Nilsson
> Date: Thu, 26 May 2022 03:17:01 +0200
Regarding setting the default for the RWX-segment warning
per-target:
> How about the usual method, a line in the ld emulparams
> file for the target?
JFTR: no extra infrastructure bits needed. I found the
right spot, just a tr
> From: Jeff Law via Binutils
> Date: Mon, 25 Apr 2022 17:30:59 +0200
> On 4/25/2022 9:26 AM, Nick Clifton wrote:
> > Hi Jeff,
> >
> > Just FYI - I am also looking at adding in another warning. This
> > time for
> > when the linker creates a PT_LOAD segment which has all of the RWX
> > fla
Again, Debian 9. Doing "git gcc-backport a4aca1edaf37d43" on
releases/gcc-10 gave me:
[releases/gcc-10 83cf5a7c6a5] PR94600: fix volatile access to the whole of a
compound object.
Date: Sun Jul 5 20:50:52 2020 +0200
9 files changed, 276 insertions(+), 1 deletion(-)
create mode 100644 gcc/test
