public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/105203] [11/12 Regression] '-fcompare-debug' failure w/ -O2 -ftracer -fPIC since r11-3078-g69ca5f3a988266da
Date: Thu, 21 Apr 2022 07:44:36 +0000 [thread overview]
Message-ID: <bug-105203-4-VoHzI1zbC0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105203-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105203
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:504b02c70abcc31e0e9b56e69f82f85b5261bca9
commit r12-8211-g504b02c70abcc31e0e9b56e69f82f85b5261bca9
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Apr 21 09:43:30 2022 +0200
emit-rtl: Fix -fcompare-debug bug with label references in debug insns
[PR105203]
When we compute LABEL_NUSES from scratch, mark_all_labels doesn't call
mark_jump_label on DEBUG_INSNs:
if (NONDEBUG_INSN_P (insn))
mark_jump_label (PATTERN (insn), insn, 0);
and so doesn't increment LABEL_NUSES from references in DEBUG_INSNs.
But, when we call emit_copy_of_insn_after e.g. when duplicating some
DEBUG_INSNs, we call it even on those, which then results in LABEL_NUSES
differences and -fcompare-debug failures.
The following patch makes sure we don't call it on DEBUG_INSNs.
2022-04-21 Jakub Jelinek <jakub@redhat.com>
PR debug/105203
* emit-rtl.cc (emit_copy_of_insn_after): Don't call mark_jump_label
on DEBUG_INSNs.
* gfortran.dg/g77/pr105203.f: New test.
next prev parent reply other threads:[~2022-04-21 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 9:59 [Bug debug/105203] New: '-fcompare-debug' failure w/ -O2 -ftracer -fPIC asolokha at gmx dot com
2022-04-08 12:04 ` [Bug debug/105203] [11/12 Regression] '-fcompare-debug' failure w/ -O2 -ftracer -fPIC since r11-3078-g69ca5f3a988266da marxin at gcc dot gnu.org
2022-04-08 15:25 ` segher at gcc dot gnu.org
2022-04-08 15:44 ` segher at gcc dot gnu.org
2022-04-08 16:05 ` asolokha at gmx dot com
2022-04-08 16:20 ` segher at gcc dot gnu.org
2022-04-11 7:46 ` [Bug rtl-optimization/105203] " marxin at gcc dot gnu.org
2022-04-20 8:36 ` [Bug debug/105203] " jakub at gcc dot gnu.org
2022-04-20 13:31 ` segher at gcc dot gnu.org
2022-04-21 7:44 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-21 7:47 ` [Bug debug/105203] [11 " jakub at gcc dot gnu.org
2022-04-21 7:51 ` rguenth at gcc dot gnu.org
2022-04-21 9:29 ` cvs-commit at gcc dot gnu.org
2022-04-21 9:30 ` 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-105203-4-VoHzI1zbC0@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: link
Be 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).