From: Robert Stevenson <robert_steve82@yahoo.com>
To: gcc@gnu.org
Subject: Re: Using add_stmt in gimplify.c
Date: Thu, 16 Dec 2010 16:58:00 -0000 [thread overview]
Message-ID: <530353.581.qm@web121702.mail.ne1.yahoo.com> (raw)
In-Reply-To: <mcrsjxyxsbj.fsf@google.com>
Is there any change I should do to the Makefile.in or any other files? Is there
any specific header files I should add ? (I have c-family/c-common.h).
Regards,
Bobby
----- Original Message ----
From: Ian Lance Taylor <iant@google.com>
To: Robert Stevenson <robert_steve82@yahoo.com>
Cc: gcc@gnu.org
Sent: Wed, December 15, 2010 11:19:44 PM
Subject: Re: Using add_stmt in gimplify.c
Robert Stevenson <robert_steve82@yahoo.com> writes:
> I am trying to add some information/instructions into loop statements in
> GCC front-end. For this, in the previous gcc, I have used "add_stmt" to insert
> these instructions and they worked fine. When I do it in gcc 4.6 (snapshot
> 2010/12/4) I get "undefined references to "add_stmt."
>
> One thing I found different in this 4.6 version of gcc is that the files
> prefixed with "c-" have been stored in the c-family director. Is this the
>reason
>
> why I am not able to use add_stmt in the gimplify.c function? What can I do to
> use "add_stmt" function?
add_stmt is still there in the C and C++ frontends; I don't know why it
doesn't work for you. But you shouldn't really call it from gimplify.c
anyhow, as add_stmt adds statements to the wrong place. In gimplify.c
you should use functions like gimplify_seq_add_stmt. There are many
examples in that file.
Ian
next prev parent reply other threads:[~2010-12-16 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 1:27 Robert Stevenson
2010-12-16 4:20 ` Ian Lance Taylor
2010-12-16 16:58 ` Robert Stevenson [this message]
2010-12-17 1:24 ` Ian Lance Taylor
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=530353.581.qm@web121702.mail.ne1.yahoo.com \
--to=robert_steve82@yahoo.com \
--cc=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).