public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/94439] New: gcc: error: gcc/testsuite/gcc.dg/torture/builtin-complex-1.c: ‘-fcompare-debug’ failure since r10-3499-g0ce77f463d1d150e Date: Wed, 01 Apr 2020 12:35:35 +0000 [thread overview] Message-ID: <bug-94439-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94439 Bug ID: 94439 Summary: gcc: error: gcc/testsuite/gcc.dg/torture/builtin-complex-1.c: ‘-fcompare-debug’ failure since r10-3499-g0ce77f463d1d150e Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- The following causes -fdebug-compare: $ gcc /home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/torture/builtin-complex-1.c -fcompare-debug -flive-patching=inline-clone -O2 -funroll-loops -fno-tree-forwprop -fno-expensive-optimizations -mstack-arg-probe gcc: error: /home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/torture/builtin-complex-1.c: ‘-fcompare-debug’ failure
next reply other threads:[~2020-04-01 12:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-01 12:35 marxin at gcc dot gnu.org [this message] 2020-04-01 12:36 ` [Bug debug/94439] [10 Regression] " marxin at gcc dot gnu.org 2020-04-01 12:57 ` jakub at gcc dot gnu.org 2020-04-01 13:17 ` jakub at gcc dot gnu.org 2020-04-02 11:16 ` jakub at gcc dot gnu.org 2020-04-17 18:11 ` law at redhat dot com 2020-04-17 19:16 ` law at redhat dot com 2020-04-17 19:21 ` law at redhat dot com 2020-04-18 15:40 ` cvs-commit at gcc dot gnu.org 2020-04-18 15:41 ` law at redhat dot com
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-94439-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).