vault backup: 2023-10-18 12:29:55

This commit is contained in:
Alice 2023-10-18 12:29:55 +01:00
parent 537b549a21
commit a51ee5af5a
3 changed files with 6 additions and 2 deletions

View file

@ -185,6 +185,7 @@
}, },
"active": "cca189cd61cd7fe5", "active": "cca189cd61cd7fe5",
"lastOpenFiles": [ "lastOpenFiles": [
"Pasted image 20231018122801.png",
"My Digital Garden.md", "My Digital Garden.md",
"4a1s/CP/PL - Aula 6.md", "4a1s/CP/PL - Aula 6.md",
"Images/Pasted image 20231018121319.png", "Images/Pasted image 20231018121319.png",
@ -221,7 +222,6 @@
"Excalidraw/Drawing 2023-10-04 09.18.24.excalidraw.md", "Excalidraw/Drawing 2023-10-04 09.18.24.excalidraw.md",
"Excalidraw/Drawing 2023-10-04 09.18.23.excalidraw.md", "Excalidraw/Drawing 2023-10-04 09.18.23.excalidraw.md",
"4a1s/MFES/PL - Aula 2.md", "4a1s/MFES/PL - Aula 2.md",
"4a1s/MFES/PL - Aula 1.md",
"4a1s/ESR", "4a1s/ESR",
"Private-Project", "Private-Project",
"4a1s/Excalidraw/RAS", "4a1s/Excalidraw/RAS",

View file

@ -55,9 +55,13 @@ There is a restriction on the thread access to the printing - each thread is for
**** ****
### Ex 3 ### Ex 3
### 3.1 + 3.2 ### 3.1
![[Pasted image 20231018121319.png]] ![[Pasted image 20231018121319.png]]
The output is always the same, since the instruction ''''\#pragma omp barrier'''' creates a barrier after one single thread execution (series of fork joins between the 2 threads). The output is always the same, since the instruction ''''\#pragma omp barrier'''' creates a barrier after one single thread execution (series of fork joins between the 2 threads).
### 3.2
![[Pasted image 20231018122801.png]]
O resultado é semelhante ao \#pragma omp ordered

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB