public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc.gnu.org+lufm at davidak dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108854] New: tbb-2021.8.0 fails on i686-linux (32-bit) Date: Sun, 19 Feb 2023 23:53:50 +0000 [thread overview] Message-ID: <bug-108854-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108854 Bug ID: 108854 Summary: tbb-2021.8.0 fails on i686-linux (32-bit) Product: gcc Version: 11.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gcc.gnu.org+lufm at davidak dot de Target Milestone: --- Created attachment 54490 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54490&action=edit full build log Hello, i tried to build tbb_2021_8 for i686-linux platform on x86_64-linux. The build fails and the log said i should create a bug report here. I'm not a developer and never used gcc manually, so please be patient with me. I don't know how to get the "preprocessed file (*.i*) that triggers the bug", but otherwise you should have all requested information. I added those flags to the build you see the log of in the attachment: # For 32-bit build cmakeFlags = [ "-DCMAKE_CXX_FLAGS=-m32" ]; NIX_CFLAGS_COMPILE = [ "-Wall -Wextra -fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations -fsanitize=undefined" ]; You can reproduce the issue using the Nix package manager and this command: nix-build https://github.com/davidak/nixpkgs/archive/refs/heads/tbb-split-32-bit-fix.zip --system i686-linux -A tbb_2021_8 Downstream issue: https://github.com/oneapi-src/oneTBB/issues/1030 (maybe the issue is in their code) The code: https://github.com/oneapi-src/oneTBB/tree/v2021.8.0 Tested on NixOS 22.11.2620.de5448dab58 with Intel Core i9 9900K
next reply other threads:[~2023-02-19 23:53 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-19 23:53 gcc.gnu.org+lufm at davidak dot de [this message] 2023-02-20 8:34 ` [Bug middle-end/108854] tbb-2021.8.0 fails on i686-linux (32-bit), internal compiler error: in expand_expr_real_1, at expr.c:10281 rguenth at gcc dot gnu.org 2023-02-20 9:52 ` jakub at gcc dot gnu.org 2023-02-20 12:14 ` redi at gcc dot gnu.org 2023-02-20 23:31 ` pinskia at gcc dot gnu.org 2023-02-20 23:39 ` pinskia at gcc dot gnu.org 2023-02-21 17:00 ` gcc.gnu.org+lufm at davidak dot de 2023-02-21 18:32 ` jakub at gcc dot gnu.org 2023-02-22 9:40 ` slyfox at gcc dot gnu.org 2023-02-22 13:22 ` jakub at gcc dot gnu.org 2023-02-22 15:40 ` [Bug middle-end/108854] [10/11/12/13 Regression] " jakub at gcc dot gnu.org 2023-02-23 15:55 ` [Bug middle-end/108854] [10/11/12/13 Regression] tbb-2021.8.0 fails on i686-linux (32-bit), internal compiler error: in expand_expr_real_1, at expr.c:10281 since r10-4511-g6cf67b62c8cda035dccac jakub at gcc dot gnu.org 2023-02-23 16:16 ` jakub at gcc dot gnu.org 2023-02-24 10:06 ` cvs-commit at gcc dot gnu.org 2023-02-24 10:07 ` [Bug middle-end/108854] [10/11/12 " jakub at gcc dot gnu.org 2023-03-19 5:29 ` cvs-commit at gcc dot gnu.org 2023-03-20 10:27 ` [Bug middle-end/108854] [10/11 " jakub at gcc dot gnu.org 2023-05-02 20:15 ` cvs-commit at gcc dot gnu.org 2023-05-03 10:39 ` [Bug middle-end/108854] [10 " jakub at gcc dot gnu.org 2023-05-03 15:21 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:25 ` jakub 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-108854-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).