public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/99490] -gdwarf-5 -gsplit-dwarf puts .debug_rnglists to main file, not .dwo file
Date: Tue, 09 Mar 2021 16:48:36 +0000	[thread overview]
Message-ID: <bug-99490-4-2lM4dJllnA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99490-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99490

--- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
Created attachment 50341
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50341&action=edit
range-gcc.s

  parent reply	other threads:[~2021-03-09 16:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 16:47 [Bug debug/99490] New: " jan.kratochvil at redhat dot com
2021-03-09 16:48 ` [Bug debug/99490] " jan.kratochvil at redhat dot com
2021-03-09 16:48 ` jan.kratochvil at redhat dot com [this message]
2021-03-09 19:31 ` marxin at gcc dot gnu.org
2021-03-09 20:10 ` jan.kratochvil at redhat dot com
2021-03-10  9:53 ` jakub at gcc dot gnu.org
2021-03-10 10:17 ` mark at gcc dot gnu.org
2021-03-10 11:35 ` jakub at gcc dot gnu.org
2021-03-10 11:43 ` jan.kratochvil at redhat dot com
2021-03-10 12:03 ` jakub at gcc dot gnu.org
2021-03-10 12:06 ` jakub at gcc dot gnu.org
2021-03-10 12:29 ` jan.kratochvil at redhat dot com
2021-03-10 22:10 ` jakub at gcc dot gnu.org
2021-03-10 22:17 ` jan.kratochvil at redhat dot com
2021-03-10 22:21 ` jakub at gcc dot gnu.org
2021-03-10 23:18 ` jan.kratochvil at redhat dot com
2021-03-11 12:20 ` jakub at gcc dot gnu.org
2021-03-11 12:46 ` jakub at gcc dot gnu.org
2021-03-12  9:00 ` jan.kratochvil at redhat dot com
2021-03-12  9:22 ` [Bug debug/99490] [11 Regression] " jakub at gcc dot gnu.org
2021-03-31 19:27 ` cvs-commit at gcc dot gnu.org
2021-03-31 19:39 ` 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-99490-4-2lM4dJllnA@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).