This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch, fortran] PR33749 - Wrong evaluation of expressions in lhs of assignment statements

From: Paul Thomas <paulthomas2 at wanadoo dot fr>
To: Tobias Burnus <burnus at net-b dot de>
Cc: Paul Richard Thomas <paul dot richard dot thomas at gmail dot com>, "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>, gcc-patches List <gcc-patches at gcc dot gnu dot org>
Date: Sun, 21 Oct 2007 19:05:11 +0200
Subject: Re: [Patch, fortran] PR33749 - Wrong evaluation of expressions in lhs of assignment statements
References: <339c37f20710210241w73f07b56o8db51abb0702dfb4@mail.gmail.com> <471B489A.6040605@net-b.de>

Tobias Burnus wrote:

Paul Richard Thomas wrote:

Bootstraps and regtests on x86_ia64 - OK for trunk?

OK.

Note: For the following, gfortran generates an unneeded temporary
variable; before it depended whether q was an integer 4 or 8 variable
and thus it is not really a newly missed optimization.

   integer(4) :: p(4) = (/2,4,1,3/)
   integer(8) :: q(4) = (/2,4,1,3/)
   p(q) = (/(i, i = 1, 4)/)

Filled as PR 33850.

Yes, I was aware of this problem but did not think that the effort of checking for the dependency between the lvalue 'p' and its vector subscript. I will look for an economical way of accomplishing this.

Thanks

Paul

References:
- [Patch, fortran] PR33749 - Wrong evaluation of expressions in lhs of assignment statements
  - From: Paul Richard Thomas
- Re: [Patch, fortran] PR33749 - Wrong evaluation of expressions in lhs of assignment statements
  - From: Tobias Burnus

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]