[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-10-19 Thread sistek at seznam dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #10 from Jakub Sistek --- Hello, are there any news regarding this issue, please? Were you able to reproduce it? Best wishes, Jakub Sistek

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-08-08 Thread sistek at seznam dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #9 from Jakub Sistek --- Created attachment 41953 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41953=edit an enhanced version of the example producing an error Hi Jakub, sorry for my late response, I was on vacation :-)

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-08-01 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #8 from Jakub Jelinek --- I believe the check that triggers here is just wrong, if we have 2 different queuest, it is very well possible that they will have different tasks with the same priority as the next candidates. And the code

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-08-01 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #7 from Jakub Jelinek --- Slightly adjusted testcase - no headers, no VLAs, etc.: int main () { #define MT 4 int a[MT * MT]; for (int i = 0; i < MT * MT; i++) a[i] = 0; #pragma omp parallel #pragma omp master { for

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-08-01 Thread sistek at seznam dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #6 from Jakub Sistek --- Also, the problem seems to disappear if there is no priority prescribed on the nested task. However, as soon as I prescribe any priority to the child task, it seems to appear. Jakub :-)

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-08-01 Thread sistek at seznam dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #5 from Jakub Sistek --- Created attachment 41879 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41879=edit test case producing an error Hello Jakub, thanks for looking into it. I have been able to isolate our problem into

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-07-31 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #4 from Jakub Jelinek --- Before that is available, perhaps backtrace from the gomp_fatal call in the _LIBGOMP_CHECKING_ enabled build might be also useful.

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-07-31 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #3 from Jakub Jelinek --- I think we need a reproducer for this. Can you provide something?

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-07-28 Thread sistek at seznam dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #2 from Jakub Sistek --- 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 >

[Bug libgomp/81591] segmentation fault when using priorities of nested tasks

2017-07-28 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81591 --- Comment #1 from Richard Biener --- There's static void inline priority_queue_downgrade_task (enum priority_queue_type type, struct priority_queue *head, struct gomp_task *task) {