From: "Dennis, CHENG Renquan" <crquan@fedoraproject.org>
To: Laurynas Biveinis <laurynas.biveinis@gmail.com>
Cc: Kai Ruottu <kai.ruottu@wippies.com>, gcc@gcc.gnu.org
Subject: Re: on how to compile gcc-4.6 correctly?
Date: Mon, 13 Sep 2010 20:31:00 -0000 [thread overview]
Message-ID: <AANLkTikVggakG47a1BNvZkgZ=Ao5wEOLLpSWBfQRJXZq@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin2KHrLzahi1eM=jQ6eGkZetTP_v_yPUZPySPTA@mail.gmail.com>
On Mon, Sep 13, 2010 at 8:16 PM, Laurynas Biveinis
<laurynas.biveinis@gmail.com> wrote:
> I am the author of how these macros are generated, but somehow I have
> missed this thread initially. Could you send me off-list that
> gtype-desc.h file?
The problematic gtype-desc.h has been sent to Laurynas separately, I
was compiling only the gcc-core-4.6-20100911.tar.bz2 tarball, because
I only want a c compiler; I searched the macro
ggc_alloc_cleared_lang_type through out the source and build
directory, only one definition and two usage, with conflict arguments
passing:
../path/to/gcc-build$ grep -RsInw ggc_alloc_cleared_lang_type
../gcc-4.6-20100911/ gcc/
../gcc-4.6-20100911/gcc/c-decl.c:7027: space =
ggc_alloc_cleared_lang_type (sizeof (struct lang_type));
../gcc-4.6-20100911/gcc/c-decl.c:7310: lt =
ggc_alloc_cleared_lang_type (sizeof (struct lang_type));
gcc/gtype-desc.h:2451:#define ggc_alloc_cleared_lang_type() ((struct
lang_type *)(ggc_internal_cleared_alloc_stat (sizeof (struct
lang_type) MEM_STAT_INFO)))
and in fact, I'm interested why this Kai Ruottu got a
ggc_alloc_cleared_lang_type_u macro with 0 arguments in gtype-desc.h
while my gtype-desc.h doesn't have that macro? I'm not sure he could
get ggc_alloc_cleared_lang_type macro or not, so how can he succeed
his compilation;
On Mon, Sep 6, 2010 at 10:51 PM, Kai Ruottu <kai.ruottu@wippies.com> wrote:
> This seems to be defined in a header generated during the build
> into the $BUILD/gcc :
>
> [root@localhost gcc]# grep ggc_alloc_cleared_lang_type *.h
> gtype-desc.h:#define ggc_alloc_cleared_lang_type_u() ((union lang_type_u
> *)(ggc_internal_cleared_alloc_stat (sizeof (union lang_type_u)
> MEM_STAT_INFO)))
>
> Thanks,
> --
> Laurynas
>
--
Cheng, from Singapore
next prev parent reply other threads:[~2010-09-13 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 3:17 Dennis
2010-09-06 9:18 ` Justin P. Mattock
2010-09-06 9:54 ` Cheng Rk
2010-09-06 10:32 ` Justin Mattock
2010-09-06 14:52 ` Kai Ruottu
2010-09-13 14:19 ` Dennis, CHENG Renquan
2010-09-13 20:04 ` Kai Ruottu
2010-09-13 20:15 ` Laurynas Biveinis
2010-09-13 20:31 ` Dennis, CHENG Renquan [this message]
2010-09-13 21:37 ` Laurynas Biveinis
2010-09-13 21:42 ` Dennis, CHENG Renquan
2010-09-14 14:01 ` Dennis, CHENG Renquan
2010-09-14 14:23 ` Kai Ruottu
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='AANLkTikVggakG47a1BNvZkgZ=Ao5wEOLLpSWBfQRJXZq@mail.gmail.com' \
--to=crquan@fedoraproject.org \
--cc=gcc@gcc.gnu.org \
--cc=kai.ruottu@wippies.com \
--cc=laurynas.biveinis@gmail.com \
/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).