public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41113] spurious  _gfortran_internal_pack
Date: Fri, 21 Aug 2009 06:09:00 -0000	[thread overview]
Message-ID: <20090821060936.3995.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41113-6642@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from jv244 at cam dot ac dot uk  2009-08-21 06:09 -------
(In reply to comment #2)
> which returns "false". It gets quite complicated if we want to handle:
>    foo(1)%bar(1:1)%variable(:)(sub:string)

AFAICT this is already handled fine:
write(6,*) foo(1)%bar(1:1)%variable(:)(2:4)
         1
Error: Two or more part references with nonzero rank must not be specified at
(1)

> Attached patch does the first steps, but it needs some improvements to handle 
> "sym" and "comp" correctly. "sym->" appears all over the place in the rest of
> the function and it needs to be properly handled.  (NOTE: The attached patch
> will not work!)

I believe that some function which can find if an expression is really  a
contiguous array in memory is pretty useful. In the end, many optimization
(also vectorization) relies on that.

I have another example, I will file it as a different PR, but make a
'cross-link'


-- 

jv244 at cam dot ac dot uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu dot
                   |                            |org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41113


  parent reply	other threads:[~2009-08-21  6:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 20:36 [Bug fortran/41113] New: " jv244 at cam dot ac dot uk
2009-08-19  8:59 ` [Bug fortran/41113] " jv244 at cam dot ac dot uk
2009-08-19 13:31 ` burnus at gcc dot gnu dot org
2009-08-21  6:09 ` jv244 at cam dot ac dot uk [this message]
2009-08-21  6:15 ` jv244 at cam dot ac dot uk
2009-12-20 18:47 ` pault at gcc dot gnu dot org
2009-12-20 21:58 ` pault at gcc dot gnu dot org
2010-02-06 16:40 ` jv244 at cam dot ac dot uk
2010-02-06 16:47 ` rguenth at gcc dot gnu dot org
2010-02-08  8:10 ` jv244 at cam dot ac dot uk
2010-02-08 14:06 ` pault at gcc dot gnu dot org
2010-02-08 14:38 ` jv244 at cam dot ac dot uk
2010-02-08 17:26 ` pault at gcc dot gnu dot org
2010-02-08 20:49 ` dominiq at lps dot ens dot fr
2010-02-08 20:53 ` dominiq at lps dot ens dot fr
2010-02-08 20:53 ` dominiq at lps dot ens dot fr
2010-02-10  9:17 ` burnus at gcc dot gnu dot org
2010-02-13 12:43 ` pault at gcc dot gnu dot org
2010-02-14 19:26 ` pault at gcc dot gnu dot org
2010-02-14 19:58 ` dominiq at lps dot ens dot fr
2010-02-14 20:07 ` dominiq at lps dot ens dot fr
2010-02-14 20:16 ` dominiq at lps dot ens dot fr
2010-02-20 21:51 ` burnus at gcc dot gnu dot org
2010-02-21 10:43 ` paul dot richard dot thomas at gmail dot com
2010-02-21 14:16 ` jv244 at cam dot ac dot uk
2010-02-22  5:45 ` pault at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090821060936.3995.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).