Custom Query (245 matches)
Results (25 - 27 of 245)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#300 | duplicate | Make spawnvpe support extension-less executables | ||
Description |
The current version of
Currently, this limitation may be worked around by creating a symlink to the program that has
|
|||
#298 | worksforme | path for cc1 and cc1plus is missing | ||
Description |
Hi/2. When setting gcc env up with gccenv.cmd, path for cc1 and cc1plus is missing. If you set path for emx, you could not relize this. Because gcc335 called cc1 of emx not its companion cc1. |
|||
#296 | wontfix | Add SIGFPE handler to all threads | ||
Description |
It is known that some OS/2 system DLLs and some third party DLLs unexpectedly reset the FPU control word to a value that causes FPU exceptions to be thrown by the CPU. This may happen to any application, no matter what compiler and runtime it uses. Even if the application doesn't load the "viral" DLL directly, it may be injected into the process by the system (i.e. via PM DLL hooks).
However, according to IEEE 754, the default action for FPU exceptions (e.g. divide by zero) in the compatible C runtime is to return a special value (e.g.
This often leads to a situation when the program does something like
Some applications work around this issue by manually calling
In fact, virtually any application needs this fix, for any of its threads (including threads created by third party library functions). Doing this over and over in each application is a pain. Functionally this definitely belongs to the C runtime. Normal programs (including third party libraries) are expected to start new threads using
So the FPU exception handler must be installed by LIBC both for
PS. GCC on Mac shows the correct behavior, no SIGFPE when I do things like |