Jakub Jelinek - Re: Vectorizing HIRLAM 4: complicated access patterns examined. (original) (raw)

This is the mail archive of the gcc@gcc.gnu.orgmailing list for the GCC project.

• From: Jakub Jelinek
• To: Tobias dot Schlueter at Physik dot Uni-Muenchen dot DE
• Cc: Paul Thomas , Toon Moene , fortran at gcc dot gnu dot org, gcc at gcc dot gnu dot org
• Date: Tue, 1 Nov 2005 15:26:58 +0100
• Subject: Re: Vectorizing HIRLAM 4: complicated access patterns examined.
• References: E1EVDBS-0006ob-4S@laptop.moene.indiv.nluug.nl <436758AA.4060902@wanadoo.fr> <1130850103.43676737a4f69@www.cip.physik.uni-muenchen.de>
• Reply-to: Jakub Jelinek

On Tue, Nov 01, 2005 at 02:01:43PM +0100, Tobias.Schlueter@Physik.Uni-Muenchen.DE wrote:

[ Bringing this back to fortran@, taking the optimizer guys out of CC: ]

Quoting Toon Moene:

I still have to construct a bug report of something that confuses the parser and that basically looks like this:

 IMPLICIT CHARACTER*8 (Y)
 CHARACTER*11 Y1, Y2, Y3
 ...
 YA = 'D' // Y1 // Y2(1:3) // Y3(1:3) //
1     // YB(1:5)
      1

Unclassifiable statement at (1)

Unfortunately, if I reduce the code to this one (continued) line and the necessary declarations, it doesn't fail ;-)

Does this fail as long as you keep the type implicit? This reminds me of another PR, where the parser would decide too early that it had seen an array range instead of a substring, which would lead to these kinds of niceties further down the line. Unfortunately, I couldn't find this bug in bugzilla, looks like its PR's summary is not very descriptive.

You mean PR18833?

Jakub

• Follow-Ups:
  • Re: Vectorizing HIRLAM 4: complicated access patterns examined.
    * From: Tobias . Schlueter
• References:
  • Re: Vectorizing HIRLAM 4: complicated access patterns examined.
    * From: Paul Thomas
  • Re: Vectorizing HIRLAM 4: complicated access patterns examined.
    * From: Tobias . Schlueter