From: William Tambe <tambewilliam@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: GCC generating symbols prefixed with "call_"
Date: Wed, 25 Mar 2020 21:41:09 -0400 [thread overview]
Message-ID: <CAF8i9mNbn6eErETpLr-Q_Lu4+w3chCEyzBa8Mp0zVetydR4VbA@mail.gmail.com> (raw)
Any idea what is causing GCC to generate the following symbols prefixed
with "call_" ?
call___do_global_ctors_aux
call___do_global_dtors_aux
call_frame_dummy
next reply other threads:[~2020-03-26 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 1:41 William Tambe [this message]
2020-03-26 23:02 ` Jim Wilson
2020-03-27 0:03 ` William Tambe
2020-03-30 17:43 ` Jim Wilson
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=CAF8i9mNbn6eErETpLr-Q_Lu4+w3chCEyzBa8Mp0zVetydR4VbA@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=gcc-help@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).