subject:"\[Bug fortran\/95647\] operator\(.eq.\) and operator\(==\) treated differently"

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-13 Thread jvdelisle at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-12 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #12 from CVS Commits --- The releases/gcc-10 branch has been updated by Jerry DeLisle : https://gcc.gnu.org/g:d5021162cf33081c128cd5c4f96ea0b7ca8739d7 commit r10-9365-gd5021162cf33081c128cd5c4f96ea0b7ca8739d7 Author: Steve Kargl Da

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-12 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #11 from CVS Commits --- The master branch has been updated by Jerry DeLisle : https://gcc.gnu.org/g:0631e008adc759cc801d0d034224ee6b4bcf31aa commit r11-7225-g0631e008adc759cc801d0d034224ee6b4bcf31aa Author: Steve Kargl Date: Fri

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-08 Thread jvdelisle at charter dot net via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #10 from Jerry DeLisle --- Oops, that what I get for doing 16 things at once. sorry.

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread kargl at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org --- C

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread jvdelisle at charter dot net via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #8 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #6) > (In reply to Bill Long from comment #5) > > Is this fixed in a release version of GCC? > > Submitting patch for approval and will backport as the fix is simple.

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread longb at cray dot com via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #7 from Bill Long --- For our purposes, 10 will be fine.

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread jvdelisle at charter dot net via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at charter dot net --- Comment

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-01-22 Thread longb at cray dot com via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #5 from Bill Long --- Is this fixed in a release version of GCC?

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2020-06-13 Thread sgk at troutmask dot apl.washington.edu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #4 from Steve Kargl --- On Sat, Jun 13, 2020 at 08:11:22AM +, tkoenig at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 > > --- Comment #3 from Thomas Koenig --- > If we treat .eq. and == differently

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2020-06-13 Thread tkoenig at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #3 from Thomas Koenig --- If we treat .eq. and == differently, that is an indication of a bug in the compiler itself.