http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Feb 06, 2014 at 02:25:27AM +0000, thatcadguy at gmail dot com wrote:
>
> If you bothered to look at the gcc output file, you'd see that I tested it on
> Linux as well. This is a GCC and MinGW problem. The code segfaults on both
> platforms with both compilers.
>
What output file? gcc_flags.txt does not show a segfault
or a debugger backtrace.
I've now tested your code on x86_64-*-freebsd with 4.7,
4.8, and trunk. The code does not segfault. The code
runs fine under valgrind.
% valgrind ./z
==60969== Memcheck, a memory error detector
==60969== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==60969== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==60969== Command: ./z
==60969==
1 1.167898E+02
2 3.604828E+00
3 1.307785E-01
4 8.716767E-03
5 7.426061E-04
6 7.142144E-05
7 7.658771E-06
8 8.214756E-07
9 9.465642E-08
10 1.078958E-08
11 1.283740E-09
12 1.517027E-10
13 1.834825E-11
Max. Error: 4.480767E-13
Avg. Error: 1.225708E-14
Tot. Error: 1.961134E-11
==60969==
==60969== HEAP SUMMARY:
==60969== in use at exit: 0 bytes in 0 blocks
==60969== total heap usage: 31 allocs, 31 frees, 215,965 bytes allocated
==60969==
==60969== All heap blocks were freed -- no leaks are possible
==60969==
==60969== For counts of detected and suppressed errors, rerun with: -v
==60969== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
