public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/111409] Invalid .debug_macro.dwo macro information for split DWARF
Date: Tue, 28 Nov 2023 12:58:50 +0000 [thread overview]
Message-ID: <bug-111409-4-otD3yPHxJP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111409-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111409
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ro at gcc dot gnu.org
--- Comment #3 from Rainer Orth <ro at gcc dot gnu.org> ---
The new test FAILs on a couple of targets (sparc-sun-solaris2.11,
powerpc-ibm-aix7.2.5.0, hppa64-hp-hpux11.11). I've commited a patch for the
Solaris/SPARC (and probably AIX) issue:
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638456.html
HP/UX seems to be different, however.
Besides, is there a reason this PR is still open?
next prev parent reply other threads:[~2023-11-28 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 21:29 [Bug debug/111409] New: " osandov at osandov dot com
2023-09-14 6:51 ` [Bug debug/111409] " osandov at osandov dot com
2023-09-20 6:03 ` cvs-commit at gcc dot gnu.org
2023-11-28 12:58 ` ro at gcc dot gnu.org [this message]
2024-02-27 0:57 ` osandov at osandov dot com
2024-05-21 15:04 ` vries at gcc dot gnu.org
2024-05-21 15:05 ` vries 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-111409-4-otD3yPHxJP@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).