From: Laurynas Biveinis <laurynas.biveinis@gmail.com>
To: Aravinda <aravindakidambi@gmail.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: undefined reference to `gt_pch_nx_tree_code'
Date: Sun, 01 Nov 2009 20:28:00 -0000 [thread overview]
Message-ID: <d1e3ff2b0911011227m4296c1afpa1bc77d1080b347f@mail.gmail.com> (raw)
In-Reply-To: <26eb53620910262044g15335b4etd75caa03bca635b5@mail.gmail.com>
Hi,
It's hard to tell. The normal definition of tree_code is enum in
tree.h and it is an atomic type with respect GCC garbage collection.
But the names like gt_gcc_mx_tree_code suggest that GCC internals try
to treat it as a struct or some other non atomic type. Any chance
that your source does not include tree.h and defines some tree_code
type of its own?
2009/10/27 Aravinda <aravindakidambi@gmail.com>:
> Hi,
>
> I am writing a new pass for gcc that uses the GTY markers,
> 1. I have included the source file in GTFILES_H in gcc/Makefile.in.
> 2. I have the gt-path.h mentioned in the compilation for source file
> 3. I have the #include "gt-path.h" at the very end of the code of source file.
>
> I see the gt-path.h is getting created in the build/gcc directory. But
> I am getting the below error. Is there something I am missing in the
> Makefile, I tried to look at a similar example of tree-mudflap.c that
> uses GTY markers, I do not see any difference in the steps I have
> followed. I havent done gcc dev before, so I'd really appreciate any
> help in this regard.
>
> main.o tree-browser.o libbackend.a ../libcpp/libcpp.a
> ../libdecnumber/libdecnumber.a ../libcpp/libcpp.a
> ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -lmpfr -lgmp
> -rdynamic -ldl
> libbackend.a(gtype-desc.o): In function `gt_ggc_m_P9tree_code4htab':
> /home/aravinda/svnbuild/gcc/gtype-desc.c:1968: undefined reference to
> `gt_ggc_mx_tree_code'
> libbackend.a(gtype-desc.o): In function `gt_pch_n_P9tree_code4htab':
> /home/aravinda/svnbuild/gcc/gtype-desc.c:4133: undefined reference to
> `gt_pch_nx_tree_code'
> collect2: ld returned 1 exit status
> make[3]: *** [cc1-dummy] Error 1
> Thanks,
> Aravinda
>
--
Laurynas
next prev parent reply other threads:[~2009-11-01 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26eb53620910262036l30235febh11fe83ba4353351a@mail.gmail.com>
2009-10-27 9:51 ` Aravinda
2009-11-01 20:28 ` Laurynas Biveinis [this message]
2009-11-01 22:37 ` Aravinda
2009-11-01 22:45 ` Laurynas Biveinis
2009-11-02 22:34 ` Aravinda
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=d1e3ff2b0911011227m4296c1afpa1bc77d1080b347f@mail.gmail.com \
--to=laurynas.biveinis@gmail.com \
--cc=aravindakidambi@gmail.com \
--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).