public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96700] undefined reference to `failure_on_line_796' Date: Tue, 29 Sep 2020 17:43:56 +0000 [thread overview] Message-ID: <bug-96700-4-wDLicc7um4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96700-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96700 Jim Wilson <wilson at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Jim Wilson <wilson at gcc dot gnu.org> --- I took another look at this. I can get this to fail with an x86_64 gcc, but that is the system compiler which is gcc-7. A little testing shows that the testcase works for x86_64 gcc-8 and later and fails for gcc-7. However, since this is a testcase for gcc-11, there is no expectation that it should work with older gcc versions. We sometimes need to modify testcases to work when gcc changes. I also tried this with rv32-elf compilers, gcc-11, gcc-10, gcc-9, and I couldn't get the testcase to fail for any of them, with or without -flto. So I can't reproduce the original poster's problem, which gets me back to my original claim that I don't think that this is a gcc bug. Actually, on second thought, I realized that I'm using the original testcase from the gcc source tree gcc.dg/tree-ssa/buitlin-sprintf.c not the attachment. Looking at the attachment, I see that some numbers have been modified. So that is why it fails. It is a bogus testcase. Looking further, I see that you are using an old version of the testcase before it was changed in 2018. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86274 which both changed an optimization and changed the testcase to match the new optimization. The fix was put on mainlnie (gcc-9) and backported to gcc-8, so the testcase should fail for any gcc-8 or later. This is invalid. You can't take a testcase from gcc-X and expect it to work with gcc-Y.
prev parent reply other threads:[~2020-09-29 17:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-19 6:37 [Bug lto/96700] New: " sujian.liu at huawei dot com 2020-09-23 20:25 ` [Bug target/96700] " wilson at gcc dot gnu.org 2020-09-23 22:36 ` msebor at gcc dot gnu.org 2020-09-29 17:43 ` wilson at gcc dot gnu.org [this message]
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-96700-4-wDLicc7um4@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).