From: Richard Biener <richard.guenther@gmail.com>
To: avantikagupta <avantikagupta@cse.iitb.ac.in>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: dynamic plugin in c++
Date: Wed, 28 Aug 2013 11:40:00 -0000 [thread overview]
Message-ID: <CAFiYyc2iYC=Jmp34oZvOtsE4ABUrrg0bft-FksnvowFC5WQ8bw@mail.gmail.com> (raw)
In-Reply-To: <8f3d78b91ae68665ff1278e5973f868f@cse.iitb.ac.in>
On Wed, Aug 28, 2013 at 10:05 AM, avantikagupta
<avantikagupta@cse.iitb.ac.in> wrote:
>
>
> hi,
>
> i am writing a dynamic plugin,
>
>
> however, sometimes it run succesfully and sometimes it give following error:
>
> /home/avantika/Downloads/gcc/gccpackage/install/bin/g++ -o result -flto
> -fplugin=./plugin.so test1.o -O3 -fdump-ipa-all
> In function ‘main’:
> lto1: internal compiler error: in rebuild_frequencies, at predict.c:2396
you have to look at this place to see what the code expects and think about
how/why you would violate its assumptions.
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> lto-wrapper: /home/avantika/Downloads/gcc/gccpackage/install/bin/g++
> returned 1 exit status
> /usr/bin/ld: lto-wrapper failed
> collect2: error: ld returned 1 exit status
> make: *** [test] Error 1
>
>
> code : following are the name of files constraint.cpp, dataflow.cpp ,
> constraint.hpp, dataflow.hpp;
>
> the main file named pointo-callstring.c includes both the hpp files, and is
> defining some object and class map.
>
> i have attached the files.
next prev parent reply other threads:[~2013-08-28 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 11:06 avantikagupta
2013-08-28 11:40 ` Richard Biener [this message]
2013-08-28 12:12 ` Jakub Jelinek
2013-08-28 20:16 ` avantikagupta
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='CAFiYyc2iYC=Jmp34oZvOtsE4ABUrrg0bft-FksnvowFC5WQ8bw@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=avantikagupta@cse.iitb.ac.in \
--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).