From: Alexander Monakov <amonakov@ispras.ru>
To: Josef Wolf <jw@raven.inka.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Linker won't bail out on non-existing functions?
Date: Fri, 4 Sep 2020 14:45:04 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.20.13.2009041443000.18674@monopod.intra.ispras.ru> (raw)
In-Reply-To: <20200904101835.GB4037@raven.inka.de>
On Fri, 4 Sep 2020, Josef Wolf wrote:
> So why won't the linker bail out when it can't resolve a reference?
> Any hints?
You're linking with --gc-sections, and if all references to undefined functions
are in discarded sections, the linker won't complain. In other words, checking
for remaining undefined references happens after discarding unneeded sections.
Alexander
next prev parent reply other threads:[~2020-09-04 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 10:18 Josef Wolf
2020-09-04 11:45 ` Alexander Monakov [this message]
2020-09-04 12:56 ` Josef Wolf
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=alpine.LNX.2.20.13.2009041443000.18674@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=gcc-help@gcc.gnu.org \
--cc=jw@raven.inka.de \
/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).