Adjust offset of array reference in named address space

2021-01-08 Thread Tucker Kern via Gcc
Hi, I'm implementing named addresses spaces for a Harvard architecture machine to support copying data from instruction memory to data memory. This is achieved via a special instruction. e.g. think AVR and progmem/__flash. However, the instruction memory is narrower than the data memory (12 vs 16

gcc-9-20210108 is now available

2021-01-08 Thread GCC Administrator via Gcc
Snapshot gcc-9-20210108 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20210108/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: [RFC] restricting aliasing by standard containers (PR 98465)

2021-01-08 Thread Martin Sebor via Gcc
On 1/8/21 12:51 AM, Richard Biener wrote: On Thu, Jan 7, 2021 at 10:41 PM Martin Sebor wrote: The test case in PR 98465 brings to light a problem we've discussed before (e.g., PR 93971) where a standard container (std::string in this case but the problem applies to any class that owns and mana

Re: Fw: Problems with compiling autogen with GCC8 or newer versions

2021-01-08 Thread Jeff Law via Gcc
On 1/8/21 10:39 AM, Bruce Korb via Gcc wrote: > Hi, > > You are supposed to be able to post once you've subscribed. > > Also, GCC's code analysis is wrong. "name_bf" contains *NO MORE* than > MAXNAMELEN characters. That is provable. > > "def_str" points into a buffer of size ((MAXNAMELEN * 2) +

Re: Fw: Problems with compiling autogen with GCC8 or newer versions

2021-01-08 Thread Bruce Korb via Gcc
Hi, You are supposed to be able to post once you've subscribed. Also, GCC's code analysis is wrong. "name_bf" contains *NO MORE* than MAXNAMELEN characters. That is provable. "def_str" points into a buffer of size ((MAXNAMELEN * 2) + 8) and at an offset maximum of MAXNAMELEN+1 (also provable