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] -fopenmp with -fplugin conflicts
Date: Fri, 15 Mar 2013 08:35:00 -0000	[thread overview]
Message-ID: <bug-56622-4-0QXUyZKXR1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56622-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #3 from hayder.alkhalissi at googlemail dot com 2013-03-15 08:35:29 UTC ---
(In reply to comment #2)
> >join_on_bb_function_call, at aop-pc-fun-call.c:246
> 
> This is a bug in your plugin code and not in GCC.  Please report it to the
> place where you got the plugin.

Thanks for fast response.
I found the code in aop_pc_fun_call.c:

gimple stmt = gsi_stmt (gsi)  /* gimple_stmt_iterator gsi; */

/* At this stage, there should be no GIMPLE statements with sub-statements. */
gcc-assert(!gimple_has_substatements (stmt));       <------line 246

As explained above, the error in using  gcc-assert().

Do you know why? and how could avoided?

Thanks


  parent reply	other threads:[~2013-03-15  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 18:54 [Bug plugins/56622] New: " hayder.alkhalissi at googlemail dot com
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 [this message]
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-0QXUyZKXR1@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).