[Bug fortran/28154] SPREAD (and friends) on unallocated arrays

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28154 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC||quantheory

[Bug fortran/56789] Wrong code with contiguous dummy argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC||quantheory

[Bug fortran/56789] Wrong code with contiguous dummy argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #4 from Sean Santos quantheory at gmail dot com --- Oops, I mean a free() error as in comment 0, not a segfault.

[Bug fortran/60928] gfortran issue with allocatable components and OpenMP

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60928 --- Comment #5 from Sean Santos quantheory at gmail dot com --- Well, I thought I understood this, but maybe not. I was thinking that subobject in this context meant component. A list item here is just any variable or common block listed

[Bug fortran/60928] gfortran issue with allocatable components and OpenMP

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60928 --- Comment #7 from Sean Santos quantheory at gmail dot com --- Ah, right. Thinking about it again today, my comment 5 is very confused for several reasons, and I don't agree with it anymore. My original interpretation is the only one that makes

[Bug fortran/60928] gfortran issue with allocatable components and OpenMP

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60928 --- Comment #3 from Sean Santos quantheory at gmail dot com --- OpenMP 4.0 is strange. Sure, it does refer to allocatable enhancement as an unsupported feature, which is vague. It might refer to the TR unofficially known as the Allocatable

[Bug fortran/60928] New: gfortran issue with allocatable components and OpenMP

Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: quantheory at gmail dot com Just as a disclaimer up front, this is probably an OpenMP 4.0 issue. OpenMP 3.1 sort of glossed over this use case, but OpenMP 4.0 quietly added language about it. Still, it would be nice

[Bug fortran/60795] [4.7/4.8/4.9 Regression] Wrong length when allocating character array

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60795 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC||quantheory

[Bug fortran/40196] F2003: Type parameter inquiry (str%len, a%kind) and Complex parts (z%re, z%im)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40196 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC||quantheory

[Bug fortran/40054] [F08] Pointer functions as lvalue

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40054 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC||quantheory

[Bug fortran/58204] [F2008] BOZ literals in the int function should not be treated as unsigned integers

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58204 Sean Santos quantheory at gmail dot com changed: What|Removed |Added Summary|Spurious error when using |[F2008] BOZ

[Bug fortran/58204] New: Spurious error when using BOZ literal to set an integer

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: quantheory at gmail dot com On a x86_64 system, I find that the following program produces two different compile-time errors: integer, parameter :: i128 = selected_int_kind(26) integer(i128

[Bug fortran/44672] [F2008] ALLOCATE with SOURCE and no array-spec

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44672 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC||quantheory

[Bug fortran/45440] [F03] ALLOCATE with SOURCE gives an ICE (segfault)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45440 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC||quantheory

[Bug fortran/45424] F2008: Add is_contiguous intrinsic

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45424 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC

[Bug fortran/29383] Fortran 2003/F95[TR15580:1999]: Floating point exception (IEEE) support

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29383 --- Comment #11 from Sean Santos quantheory at gmail dot com 2013-04-14 20:08:59 UTC --- I'm doing a bit of research because I'm considering trying to tackle part of this soon. I believe that the Fortran standard does not require

[Bug fortran/48979] FRACTION und EXPONENT return invalid results for infinity/NaN

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48979 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC

[Bug fortran/29383] Fortran 2003/F95[TR15580:1999]: Floating point exception (IEEE) support

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29383 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC

[Bug fortran/55069] TRIM incorrectly optimized out for assignment to allocatable strings (deferred length)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55069 --- Comment #3 from Sean Santos quantheory at gmail dot com 2012-10-25 17:49:44 UTC --- Ah, it seems I was quite tired yesterday and made a couple mistakes: - I mixed up a test using an older gfortran version with a test

[Bug fortran/52843] Unexpected rejection of pure recursive function

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52843 Sean Santos quantheory at gmail dot com changed: What|Removed |Added CC

[Bug fortran/55069] New: [4.7/4.8 Regression] TRIM incorrectly optimized out for assignment to allocatable string

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55069 Bug #: 55069 Summary: [4.7/4.8 Regression] TRIM incorrectly optimized out for assignment to allocatable string Classification: Unclassified Product: gcc Version: 4.7.3

[Bug fortran/54917] New: transfer on polymorphic variable causes ICE (gfc_target_expr_size)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54917 Bug #: 54917 Summary: transfer on polymorphic variable causes ICE (gfc_target_expr_size) Classification: Unclassified Product: gcc Version: 4.7.3 Status: