public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andrey.vul at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/66146] New: call_once not C++11-compliant on ppc64le Date: Thu, 14 May 2015 18:31:00 -0000 [thread overview] Message-ID: <bug-66146-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66146 Bug ID: 66146 Summary: call_once not C++11-compliant on ppc64le Product: gcc Version: 5.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: andrey.vul at gmail dot com Target Milestone: --- std::call_once is not C++11 (or even N2447) compliant on ppc64le. According to N2447, "If the invocation of func results in an exception being thrown, the exception is propagated to the caller and the effects are as-if this invocation of call_once did not occur." Given the code #include <mutex> int call_count = 0; void func_() { printf("Inside func_ call_count %d\n", call_count); if (++call_count < 2) throw 0; } int main() { std::once_flag flag_; printf("Before calling call_once flag_: %d\n", *(int*)&flag_); try { std::call_once(flag_, func_); } catch(...) { printf("Inside catch all excepton flag_: %d\n", *(int*)&flag_); } printf("before the 2nd call to call_once flag_: %d\n", *(int*)&flag_); std::call_once(flag_, func_); } the output on amd64 is Before calling call_once flag_: 0 Inside func_ call_count 0 Inside catch all excepton flag_: 0 before the 2nd call to call_once flag_: 0 but on ppc64el is Before calling call_once flag_: 0 Inside func_ call_count 0 Inside catch all excepton flag_: 1 before the 2nd call to call_once flag_: 1 amd64 has the correct behavior. ppc64le gcc tested: $gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/powerpc64le-linux-gnu/4.9/lto-wrapper Target: powerpc64le-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.9.1-16ubuntu6' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libsanitizer --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-ppc64el/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-ppc64el --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-ppc64el --with-arch-directory=ppc64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-secureplt --with-cpu=power7 --with-tune=power8 --disable-multilib --enable-multiarch --disable-werror --with-long-double-128 --enable-checking=release --build=powerpc64le-linux-gnu --host=powerpc64le-linux-gnu --target=powerpc64le-linux-gnu Thread model: posix gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) $gcc-5.1 -v Using built-in specs. COLLECT_GCC=/home/andreyv/nfs/gcc/bin/gcc-5.1 COLLECT_LTO_WRAPPER=/nfs/home/andreyv/gcc/bin/../libexec/gcc/powerpc64le-unknown-linux-gnu/5.1.0/lto-wrapper Target: powerpc64le-unknown-linux-gnu Configured with: ../gcc-5.1.0/configure --prefix=/nfs/home/andreyv/gcc/ --program-suffix=-5.1 --enable-languages=c,c++,lto CFLAGS='-O2 -mtune=native' CXXFLAGS='-O2 -mtune=native' Thread model: posix gcc version 5.1.0 (GCC) Both versions compiled and run on Ubuntu 14.10 on a Power8. gcc-5.1 invocation: $ ~/nfshome/gcc/bin/g++-5.1 -std=c++11 -lpthread -Wl,-rpath=~/nfshome/gcc/lib64 -Wall -Wextra a.cc gcc-4.9 invocation: g++ -std=c++11 -lpthread -Wall -Wextra a.cc
next reply other threads:[~2015-05-14 18:31 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-14 18:31 andrey.vul at gmail dot com [this message] 2015-05-15 8:55 ` [Bug libstdc++/66146] " redi at gcc dot gnu.org 2015-05-15 15:12 ` andrey.vul at gmail dot com 2015-05-15 17:40 ` msebor at gcc dot gnu.org 2015-05-15 20:31 ` redi at gcc dot gnu.org 2015-05-19 17:36 ` andrey.vul at gmail dot com 2015-05-20 0:11 ` msebor at gcc dot gnu.org 2015-05-20 14:12 ` redi at gcc dot gnu.org 2015-05-20 14:36 ` bugdal at aerifal dot cx 2015-05-20 14:46 ` jakub at gcc dot gnu.org 2015-05-20 14:47 ` redi at gcc dot gnu.org 2015-05-20 14:51 ` bugdal at aerifal dot cx 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-06-27 18:18 ` pdimov at gmail dot com 2020-07-09 8:52 ` redi at gcc dot gnu.org 2020-08-27 13:56 ` kisha-nik at mail dot ru 2020-11-03 14:51 ` redi at gcc dot gnu.org 2020-11-03 18:45 ` cvs-commit at gcc dot gnu.org 2020-11-03 18:46 ` redi at gcc dot gnu.org 2020-11-03 18:46 ` redi at gcc dot gnu.org 2020-11-03 20:17 ` redi at gcc dot gnu.org 2020-12-17 9:08 ` tschwinge at gcc dot gnu.org 2020-12-17 9:58 ` redi at gcc dot gnu.org 2020-12-17 14:03 ` cvs-commit at gcc dot gnu.org 2021-02-04 15:16 ` libor.bukata at oracle dot com 2021-02-11 8:00 ` libor.bukata at oracle dot com 2021-02-11 13:29 ` redi at gcc dot gnu.org 2021-02-15 13:03 ` redi at gcc dot gnu.org 2021-02-15 14:13 ` bugdal at aerifal dot cx 2021-02-15 15:00 ` redi at gcc dot gnu.org 2021-02-15 17:08 ` bugdal at aerifal dot cx 2021-02-15 17:10 ` fw at gcc dot gnu.org 2021-02-15 17:30 ` bugdal at aerifal dot cx 2021-03-16 12:39 ` cvs-commit at gcc dot gnu.org 2021-04-07 6:22 ` unlvsur at live dot com 2021-04-07 10:03 ` redi at gcc dot gnu.org 2021-04-19 10:40 ` redi at gcc dot gnu.org 2021-04-27 11:37 ` jakub at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2022-02-10 23:20 ` redi at gcc dot gnu.org 2022-02-10 23:29 ` redi at gcc dot gnu.org 2022-12-02 1:25 ` lh_mouse at 126 dot com 2022-12-03 9:26 ` redi at gcc dot gnu.org 2024-03-14 11:55 ` cvs-commit at gcc dot gnu.org 2024-03-18 11:22 ` cvs-commit at gcc dot gnu.org 2024-03-18 14:03 ` cvs-commit at gcc dot gnu.org 2024-05-13 9:04 ` [Bug libstdc++/66146] call_once not C++11-compliant iains 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-66146-4@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: linkBe 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).