From: John David Anglin <dave.anglin@bell.net>
To: libc-alpha@sourceware.org
Subject: hppa: glibc trunk build fails with gcc trunk
Date: Fri, 6 Oct 2023 14:28:07 -0400 [thread overview]
Message-ID: <b580e9f4-9a33-4ed4-8043-8aa8f7b6cccc@bell.net> (raw)
/home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/objdir/gcc/ dl-find_object.c -c -std=gnu11 -fgnu89-inline -g -O2 -Wall -Wwrite-strings
-Wundef -Werror -fmerge-all-constants -frounding-math -fno-stack-protector -fno-common -Wp,-U_FORTIFY_SOURCE -Wstrict-prototypes
-Wold-style-definition -fmath-errno -fno-pie -fno-stack-protector -DSTACK_PROTECTOR_LEVEL=0 -ftls-model=initial-exec -I../include
-I/home/dave/gnu/glibc/objdir/elf -I/home/dave/gnu/glibc/objdir -I../sysdeps/unix/sysv/linux/hppa -I../sysdeps/hppa/nptl
-I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu
-I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/hppa/hppa1.1 -I../sysdeps/wordsize-32
-I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/hppa/fpu -I../sysdeps/hppa -I../sysdeps/ieee754 -I../sysdeps/generic
-I.. -I../libio -I. -nostdinc -isystem /home/dave/gnu/gcc/objdir/gcc/include -isystem /home/dave/gnu/gcc/objdir/gcc/include-fixed -isystem
/usr/include -D_LIBC_REENTRANT -include /home/dave/gnu/glibc/objdir/libc-modules.h -DMODULE_NAME=libc -include ../include/libc-symbols.h
-DTOP_NAMESPACE=glibc -o /home/dave/gnu/glibc/objdir/elf/dl-find_object.o -MD -MP -MF /home/dave/gnu/glibc/objdir/elf/dl-find_object.o.dt -MT
/home/dave/gnu/glibc/objdir/elf/dl-find_object.o
In file included from ../include/atomic.h:49,
from dl-find_object.c:20:
In function ‘_dlfo_update_init_seg’,
inlined from ‘_dl_find_object_update_1’ at dl-find_object.c:689:30,
inlined from ‘_dl_find_object_update’ at dl-find_object.c:805:13:
../sysdeps/unix/sysv/linux/hppa/atomic-machine.h:44:4: error: ‘__atomic_store_4’ writing 4 bytes into a region of size 0 overflows the
destination [-Werror=stringop-overflow=]
44 | __atomic_store_n ((mem), (val), __ATOMIC_RELAXED); \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
dl-find_object.c:644:3: note: in expansion of macro ‘atomic_store_relaxed’
644 | atomic_store_relaxed (&seg->size, new_seg_size);
| ^~~~~~~~~~~~~~~~~~~~
In function ‘_dl_find_object_update’:
*cc1: note: destination object is likely at address zero*
Dave
--
John David Anglin dave.anglin@bell.net
reply other threads:[~2023-10-06 18:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b580e9f4-9a33-4ed4-8043-8aa8f7b6cccc@bell.net \
--to=dave.anglin@bell.net \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).