[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2021-01-22 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #11 from anlauf at gcc dot gnu.org --- (In reply to Bill Long from comment #10) > Still fails with 10.2.0. Can you say which release version will include the > fix? According to https://gcc.gnu.org/, gcc 10.2 was released in July

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2021-01-22 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #10 from Bill Long --- Still fails with 10.2.0. Can you say which release version will include the fix?

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-08 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 anlauf at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-08 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #8 from CVS Commits --- The releases/gcc-9 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:83967508034454425dfce7fe0ea33a153c34e7cb commit r9-8985-g83967508034454425dfce7fe0ea33a153c34e7cb Author: Harald Anlauf

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-08 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #7 from CVS Commits --- The releases/gcc-10 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:d4ec0a15afb7538247206aa9936071544fd860f8 commit r10-8870-gd4ec0a15afb7538247206aa9936071544fd860f8 Author: Harald Anlauf

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-05 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #6 from anlauf at gcc dot gnu.org --- (In reply to Bill Long from comment #5) > The original intent of adding the KIND argument was because some > implementations used a 32-bit integer for the result, and it is possible for > the

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-04 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #5 from Bill Long --- The original intent of adding the KIND argument was because some implementations used a 32-bit integer for the result, and it is possible for the answer to be larger than 2**31-1. Just checking to be sure that

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-04 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #4 from CVS Commits --- The master branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:35d2c6b6e8a7448a84abbf967feeb78a29117014 commit r11-3646-g35d2c6b6e8a7448a84abbf967feeb78a29117014 Author: Harald Anlauf Date:

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-02 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 anlauf at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-02 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #2 from anlauf at gcc dot gnu.org --- Untested fix: diff --git a/gcc/fortran/trans-intrinsic.c b/gcc/fortran/trans-intrinsic.c index 3b3bd8629cd..9e9898c2bbf 100644 --- a/gcc/fortran/trans-intrinsic.c +++

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-02 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|