public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/109849] suboptimal code for vector walking loop Date: Tue, 28 Nov 2023 12:41:03 +0000 [thread overview] Message-ID: <bug-109849-4-isoh4yi5VB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109849-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849 --- Comment #28 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Martin Jambor from comment #27) > Unfortunately I cannot reproduce this, the above (on pristine master > commit 006e90e1344 on an x86_64-linux) results in: > > Running target unix/-D_GLIBCXX_USE_CXX11_ABI=0 > Running > /home/mjambor/gcc/small/src/libstdc++-v3/testsuite/libstdc++-dg/conformance. > exp ... > PASS: 21_strings/basic_string/operators/char/1.cc -std=gnu++17 (test for > excess errors) > PASS: 21_strings/basic_string/operators/char/1.cc -std=gnu++17 execution > test Oops, sorry, that particular FAIL needs either --target_board=unix/-D_GLIBCXX_USE_CXX11_ABI=0/-D_GLIBCXX_DEBUG which then makes it fail for all -std modes: Schedule of variations: unix/-D_GLIBCXX_USE_CXX11_ABI=0/-D_GLIBCXX_DEBUG Running target unix/-D_GLIBCXX_USE_CXX11_ABI=0/-D_GLIBCXX_DEBUG Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/test/src/gcc/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/test/src/gcc/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... FAIL: 21_strings/basic_string/operators/char/1.cc -std=gnu++11 execution test FAIL: 21_strings/basic_string/operators/char/1.cc -std=gnu++14 execution test FAIL: 21_strings/basic_string/operators/char/1.cc -std=gnu++17 execution test FAIL: 21_strings/basic_string/operators/char/1.cc -std=gnu++20 execution test FAIL: 21_strings/basic_string/operators/char/1.cc -std=gnu++23 execution test FAIL: 21_strings/basic_string/operators/char/1.cc -std=gnu++26 execution test Or just set GLIBCXX_TESTSUITE_STDS="17,20" in the env before running the test: Schedule of variations: unix/-D_GLIBCXX_USE_CXX11_ABI=0 Running target unix/-D_GLIBCXX_USE_CXX11_ABI=0 Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/test/src/gcc/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/test/src/gcc/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... FAIL: 21_strings/basic_string/operators/char/1.cc -std=gnu++20 execution test It seems I picked a bad example to give, which requires additional options to FAIL. Many of the other FAILs do not require _GLIBCXX_DEBUG or -std=gnu++20 to FAIL, but the -D_GLIBCXX_USE_CXX11_ABI=0 option is necessary, at least for all the ones I inspected. That option isn't used by default, but I run the full testsuite with that several times a day, and with GLIBCXX_TESTSUITE_STDS=98,11,14,17,20,23,26. > Can you please try if > https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638318.html > fixes this? Testing now ...
next prev parent reply other threads:[~2023-11-28 12:41 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-13 22:26 [Bug middle-end/109849] New: " hubicka at gcc dot gnu.org 2023-05-13 22:32 ` [Bug middle-end/109849] " pinskia at gcc dot gnu.org 2023-05-13 22:40 ` pinskia at gcc dot gnu.org 2023-05-14 5:57 ` amonakov at gcc dot gnu.org 2023-05-14 9:58 ` hubicka at ucw dot cz 2023-05-14 10:01 ` hubicka at ucw dot cz 2023-05-15 6:56 ` rguenth at gcc dot gnu.org 2023-05-17 14:53 ` hubicka at gcc dot gnu.org 2023-05-17 20:36 ` rguenth at gcc dot gnu.org 2023-05-18 9:35 ` hubicka at gcc dot gnu.org 2023-05-18 11:54 ` rguenth at gcc dot gnu.org 2023-05-18 13:00 ` hubicka at gcc dot gnu.org 2023-05-23 9:57 ` cvs-commit at gcc dot gnu.org 2023-05-23 10:10 ` rguenth at gcc dot gnu.org 2023-05-24 11:19 ` cvs-commit at gcc dot gnu.org 2023-06-16 14:20 ` hubicka at gcc dot gnu.org 2023-06-18 16:59 ` cvs-commit at gcc dot gnu.org 2023-06-19 16:28 ` cvs-commit at gcc dot gnu.org 2023-06-26 16:30 ` cvs-commit at gcc dot gnu.org 2023-06-28 9:47 ` cvs-commit at gcc dot gnu.org 2023-06-29 20:46 ` cvs-commit at gcc dot gnu.org 2023-06-30 14:28 ` cvs-commit at gcc dot gnu.org 2023-11-19 15:25 ` hubicka at gcc dot gnu.org 2023-11-21 14:17 ` cvs-commit at gcc dot gnu.org 2023-11-21 15:12 ` hubicka at gcc dot gnu.org 2023-11-24 16:35 ` cvs-commit at gcc dot gnu.org 2023-11-24 17:00 ` cvs-commit at gcc dot gnu.org 2023-11-24 17:00 ` jamborm at gcc dot gnu.org 2023-11-27 14:39 ` rguenth at gcc dot gnu.org 2023-11-28 9:33 ` redi at gcc dot gnu.org 2023-11-28 10:32 ` jamborm at gcc dot gnu.org 2023-11-28 12:41 ` redi at gcc dot gnu.org [this message] 2023-11-28 13:29 ` redi at gcc dot gnu.org 2023-11-28 15:29 ` redi at gcc dot gnu.org 2023-11-28 22:21 ` redi at gcc dot gnu.org 2023-11-29 12:27 ` hubicka at ucw dot cz 2023-11-29 15:25 ` cvs-commit at gcc dot gnu.org 2024-01-03 17:41 ` jamborm 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-109849-4-isoh4yi5VB@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).