Something like this?
#include
#include
int main(void)
{
/* Compute 1.0/3.0 in default FPU mode */
volatile float somefloat = 1.0;
somefloat /= 3.0;
/* Output it in float and hex formats */
printf("%.9g\thex: %x\n", somefloat, *(int *)&somefloat);
fenv_t a, b;
fege
在 2019/2/25 22:41, Liu Hao 写道:
> 在 2019/2/25 19:27, Zidane Sama 写道:
>> After this commit:
>>
>> [e98d80] (2.0 kB) by Kai Tietz
>> Add a fix for working fesetenv in libquadmath-library
>>
>> fesetenv was broken and do not sets new fpu state because it's now
>> overwrites new env state by fnstenv.
>
在 2019/3/7 17:45, Jacek Caban 写道:
> Note that when doing 32-bit builds, _USE_32BIT_TIME_T will be most
> likely defined so this code path will not be used. Currently (although
> it might be improved in the future), one has to define
> __MINGW_USE_VC2005_COMPAT to use 64-bit time_t, and it's the onl
On 07/03/2019 03:22, Liu Hao wrote:
在 2019/3/7 上午5:11, Martin Storsjö 写道:
On Wed, 6 Mar 2019, Jacek Caban wrote:
It exists in msvcrt.dll that I checked (I think it's from win10). The
patch looks good to me.
_mkgmtime64 appeared in msvcrt.dll in Vista, it's missing in XP.
// Martin
I think
On Thu, Mar 7, 2019 at 10:30 AM Matthias Apitz wrote:
>
> Re/ crosscompiling: I'm used to do so on FreeBSD amd64 for x86 target,
> but never compiled something on FreeBSD/Linux for Windows.
use the mingw-w64 toolchain (sould be available in your freebsd distribution)
i686-w64-mingw32-gcc, etc...
El día Thursday, March 07, 2019 a las 09:36:28AM +0100, Vincent Torri escribió:
> > Below is the (very short) list of missing pieces which I can't see on my
> > Windows file system.
> >
> > Any ideas?
> > - -
> >
Personally I use
PATH="/usr/x86_64-w64-mingw32/sys-root/mingw/bin:$PATH" ldd DEADBEEF.exe
which is not exactly what you would like but still better than simply
launching ldd.
чт, 7 мар. 2019 г. в 11:27, Matthias Apitz :
> El día Wednesday, March 06, 2019 a las 11:20:05AM -0800, David Grayson
> e
On 07.03.2019 11:26, Matthias Apitz wrote:
> El día Wednesday, March 06, 2019 a las 11:20:05AM -0800, David Grayson
> escribió:
>
>> Your experience matches mine: the Cygwin ldd utility does not work properly
>> with MinGW DLLs and prints a bunch of question marks. There is an ntldd
>> utility y
On Thu, Mar 7, 2019 at 9:27 AM Matthias Apitz wrote:
>
> El día Wednesday, March 06, 2019 a las 11:20:05AM -0800, David Grayson
> escribió:
>
> > Your experience matches mine: the Cygwin ldd utility does not work properly
> > with MinGW DLLs and prints a bunch of question marks. There is an ntld
El día Wednesday, March 06, 2019 a las 11:20:05AM -0800, David Grayson escribió:
> Your experience matches mine: the Cygwin ldd utility does not work properly
> with MinGW DLLs and prints a bunch of question marks. There is an ntldd
> utility you can use instead. If it's not on your path already
10 matches
Mail list logo
