Re: gcc 3.2.3 x64 negative indexes

Problem solved. I didn't have this: #define SIZE_TYPE (TARGET_64BIT ? "long unsigned int" : "unsigned int") because I wasn't including x86_64.h. This is the first time I have attempted to go to 64-bit pointers so I wasn't aware this even existed. So here it is doing Win64 ABI: D:\devel\gcc\gc

gcc-13-20240210 is now available

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

Re: gcc 3.2.3 x64 negative indexes

(replying to Joe Monk) > It appears that this is not an issue that this version of GCC is > architected to be able to solve. > The first 64-bit PC processor, the AMD opteron series, was launched on > April 22, 2003. > GCC 3.2.3 was released on April 25, 2003. Jakub has already shown correct x64

Re: Building gcc with "-O -g"?

On Sat, Feb 10, 2024 at 07:35:22PM +0100, Marc Glisse wrote: > On Sat, 10 Feb 2024, Steve Kargl via Gcc wrote: > > > So, how does one biulding all parts of gcc with "-O -g"? > > > > In my shell script, I have > > > > CFLAGS="-O -g" > > export CFLAGS > > > > CXXFLAGS="-O -g" > > export CXXFLAGS

Re: Building gcc with "-O -g"?

On Sat, 10 Feb 2024, Steve Kargl via Gcc wrote: So, how does one biulding all parts of gcc with "-O -g"? In my shell script, I have CFLAGS="-O -g" export CFLAGS CXXFLAGS="-O -g" export CXXFLAGS BOOT_CFLAGS="-O -g" export BOOT_CFLAGS ../gcc/configure --prefix=$HOME/work --enable-languages=c,

Building gcc with "-O -g"?

So, how does one biulding all parts of gcc with "-O -g"? In my shell script, I have CFLAGS="-O -g" export CFLAGS CXXFLAGS="-O -g" export CXXFLAGS BOOT_CFLAGS="-O -g" export BOOT_CFLAGS ../gcc/configure --prefix=$HOME/work --enable-languages=c,c++,fortran \ --enable-bootstrap --disable-libssp

Re: gcc 3.2.3 x64 negative indexes

It appears that this is not an issue that this version of GCC is architected to be able to solve. The first 64-bit PC processor, the AMD opteron series, was launched on April 22, 2003. GCC 3.2.3 was released on April 25, 2003. "*Opteron* is AMD

Re: Analyzer test failures

On 2024-02-10 6:52 a.m., Iain Sandoe wrote: On 10 Feb 2024, at 11:33, FX Coudert via Gcc wrote: I’m seeing the following analyzer test failures on darwin. They were introduced in December, when the tests were moved around: FAIL: c-c++-common/analyzer/fd-glibc-byte-stream-socket.c FAIL: c-c++

Re: gcc 3.2.3 x64 negative indexes

I have it down to a deliberate conversion from signed to unsigned: temp.txt: bbb piss ccc 32 32 temp.txt: bbb piss ccc2 0 1 temp.txt: bbb piss ddd -2 temp.txt: bbb - in convert temp.txt: bbb - converting to integer temp.txt: bbb y stage1 temp.txt: bbb y stage2 temp.txt: bbb y outprec thing, inprec

Re: Analyzer test failures

> On 10 Feb 2024, at 11:33, FX Coudert via Gcc wrote: > I’m seeing the following analyzer test failures on darwin. They were > introduced in December, when the tests were moved around: > > FAIL: c-c++-common/analyzer/fd-glibc-byte-stream-socket.c > FAIL: c-c++-common/analyzer/fd-manpage-geta

Analyzer test failures

Hi, I’m seeing the following analyzer test failures on darwin. They were introduced in December, when the tests were moved around: FAIL: c-c++-common/analyzer/fd-glibc-byte-stream-socket.c FAIL: c-c++-common/analyzer/fd-manpage-getaddrinfo-client.c FAIL: c-c++-common/analyzer/fd-mappage-getaddri