[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 Mikael Morin changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 --- Comment #10 from CVS Commits --- The releases/gcc-12 branch has been updated by Mikael Morin : https://gcc.gnu.org/g:d633e1cf67ad06c2fef6c33280b548f9c6ea9eba commit r12-8826-gd633e1cf67ad06c2fef6c33280b548f9c6ea9eba Author: Mikael Morin

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 --- Comment #9 from CVS Commits --- The releases/gcc-10 branch has been updated by Mikael Morin : https://gcc.gnu.org/g:b394ebd90e1f9c125216c70beedf97d6d8739773 commit r10-11029-gb394ebd90e1f9c125216c70beedf97d6d8739773 Author: Mikael Morin

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 --- Comment #8 from CVS Commits --- The releases/gcc-11 branch has been updated by Mikael Morin : https://gcc.gnu.org/g:fee1edea459ca655917f14605bdd38fe0e8f344e commit r11-10300-gfee1edea459ca655917f14605bdd38fe0e8f344e Author: Mikael Morin

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 --- Comment #7 from CVS Commits --- The master branch has been updated by Mikael Morin : https://gcc.gnu.org/g:29919bf3b6449bafd02e795abbb1966e3990c1fc commit r13-2835-g29919bf3b6449bafd02e795abbb1966e3990c1fc Author: Mikael Morin Date:

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 Mikael Morin changed: What|Removed |Added Last reconfirmed||2022-09-03 Ever confirmed|0

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 --- Comment #5 from anlauf at gcc dot gnu.org --- (In reply to Mikael Morin from comment #4) > With the testcase from comment #3, it becomes: > > a = {CLOBBER}; > D.4223 = a + 1; > copy (, ); Right. And with -Wall one gets a bogus

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 --- Comment #4 from Mikael Morin --- (In reply to anlauf from comment #2) > I see: > > D.4225 = a + 1; > a = {CLOBBER}; > copy (, ); > > so I do not see any failure. With the testcase from comment #3, it becomes: a =

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 --- Comment #3 from Mikael Morin --- (In reply to anlauf from comment #2) > > What am I missing? The right testcase. Try this one. module m implicit none contains subroutine copy(out, in) integer, intent(in) :: in integer,

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 anlauf at gcc dot gnu.org changed: What|Removed |Added CC||anlauf at gcc dot gnu.org

[Bug fortran/106817] clobber ordering problem when an actual intent(in) argument depends on the value of an intent(out) argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817 --- Comment #1 from Mikael Morin --- PR92178 is vaguely related. The tests are very similar, but that other PR is about allocatables whereas this one isn’t, so I think they are different.