jpa

It appears that this change has been made in this commit: https://github.com/ntfreak/openocd/commit/80a5285ea6157706075e783fd6cb1ad09875d660 So maybe the ticket can be closed?

Thanks to Martin Storsjö / wbs on IRC for some hints: problem is probably in binutils, related to bugs like https://sourceware.org/bugzilla/show_bug.cgi?id=25374 workaround is to link against "foobar.dll" instead of "foobar.lib"

In my opinion this is a real and important bug. It makes it impossible to use many third-party libraries with mingw-w64-gcc 9.3. I have attached a minimal test case that tries to link against Ximea's xiapi32.dll. When compiled with i686-w64-mingw32-gcc (GCC) 7.3-win32 20180312, the import table is as follows and executable works fine: DLL Name: xiapi32.dll vma: Hint/Ord Member-Name Bound-To 64f4 368 xiStopAcquisition When compiled with i686-w64-mingw32-gcc (GCC) 9.3-win32 20200320, the import table...

Added patch here: https://sourceforge.net/p/gerbv/patches/75/

Fix bounding box calculation for slots

STM32L1xx USB is missing disconnect/connect macros

Wrong vector number for STM32L1xx USB

Wrong order in CH_STATE_NAMES