public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eebssk1 at godaftwithebk dot pub" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/108389] LTO(plugin) can not find lto-ed symbols
Date: Sat, 18 Feb 2023 18:16:34 +0000	[thread overview]
Message-ID: <bug-108389-4-lKKdw3wiqX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108389-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from BBK <eebssk1 at godaftwithebk dot pub> ---
It truly looks like a plugin problem.
See the output

eebssk1@dEBianKb:~/a$ ~/mingw-gcc/i686-w64-mingw32/bin/i686-w64-mingw32-gcc-nm
*strnlen*
00000000 T _strnlen
eebssk1@dEBianKb:~/a$ ~/mingw-gcc/i686-w64-mingw32/bin/i686-w64-mingw32-nm
*strnlen*
00000000 b .bss
00000000 d .data
00000000 N .debug_abbrev
00000000 N .debug_aranges
00000000 N .debug_info
00000000 N .debug_line
00000000 N .debug_line_str
00000000 r .eh_frame
00000000 r .gnu.lto_.decls.65045144
00000000 r .gnu.lto_.ext_symtab.65045144
00000000 r .gnu.lto_.icf.65045144
00000000 r .gnu.lto_.inline.65045144
00000000 r .gnu.lto_.ipa_modref.65045144
00000000 r .gnu.lto_.ipa_sra.65045144
00000000 r .gnu.lto_.jmpfuncs.65045144
00000000 r .gnu.lto_.lto.65045144
00000000 r .gnu.lto_.opts
00000000 r .gnu.lto_.profile.65045144
00000000 r .gnu.lto_.pureconst.65045144
00000000 r .gnu.lto_.refs.65045144
00000000 r .gnu.lto_strnlen.4.65045144
00000000 r .gnu.lto_.symbol_nodes.65045144
00000000 r .gnu.lto_.symtab.65045144
00000000 r .rdata$zzz
00000000 T _strnlen
00000000 t .text

  parent reply	other threads:[~2023-02-18 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 19:00 [Bug lto/108389] New: " eebssk1 at godaftwithebk dot pub
2023-01-12 19:04 ` [Bug lto/108389] " eebssk1 at godaftwithebk dot pub
2023-02-18 18:16 ` eebssk1 at godaftwithebk dot pub [this message]
2023-02-18 18:23 ` eebssk1 at godaftwithebk dot pub
2023-02-18 19:12 ` eebssk1 at godaftwithebk dot pub

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-108389-4-lKKdw3wiqX@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).