From: Andreas Schwab <schwab@suse.de>
To: "Frédéric Bérat via Libc-alpha" <libc-alpha@sourceware.org>
Cc: "Frédéric Bérat" <fberat@redhat.com>, siddhesh@gotplt.org
Subject: Re: [PATCH v6 00/14] Allow glibc to be built with _FORTIFY_SOURCE
Date: Thu, 06 Jul 2023 15:38:42 +0200 [thread overview]
Message-ID: <mvma5w9qhwd.fsf@suse.de> (raw)
In-Reply-To: <20230705143822.275049-1-fberat@redhat.com> (=?utf-8?B?IkZy?= =?utf-8?B?w6lkw6lyaWMgQsOpcmF0?= via Libc-alpha"'s message of "Wed, 5 Jul 2023 16:38:06 +0200")
https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/glibc/s/s390x
gcc ../sysdeps/s390/memmove-c.c -c -std=gnu11 -fgnu89-inline -O2 -Wall -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong -fno-common -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wstrict-prototypes -Wold-style-definition -fmath-errno -mlong-double-128 -fPIE -ftls-model=initial-exec -I../include -I/home/abuild/rpmbuild/BUILD/glibc-2.37.9000.594.g5324d25842/cc-base/string -I/home/abuild/rpmbuild/BUILD/glibc-2.37.9000.594.g5324d25842/cc-base -I../sysdeps/unix/sysv/linux/s390/s390-64 -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/unix/sysv/linux/s390/fpu -I../sysdeps/s390/fpu -I../sysdeps/unix/sysv/linux/s390 -I../sysdeps/s390/nptl -I../sysdeps/ieee754/ldbl-64-128 -I../sysdeps/ieee754/ldbl-opt -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/s390/s390-64 -I../sysdeps/wordsize-64 -I../sysdeps/s390/multiarch -I../sysdeps/s390 -I../sysdeps/ieee754/ldbl-128 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -D_LIBC_REENTRANT -include /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.594.g5324d25842/cc-base/libc-modules.h -DMODULE_NAME=libc -include ../include/libc-symbols.h -DPIC -DTOP_NAMESPACE=glibc -o /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.594.g5324d25842/cc-base/string/memmove-c.o -MD -MP -MF /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.594.g5324d25842/cc-base/string/memmove-c.o.dt -MT /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.594.g5324d25842/cc-base/string/memmove-c.o
In file included from ../sysdeps/s390/memmove-c.c:36:
../string/memmove.c:44:1: error: optimization attribute on 'memmove' follows definition but the attribute doesn't match [-Werror=attributes]
44 | {
| ^
In file included from ../include/sys/cdefs.h:10,
from ../include/features.h:503,
from ../posix/sys/types.h:25,
from ../include/sys/types.h:1,
from ../include/string.h:6,
from ../string/memmove.c:20:
../string/bits/string_fortified.h:34:8: note: previous definition of 'memmove' with type 'void *(void *, const void *, size_t)' {aka 'void *(void *, const void *, long unsigned int)'}
34 | __NTH (memmove (void *__dest, const void *__src, size_t __len))
| ^~~~~~~
../misc/sys/cdefs.h:81:62: note: in definition of macro '__NTH'
81 | # define __NTH(fct) __attribute__ ((__nothrow__ __LEAF)) fct
| ^~~
cc1: all warnings being treated as errors
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-07-06 13:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:38 Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 01/14] " Frédéric Bérat
2023-07-05 14:41 ` Siddhesh Poyarekar
2023-07-05 14:38 ` [PATCH v6 02/14] Exclude routines from fortification Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 03/14] sysdeps: Ensure ieee128*_chk routines to be properly named Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 04/14] string: Ensure *_chk routines have their hidden builtin definition available Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 05/14] stdio: " Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 06/14] misc/sys/cdefs.h: Create FORTIFY redirects for internal calls Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 07/14] wchar: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 08/14] posix/bits/unistd.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 09/14] unistd: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 10/14] misc/bits/select2.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 11/14] misc/bits/syslog.h: Clearly separate declaration from definition Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 12/14] libio/bits/stdio2.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 13/14] libio/bits/stdio2-decl.h: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 14/14] sysdeps/ieee754/ldbl-128ibm-compat: Fix warn unused result Frédéric Bérat
2023-07-06 13:15 ` [PATCH v6 00/14] Allow glibc to be built with _FORTIFY_SOURCE Andreas Schwab
2023-07-06 13:41 ` Frederic Berat
2023-07-06 13:46 ` Andreas Schwab
2023-07-10 5:57 ` Frederic Berat
2023-07-06 13:38 ` Andreas Schwab [this message]
2023-07-10 5:56 ` Frederic Berat
2023-07-11 8:44 ` Andreas Schwab
2023-07-12 13:35 ` Frederic Berat
2023-07-12 13:38 ` Andreas Schwab
2023-07-12 13:42 ` Frederic Berat
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=mvma5w9qhwd.fsf@suse.de \
--to=schwab@suse.de \
--cc=fberat@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).