public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hayder.alkhalissi at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/56622] New: -fopenmp with -fplugin conflicts
Date: Thu, 14 Mar 2013 18:54:00 -0000	[thread overview]
Message-ID: <bug-56622-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56622

             Bug #: 56622
           Summary: -fopenmp with -fplugin conflicts
    Classification: Unclassified
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: plugins
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hayder.alkhalissi@googlemail.com


Dear all,

I am trying to extending the compiler gcc-4.5.0 by using plug-in. When I tried
using -fpluging with -fopenmp, I got this error as bellow:

*** WARNING *** there are active plugins, do not report this as a bug unless
you can reproduce it without enabling any plugins.
Event                            | Plugins
PLUGIN_PRE_GENERICIZE            | libplugin-pointer-types
PLUGIN_FINISH                    | libplugin-pointer-types
PLUGIN_ATTRIBUTES                | libplugin-pointer-types
pointer-types-target.c: In function ‘main’:
pointer-types-target.c:46:2: internal compiler error: in
join_on_bb_function_call, at aop-pc-fun-call.c:246
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

BTY: I didn't have more experience in extending gcc.

I have already attached the *.i file as well.


             reply	other threads:[~2013-03-14 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 18:54 hayder.alkhalissi at googlemail dot com [this message]
2013-03-14 18:55 ` [Bug plugins/56622] " hayder.alkhalissi at googlemail dot com
2013-03-14 20:30 ` pinskia at gcc dot gnu.org
2013-03-15  8:35 ` hayder.alkhalissi at googlemail dot com
2013-03-15  8:57 ` rguenth at gcc dot gnu.org

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=bug-56622-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).