public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103353] Indefinite recursion when compiling -mmma requiring testcase w/ -maltivec Date: Thu, 24 Feb 2022 04:32:36 +0000 [thread overview] Message-ID: <bug-103353-4-DIcE13uh9b@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103353-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103353 --- Comment #6 from Arseny Solokha <asolokha at gmx dot com> --- *** Bug 101323 has been marked as a duplicate of this bug. ***
next prev parent reply other threads:[~2022-02-24 4:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-22 2:09 [Bug target/103353] New: " asolokha at gmx dot com 2022-02-17 1:55 ` [Bug target/103353] " linkw at gcc dot gnu.org 2022-02-22 7:37 ` linkw at gcc dot gnu.org 2022-02-22 8:49 ` linkw at gcc dot gnu.org 2022-02-22 11:33 ` segher at gcc dot gnu.org 2022-02-23 2:38 ` linkw at gcc dot gnu.org 2022-02-24 4:32 ` asolokha at gmx dot com [this message] 2022-02-24 12:12 ` segher at gcc dot gnu.org 2022-08-16 5:50 ` cvs-commit at gcc dot gnu.org 2022-08-24 2:31 ` cvs-commit at gcc dot gnu.org 2022-08-24 2:32 ` cvs-commit at gcc dot gnu.org 2022-08-24 2:35 ` cvs-commit at gcc dot gnu.org 2022-08-24 2:49 ` linkw 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-103353-4-DIcE13uh9b@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).