My own benchmarks work fine (gcc/g++ also). In John Campbell's test,
among 5 run-time failures, there is (twice):
Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.
Backtrace for this error:
1 [main] profile_omp 5664 fixup_mmaps_after_fork:
ReadProcessMemory failed
for MAP_PRIVATE address 0x6FE5FC60000, Win32 error 998
357 [main] profile_omp 5664
C:\users\tim\tim\tim\src\campbell\Profile_send_3
Nov14\profile_omp.exe: *** fatal error in forked process -
recreate_mmaps_after_fork_failed
690131 [main] profile_omp 5664 cygwin_exception::open_stackdumpfile:
Dumping stack trace to profile_omp.exe.stackdump
3 [main] profile_omp 4644 fork: child -1 - forked process 5664
died unexpectedly, retry 0, exit code 0x100, errno 11
28628 [main] profile_omp 4644 cygwin_exception::open_stackdumpfile:
Dumping stack trace to profile_omp.exe.stackdump
In spite of the remaining failures, it looks like progress.
As I'm lazy, I'll continue using gcc-5.0 trunk builds unless there is
interest (suggestion what should be done) in this one. I guess this
4.9.2-1 is more aggressive with build options than I've been able to
make work.
--
Tim Prince
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
