public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77691] [8/9/10/11 regression] experimental/memory_resource/resource_adaptor.cc FAILs
Date: Wed, 17 Feb 2021 16:30:10 +0000 [thread overview]
Message-ID: <bug-77691-4-xZHGfDUkmc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-77691-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77691
--- Comment #45 from John David Anglin <danglin at gcc dot gnu.org> ---
We see this fail on hppa-linux:
https://buildd.debian.org/status/fetch.php?pkg=mysql-8.0&arch=hppa&ver=8.0.23-3&stamp=1613526368&raw=0
[ 49%] Building CXX object
storage/innobase/CMakeFiles/innobase.dir/api/api0api.cc.o
cd /<<PKGBUILDDIR>>/builddir/storage/innobase && /usr/bin/hppa-linux-gnu-g++
-DBOOST_GEOMETRY_SQRT_CHECK_FINITENESS -DCOMPILER_HINTS -DHAVE_CONFIG_H
-DHAVE_FALLOC_FL_ZERO_RANGE=1 -DHAVE_FALLOC_PUNCH_HOLE_AND_KEEP_SIZE=1
-DHAVE_IB_GCC_ATOMIC_THREAD_FENCE=1 -DHAVE_IB_GCC_SYNC_SYNCHRONISE=1
-DHAVE_IB_LINUX_FUTEX=1 -DHAVE_LZ4=1 -DHAVE_NANOSLEEP=1 -DHAVE_SCHED_GETCPU=1
-DHAVE_TLSv13 -DLINUX_NATIVE_AIO=1 -DLOG_SUBSYSTEM_TAG=\"InnoDB\"
-DLZ4_DISABLE_DEPRECATE_WARNINGS -DMUTEX_EVENT -DMYSQL_SERVER -DPFS_DIRECT_CALL
-DRAPIDJSON_NO_SIZETYPEDEFINE -DRAPIDJSON_SCHEMA_USE_INTERNALREGEX=0
-DRAPIDJSON_SCHEMA_USE_STDREGEX=1 -DUNIV_LINUX -D_FILE_OFFSET_BITS=64
-D_GNU_SOURCE -D_USE_MATH_DEFINES -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
-I/<<PKGBUILDDIR>>/builddir -I/<<PKGBUILDDIR>>/builddir/include
-I/<<PKGBUILDDIR>> -I/<<PKGBUILDDIR>>/include
-I/<<PKGBUILDDIR>>/storage/innobase -I/<<PKGBUILDDIR>>/storage/innobase/include
-I/<<PKGBUILDDIR>>/storage/innobase/handler -I/<<PKGBUILDDIR>>/sql
-I/<<PKGBUILDDIR>>/sql/auth -isystem /<<PKGBUILDDIR>>/extra/rapidjson/include
-isystem /usr/include/editline -std=c++14 -fno-omit-frame-pointer -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -Wformat -Werror=format-security -Wall
-Wextra -Wformat-security -Wvla -Wundef -Woverloaded-virtual -Wcast-qual
-Wimplicit-fallthrough=2 -Wstringop-truncation -Wsuggest-override -Wlogical-op
-Wno-unused-parameter -Wno-cast-qual -DDBUG_OFF -ffunction-sections
-fdata-sections -O2 -g -DNDEBUG -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -o
CMakeFiles/innobase.dir/api/api0api.cc.o -c
/<<PKGBUILDDIR>>/storage/innobase/api/api0api.cc
In file included from
/<<PKGBUILDDIR>>/storage/innobase/include/sync0types.h:42,
from /<<PKGBUILDDIR>>/storage/innobase/include/univ.i:588,
from /<<PKGBUILDDIR>>/storage/innobase/os/file.h:47,
from /<<PKGBUILDDIR>>/storage/innobase/include/os0file.h:47,
from /<<PKGBUILDDIR>>/storage/innobase/include/api0misc.h:40,
from /<<PKGBUILDDIR>>/storage/innobase/api/api0api.cc:41:
/<<PKGBUILDDIR>>/storage/innobase/include/ut0new.h: In instantiation of ‘class
ut_allocator<PolicyMutex<OSTrackMutex<GenericPolicy> > >’:
/<<PKGBUILDDIR>>/storage/innobase/include/ut0new.h:1033:19: required from
‘void ut_delete(T*) [with T = PolicyMutex<OSTrackMutex<GenericPolicy> >]’
/<<PKGBUILDDIR>>/storage/innobase/include/dict0mem.h:2568:5: required from
here
/<<PKGBUILDDIR>>/storage/innobase/include/ut0new.h:583:28: error: static
assertion failed: ut_allocator does not support over-aligned types. Use
aligned_memory or another similar allocator for this type.
583 | static_assert(alignof(T) <= alignof(std::max_align_t),
| ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[4]: *** [storage/innobase/CMakeFiles/innobase.dir/build.make:85:
storage/innobase/CMakeFiles/innobase.dir/api/api0api.cc.o] Error 1
It seems we have 8-byte alignment specified using std::max_align_t and 16-byte
alignment for pthread mutexes and malloc.
next prev parent reply other threads:[~2021-02-17 16:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-77691-4@http.gcc.gnu.org/bugzilla/>
2020-05-13 7:51 ` cvs-commit at gcc dot gnu.org
2020-05-26 10:15 ` cvs-commit at gcc dot gnu.org
2020-10-31 21:16 ` redi at gcc dot gnu.org
2021-02-17 16:30 ` danglin at gcc dot gnu.org [this message]
2021-02-17 16:46 ` redi at gcc dot gnu.org
2021-02-17 16:58 ` dave.anglin at bell dot net
2021-03-25 15:13 ` seurer at gcc dot gnu.org
2021-05-14 9:48 ` [Bug libstdc++/77691] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:08 ` rguenth at gcc dot gnu.org
2022-05-27 9:36 ` [Bug libstdc++/77691] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:32 ` jakub at gcc dot gnu.org
2023-01-05 21:26 ` danglin at gcc dot gnu.org
2023-01-08 23:10 ` danglin at gcc dot gnu.org
2023-01-09 11:20 ` redi at gcc dot gnu.org
2023-01-09 22:14 ` dave.anglin at bell dot net
2023-01-12 20:59 ` cvs-commit at gcc dot gnu.org
2023-07-07 10:31 ` [Bug libstdc++/77691] [11/12/13/14 " rguenth at gcc dot gnu.org
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=bug-77691-4-xZHGfDUkmc@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).