https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61615
--- Comment #1 from Jacob Abel ---
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.
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 choos
: 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261
--- Comment #5 from Jacob Abel ---
(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 modu
>
> PROGRAM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261
--- Comment #3 from Jacob Abel ---
Created attachment 32838
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32838&action=edit
gfortran -v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261
--- Comment #2 from Jacob Abel ---
Created attachment 32837
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32837&action=edit
valgrind output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261
--- Comment #1 from Jacob Abel ---
Created attachment 32836
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32836&action=edit
gdb output
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=32835&action=edit
Test source file
The attached code produces a segfault on
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #23 from Jacob Abel ---
If it helps at all, the following produces the same problem under gcc:
#include
#include
int main(void)
{
__float128 *ptr = NULL;
int i;
if (ptr = malloc(100 * sizeof(__float128)))
for (i
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #19 from Jacob Abel ---
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-ubuntu
Copyright (C) 2013 Free So
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #16 from Jacob Abel ---
Still segfaults, at least on MinGW:
C:\Users\Jake\Downloads>gfortran -march=native -Wl,-uquadmath_snprintf
newtest.f
90
C:\Users\Jake\Downloads>a
Program received signal SIGSEGV: Segmentation fault - invalid
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #13 from Jacob Abel ---
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 PROGRAM main
Creates the same
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #12 from Jacob Abel ---
Created attachment 32074
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32074&action=edit
NEW smaller simpler file to create the segfault
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #11 from Jacob Abel ---
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 laptop, so might be multiple is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #8 from Jacob Abel ---
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 and all you've done is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #6 from Jacob Abel ---
(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. Here's the gdb output:
jake@
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #3 from Jacob Abel ---
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.
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=32061&action=edit
zip file of the code, makefile, and gcc output
I
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #1 from Jacob Abel ---
Created attachment 32062
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32062&action=edit
gcc -v output and march=native flags
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48937
Jacob Abel changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
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:
21 matches
Mail list logo
