public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/99618] `.gnu.debuglto_.debug_macro' referenced in section `.gnu.debuglto_.debug_macro' of X defined in discarded section
Date: Wed, 17 Mar 2021 13:41:37 +0000	[thread overview]
Message-ID: <bug-99618-4-WnmS8Ylsw1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99618-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #3)
> This is what GCC generates:
> 
> hjl@gnu-cfl-2 pr27590]$ cat bad.s
> 	.section	.gnu.debuglto_.debug_macro,"e",@progbits
> .Ldebug_macro0:
> 	.long	.Ldebug_macro2
> 	.section	.gnu.debuglto_.debug_macro,"eG",@progbits,wm4,comdat
> .Ldebug_macro2:
> 	.value	0x4
> [hjl@gnu-cfl-2 pr27590]$ gcc -c bad.s
> [hjl@gnu-cfl-2 pr27590]$ ld -r bad.o bad.o
> `.gnu.debuglto_.debug_macro' referenced in section
> `.gnu.debuglto_.debug_macro' of bad.o: defined in discarded section
> `.gnu.debuglto_.debug_macro[wm4]' of bad.o
> [hjl@gnu-cfl-2 pr27590]$

what's wrong with it?  All sections are marked as to be Excluded, that
the excluded sections reference each other should be irrelevant?  I suppose
that one s comdat confuses the linker?

  parent reply	other threads:[~2021-03-17 13:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 13:11 [Bug lto/99618] New: " marxin at gcc dot gnu.org
2021-03-16 13:23 ` [Bug lto/99618] " rguenth at gcc dot gnu.org
2021-03-16 13:26 ` marxin at gcc dot gnu.org
2021-03-17 13:33 ` hjl.tools at gmail dot com
2021-03-17 13:41 ` rguenth at gcc dot gnu.org [this message]
2021-03-17 13:44 ` rguenth at gcc dot gnu.org
2021-03-17 13:44 ` jakub at gcc dot gnu.org
2021-03-17 13:49 ` hjl.tools at gmail dot com
2021-03-17 13:51 ` [Bug debug/99618] " hjl.tools at gmail dot com
2021-03-17 13:54 ` hjl.tools at gmail dot com
2021-03-17 13:56 ` rguenth at gcc dot gnu.org
2021-03-17 13:59 ` jakub at gcc dot gnu.org
2021-03-17 14:08 ` rguenth at gcc dot gnu.org
2021-03-17 14:10 ` rguenth at gcc dot gnu.org
2021-03-17 14:12 ` jakub at gcc dot gnu.org
2021-03-17 14:12 ` rguenth at gcc dot gnu.org
2021-03-17 14:29 ` hjl.tools at gmail dot com
2021-03-17 14:32 ` jakub at gcc dot gnu.org
2021-03-17 15:54 ` jakub at gcc dot gnu.org
2021-03-17 18:09 ` marxin at gcc dot gnu.org
2021-03-17 22:45 ` hjl.tools at gmail 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-99618-4-WnmS8Ylsw1@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).