This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgomp/81591] segmentation fault when using priorities of nested tasks
- From: "sistek at seznam dot cz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 28 Jul 2017 09:18:59 +0000
- Subject: [Bug libgomp/81591] segmentation fault when using priorities of nested tasks
- Auto-submitted: auto-generated
- References: <bug-81591-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591
--- Comment #2 from Jakub Sistek <sistek at seznam dot cz> ---
With the _LIBGOMP_CHECKING_ enabled, I am getting
libgomp: priority_tree_next_task: t1 != t2
Best wishes,
Jakub Sistek
(In reply to Richard Biener from comment #1)
> There's
>
> static void inline
> priority_queue_downgrade_task (enum priority_queue_type type,
> struct priority_queue *head,
> struct gomp_task *task)
> {
> #if _LIBGOMP_CHECKING_
> if (!priority_queue_task_in_queue_p (type, head, task))
> gomp_fatal ("Attempt to downgrade missing task %p", task);
> #endif
> if (priority_queue_multi_p (head))
> {
> struct priority_list *list
> = priority_queue_lookup_priority (head, task->priority);
> priority_list_downgrade_task (type, list, task);
>
> so maybe you can build libgomp with _LIBGOMP_CHECKING_ to help track this
> down?
> (just change libgomp/libgomp.h)