From: Etienne Buira <etienne.buira@free.fr>
To: gcc@gcc.gnu.org
Subject: convert_to_complex_1 vs convert
Date: Wed, 3 Jan 2024 14:00:28 +0100 [thread overview]
Message-ID: <ZZVabMG98rMYRdqj@Z926fQmE5jqhFMgp6> (raw)
Hi all,
I'm currently following tiny language front-end tutorial, and went
across a build error:
ld: convert.o: in function 'convert_to_complex_1(tree_node*, tree_node*, bool)':
convert.cc:1038: undefined reference to 'convert(tree_node*, tree_node*)'
Looking at the sources, it looks like this call was introduced in commit
13c0d052578b.
So i'm kind of stuck here, as i don't know wether:
- convert.cc should limit itself to functions it knows are implemented
in generic way.
- every frontend is mandated to export a convert(tree*, tree*) symbol.
Can someone help me here?
Regards
PS: I'm not subscribed to the list, so please CC me.
reply other threads:[~2024-01-03 13:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZZVabMG98rMYRdqj@Z926fQmE5jqhFMgp6 \
--to=etienne.buira@free.fr \
--cc=gcc@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).