search for: omp_thread_limit

...tion. Could we create additional threads to perform packing transformation? If I’m not mistaken, BLIS framework applies multithreading in its implementation [5]. That’s why we would probably get more than 0.088919 seconds mentioned above, if the multithreading were disabled (I’ve been using export OMP_THREAD_LIMIT=1 to limit the number of OMP threads. However, I haven’t found a way to avoid usual multithreading). Refs. [1] - http://wiki.cs.utexas.edu/rvdg/HowToOptimizeGemm [2] - http://www.cs.utexas.edu/users/flame/pubs/TOMS-BLIS-Analytical.pdf [3] - https://github.com/flame/blis/tree/master/kernels/x86_64...

> 1. In a CHECK-DAG group, don't let the matches for patterns overlap. > 2. Add a new CHECK-DAG-N directive, where N is some integer, to express > that a pattern must have N non-overlapping matches. I think #1 is much more intuitive and easy to describe/document than #2. Changing the meaning of DAG in that way is highly unlikely to affect any existing test, IMO. And if it does, my

Hi, calling "omp_get_thread_limit", either inside or outside a parallel region, it returns MAX_INT (2147483647) when OMP_THREAD_LIMIT is not set. Is that the correct/default behavior for that function? Thanks. Simone ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized r...

Hi, Using FileCheck, I have not found a way to make a group of CHECK-DAG directives match multiple occurrences of a string. For example, I naively thought the following would match successfully: ``` $ cat checks.txt // CHECK: start // CHECK-DAG: foo // CHECK-DAG: foo // CHECK-DAG: bar // CHECK-NEXT: end $ cat input.txt start foo bar foo end $ FileCheck --input-file=input.txt checks.txt

...gin: parallel_id=[[PARALLEL_ID]], task_id=[[IMPLICIT_TASK_ID]] ``` The author was obviously expecting CHECK-DAG not to permit overlapping matches and wanted to check that the above lines appeared three times. Specifically, he's expecting 3 threads after the master thread, but the run line sets OMP_THREAD_LIMIT=2. If overlapping matches are permitted, this will permit any non-zero number of threads after the master thread. If overlapping matches are not permitted, we must increase OMP_THREAD_LIMIT to at least 4 or reduce the number of pattern repetitions. S4. CHECK-DAG unneeded ----------------------...