public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40598] Some missed optimizations in array assignment
Date: Wed, 01 Jul 2009 07:52:00 -0000 [thread overview]
Message-ID: <20090701075159.14490.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40598-10374@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from burnus at gcc dot gnu dot org 2009-07-01 07:51 -------
(In reply to comment #4)
Here, I do not get any segfault/problem with valgrind (for gfortran and a.out).
> tmp = build4 (ARRAY_RANGE_REF, TREE_TYPE (dest), dest,
> build_int_cst (gfc_array_index_type, 3),
I actually do not understand why "3" works. If I read gccint (cf. comment 2)
correctly I would have expect that one needs to passe the byte size. But it
seems to work as the dump / a.out indicates.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40598
next prev parent reply other threads:[~2009-07-01 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 7:53 [Bug fortran/40598] New: " pault at gcc dot gnu dot org
2009-06-30 9:40 ` [Bug fortran/40598] " rguenth at gcc dot gnu dot org
2009-06-30 9:47 ` burnus at gcc dot gnu dot org
2009-06-30 9:55 ` pault at gcc dot gnu dot org
2009-06-30 12:57 ` pault at gcc dot gnu dot org
2009-07-01 7:52 ` burnus at gcc dot gnu dot org [this message]
2009-07-01 8:23 ` pault at gcc dot gnu dot org
2009-07-01 9:43 ` rguenth at gcc dot gnu dot org
2009-07-01 10:51 ` pault at gcc dot gnu dot org
2009-07-01 11:02 ` pault at gcc dot gnu dot org
2010-05-07 21:02 ` dfranke at gcc dot gnu dot org
2010-05-08 12:57 ` pault at gcc dot gnu dot org
2010-05-08 20:58 ` dfranke 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=20090701075159.14490.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).