[Bug fortran/61615] Failure to resolve correct generic with TYPE(C_PTR) arguments

2014-06-27 Thread thatcadguy at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61615 --- Comment #1 from Jacob Abel thatcadguy at gmail dot com --- I was also told the following incorrect behavior is present from 4.8.1 and on. I've tested with 4.8.1 and 4.8.2 and received the same behavior.

[Bug fortran/61615] New: Failure to resolve correct generic with TYPE(C_PTR) arguments

2014-06-25 Thread thatcadguy at gmail dot com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: thatcadguy at gmail dot com The following program does not produce the expected output (the line 'CALL bar(a, b)' does not choose the subroutine bar_s as it should, it chooses bar_a1d

[Bug fortran/61429] New: SYSTEM_CLOCK used with non-default integer kind does not produce warning

2014-06-06 Thread thatcadguy at gmail dot com
: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: thatcadguy at gmail dot com Compiling: program main implicit none integer(kind=8) :: i call system_clock(i) end program main with gfortran -std=f95 -pedantic -Wall -Wextra

[Bug fortran/61261] [OOP] Segfault on source-allocating polymorphic variables

2014-05-21 Thread thatcadguy at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261 --- Comment #5 from Jacob Abel thatcadguy at gmail dot com --- (In reply to Dominique d'Humieres from comment #4) Slightly reduced test MODULE modu IMPLICIT NONE TYPE element CLASS(*), ALLOCATABLE :: e END TYPE element END MODULE

[Bug fortran/61261] New: [OOP] Segfault on source-allocating polymorphic variables

2014-05-20 Thread thatcadguy at gmail dot com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: thatcadguy at gmail dot com Created attachment 32835 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=32835action=edit Test source file The attached code produces a segfault on Ubuntu

[Bug fortran/61261] [OOP] Segfault on source-allocating polymorphic variables

2014-05-20 Thread thatcadguy at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261 --- Comment #1 from Jacob Abel thatcadguy at gmail dot com --- Created attachment 32836 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=32836action=edit gdb output

[Bug fortran/61261] [OOP] Segfault on source-allocating polymorphic variables

2014-05-20 Thread thatcadguy at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261 --- Comment #2 from Jacob Abel thatcadguy at gmail dot com --- Created attachment 32837 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=32837action=edit valgrind output

[Bug fortran/61261] [OOP] Segfault on source-allocating polymorphic variables

2014-05-20 Thread thatcadguy at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261 --- Comment #3 from Jacob Abel thatcadguy at gmail dot com --- Created attachment 32838 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=32838action=edit gfortran -v

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-07 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #23 from Jacob Abel thatcadguy at gmail dot com --- If it helps at all, the following produces the same problem under gcc: #include quadmath.h #include stdlib.h int main(void) { __float128 *ptr = NULL; int i; if (ptr

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #11 from Jacob Abel thatcadguy at gmail dot com --- The culprit that -march=native activates on my Core i7 laptop is -mavx. Compiling with -mavx causes the segfault, without is fine. Unfortunately, that flag was not set on my other

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #12 from Jacob Abel thatcadguy at gmail dot com --- Created attachment 32074 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32074action=edit NEW smaller simpler file to create the segfault

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #13 from Jacob Abel thatcadguy at gmail dot com --- The following file: SUBROUTINE test(N) IMPLICIT NONE INTEGER, INTENT(IN) :: N REAL(KIND=16) :: array(N) array = 0 END SUBROUTINE test PROGRAM main IMPLICIT NONE CALL test(10) END

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #16 from Jacob Abel thatcadguy at gmail dot com --- Still segfaults, at least on MinGW: C:\Users\Jake\Downloadsgfortran -march=native -Wl,-uquadmath_snprintf newtest.f 90 C:\Users\Jake\Downloadsa Program received signal SIGSEGV

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #19 from Jacob Abel thatcadguy at gmail dot com --- jake@Jake-E1505:~/Desktop$ gfortran -static -march=native -Wl,-uquadmath_snprintf newtest.f90 -o newtest jake@Jake-E1505:~/Desktop$ gdb newtest GNU gdb (GDB) 7.5.91.20130417-cvs

[Bug fortran/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-05 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #1 from Jacob Abel thatcadguy at gmail dot com --- Created attachment 32062 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32062action=edit gcc -v output and march=native flags

[Bug fortran/60088] New: Segfault when using quad precision and -march=native on gfortran

2014-02-05 Thread thatcadguy at gmail dot com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: thatcadguy at gmail dot com Created attachment 32061 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32061action=edit zip file of the code, makefile, and gcc output I went to test

[Bug target/60088] [MingW] Segfault when using quad precision and -march=native on gfortran

2014-02-05 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #3 from Jacob Abel thatcadguy at gmail dot com --- 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.

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-05 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #6 from Jacob Abel thatcadguy at gmail dot com --- (In reply to Steve Kargl from comment #5) What output file? gcc_flags.txt does not show a segfault or a debugger backtrace. It shows that I was not using MinGW, as you assumed

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

2014-02-05 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #8 from Jacob Abel thatcadguy at gmail dot com --- Seriously? Look, you falsely assumed it was mingw only. Jerry reproduced the problem on linux as well. Excuse me for not knowing to post the backtrace. I come here to post a legitimate

[Bug fortran/48937] New: Discrepancy in computation between 32 and 64-bit builds

2011-05-09 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48937 Summary: Discrepancy in computation between 32 and 64-bit builds Product: gcc Version: 4.5.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/48937] Discrepancy in computation between 32 and 64-bit builds

2011-05-09 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48937 Jacob Abel thatcadguy at gmail dot com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED