public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug plugins/56622] New: -fopenmp with -fplugin conflicts
@ 2013-03-14 18:54 hayder.alkhalissi at googlemail dot com
2013-03-14 18:55 ` [Bug plugins/56622] " hayder.alkhalissi at googlemail dot com
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: hayder.alkhalissi at googlemail dot com @ 2013-03-14 18:54 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug plugins/56622] -fopenmp with -fplugin conflicts
2013-03-14 18:54 [Bug plugins/56622] New: -fopenmp with -fplugin conflicts hayder.alkhalissi at googlemail dot com
@ 2013-03-14 18:55 ` hayder.alkhalissi at googlemail dot com
2013-03-14 20:30 ` pinskia at gcc dot gnu.org
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: hayder.alkhalissi at googlemail dot com @ 2013-03-14 18:55 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56622
--- Comment #1 from hayder.alkhalissi at googlemail dot com 2013-03-14 18:55:13 UTC ---
Created attachment 29670
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29670
preprocessed file
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug plugins/56622] -fopenmp with -fplugin conflicts
2013-03-14 18:54 [Bug plugins/56622] New: -fopenmp with -fplugin conflicts 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
2013-03-15 8:57 ` rguenth at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu.org @ 2013-03-14 20:30 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56622
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-03-14 20:30:13 UTC ---
>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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug plugins/56622] -fopenmp with -fplugin conflicts
2013-03-14 18:54 [Bug plugins/56622] New: -fopenmp with -fplugin conflicts 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
2013-03-15 8:57 ` rguenth at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: hayder.alkhalissi at googlemail dot com @ 2013-03-15 8:35 UTC (permalink / raw)
To: gcc-bugs
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug plugins/56622] -fopenmp with -fplugin conflicts
2013-03-14 18:54 [Bug plugins/56622] New: -fopenmp with -fplugin conflicts hayder.alkhalissi at googlemail dot com
` (2 preceding siblings ...)
2013-03-15 8:35 ` hayder.alkhalissi at googlemail dot com
@ 2013-03-15 8:57 ` rguenth at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu.org @ 2013-03-15 8:57 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56622
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> 2013-03-15 08:57:18 UTC ---
openMP is lowered later than your plugin runs and there are still
sub-statements
around.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-03-15 8:57 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-14 18:54 [Bug plugins/56622] New: -fopenmp with -fplugin conflicts 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
2013-03-15 8:57 ` rguenth at gcc dot gnu.org
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).