public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108681] New: gcc hangs compiling opencv/channels_combine.cpp for aarch64 Date: Mon, 06 Feb 2023 05:19:31 +0000 [thread overview] Message-ID: <bug-108681-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108681 Bug ID: 108681 Summary: gcc hangs compiling opencv/channels_combine.cpp for aarch64 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: raj.khem at gmail dot com Target Milestone: --- GCC-trunk as of 31924665c86d47af6b1f22a74f594f2e1dc0ed2d is taking a long long time, probably a hang since I cancelled it after 12 mins ) compiling this file https://uclibc.org/~kraj/channels_combine.i aarch64-yoe-linux/aarch64-yoe-linux-g++ channels_combine.i -O2 ( hangs ) It compiled ok with -O0,-Os,-Og,-Oz but not with -O1,-O2,-O3
next reply other threads:[~2023-02-06 5:19 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-06 5:19 raj.khem at gmail dot com [this message] 2023-02-06 5:41 ` [Bug middle-end/108681] " pinskia at gcc dot gnu.org 2023-02-06 6:08 ` [Bug rtl-optimization/108681] [13 Regression] " pinskia at gcc dot gnu.org 2023-02-06 7:56 ` rguenth at gcc dot gnu.org 2023-02-06 10:04 ` jakub at gcc dot gnu.org 2023-02-06 10:18 ` jakub at gcc dot gnu.org 2023-02-06 10:49 ` jakub at gcc dot gnu.org 2023-02-06 14:18 ` rsandifo at gcc dot gnu.org 2023-02-13 21:14 ` cvs-commit at gcc dot gnu.org 2023-02-13 21:18 ` rsandifo at gcc dot gnu.org 2023-02-14 8:01 ` Martin.Jansa at gmail dot com 2023-02-22 8:53 ` rguenth at gcc dot gnu.org 2023-02-22 8:54 ` [Bug rtl-optimization/108681] [12 " rguenth at gcc dot gnu.org 2023-03-02 13:17 ` herrtimson at yahoo dot de 2023-03-02 13:20 ` rsandifo at gcc dot gnu.org 2023-04-03 8:58 ` cvs-commit at gcc dot gnu.org 2023-04-03 9:04 ` rsandifo 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-108681-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).