LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Question about Implicit Multithreading

Solved!
Go to solution

@Petru_Tarabuta wrote:


It would be useful if there was a white paper that explained in detail the algorithm or heuristics that LabVIEW uses to implement implicit multithreading. (sorry if one exists already)


I find this whitepaper to be pretty informative: https://bit.ly/labviewcompiler

 

I strongly recommend all LabVIEW programmers re-read this document at least once a year. In my opinion, even when LabVIEW handles so much of these things for you, knowing how things work under the hood can make you an even better LabVIEW programmer.

Message 21 of 30
(1,604 Views)

@Darren  escreveu:

@Petru_Tarabuta wrote:


It would be useful if there was a white paper that explained in detail the algorithm or heuristics that LabVIEW uses to implement implicit multithreading. (sorry if one exists already)


I find this whitepaper to be pretty informative: https://bit.ly/labviewcompiler

 

I strongly recommend all LabVIEW programmers re-read this document at least once a year. In my opinion, even when LabVIEW handles so much of these things for you, knowing how things work under the hood can make you an even better LabVIEW programmer.


Do you know if this is the state of the art for the LabVIEW Compiler?

 

I mean, has something changed since 2020 (last time the document was updated)?

0 Kudos
Message 22 of 30
(1,596 Views)

@felipefoz wrote:


Do you know if this is the state of the art for the LabVIEW Compiler?

I mean, has something changed since 2020 (last time the document was updated)?


I recently asked one of the compiler experts in LabVIEW R&D to review the document and he confirmed that, barring a few newer minor optimizations, this document reflects the current state of the LabVIEW compiler.

Message 23 of 30
(1,585 Views)

@Darren wrote:

LabVIEW R&D investigated this issue and determined that this was a bug introduced in LabVIEW 2019. I have filed Bug 2558611 on the issue. The suggested workaround, as y'all have already determined in this thread, is to use a 0 second Wait (ms) call in any For Loop, While Loop, or multi-frame sequence structure that exhibits the behavior.


As we know NI in the last years, the fix will come only for the last version of LabVIEW, right?

Lucian
CLA
0 Kudos
Message 24 of 30
(1,496 Views)

@LucianM wrote:

@Darren wrote:

LabVIEW R&D investigated this issue and determined that this was a bug introduced in LabVIEW 2019. I have filed Bug 2558611 on the issue. The suggested workaround, as y'all have already determined in this thread, is to use a 0 second Wait (ms) call in any For Loop, While Loop, or multi-frame sequence structure that exhibits the behavior.


As we know NI in the last years, the fix will come only for the last version of LabVIEW, right?


That's not something of the last years. NI never released arbitrary bug fixes for previous versions of LabVIEW, only the currently shipping one. They did a few times release a bug fix for a previous version when it was a security fix, but nothing else. There is a possibility that they did at some point release a fix for a previous release for a really big account, but those were never made public. A big account however means several 100 LabVIEW licenses at normal cost and heavy, reoccurring PXI or similar hardware sales.

 

30 years ago and before you could get actually bug fixes directly from a developer if you happened to know them. But that is a non-sustainable support model that was quickly abandoned and actively discouraged by management. But even that was normally for the latest version, usually a pre-release of the next coming version.

Rolf Kalbermatter
My Blog
0 Kudos
Message 25 of 30
(1,480 Views)

LabVIEW 2015 SP1, for example, has 13 (thirteen) patches and they were not all released before LV16 was out. I think the last one was released while LV18 was out. I might remember wrongly but I don't think so.

Lucian
CLA
0 Kudos
Message 26 of 30
(1,458 Views)

@LucianM wrote:

LabVIEW 2015 SP1, for example, has 13 (thirteen) patches and they were not all released before LV16 was out. I think the last one was released while LV18 was out. I might remember wrongly but I don't think so.


There does seem to be a LV15 patch released in 2018... (and a LV16 from 2019 etc.): LabVIEW Download - NI

 

I can't check if there where 13 patches, I never noticed more than 1 or 2 patches, but I never paid much attention to it.

0 Kudos
Message 27 of 30
(1,422 Views)

Does this bug also happen in Linux RT?

0 Kudos
Message 28 of 30
(1,335 Views)

I assume the Bug affects all LabVIEW execution targets, yes.

0 Kudos
Message 29 of 30
(1,328 Views)

For anyone watching this thread it appears the bug was fixed in LabVIEW 2023 Q3 Patch 2, see here: LabVIEW 2023 Q3 Bug Fixes - NI

Message 30 of 30
(598 Views)