public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26001] [4.1/4.2 Regression] expand uses the wrong part of the string for array accesses
Date: Mon, 30 Jan 2006 19:27:00 -0000 [thread overview]
Message-ID: <20060130192749.7137.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26001-10743@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from pinskia at gcc dot gnu dot org 2006-01-30 19:27 -------
(In reply to comment #11)
> I'm not sure what you're trying to say, so let me rephrase: given the advanced
> state of 4.1 in the relase cycle, it may make sense to revert Feng Wang's patch
> in 4.1, and to fix the underlying bug only in the trunk.
That might be a good idea, I was just not thinking too well today for some
reason.
> > Here is the reduced testcase that passes at -O0 but fails at -O1.
> > CHARACTER*10 INTSTR
> > CHARACTER C1
> > DATA INTSTR / '0123456789' /
> >
> > C1 = INTSTR(1:1)
> > print *, C1
> > if(C1 .ne. '0') call abort()
> >
> > end
>
> Thanks, do you still get '1' in the RTL dump if you change INSTR? IOW, does it
> address the elements of the string incorrectly,
>
> if (c1[1]{lb: 1 sz: 1} != "0"[1]{lb: 1 sz: 1})
> ^^^
> this (t02.original) looks like a possible off-by-one error.
[1] here is correct, the arrary bounds is 1:1 and not the C array bounds
starting at 0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26001
next prev parent reply other threads:[~2006-01-30 19:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 6:01 [Bug regression/26001] New: LAPACK testsuite failure with optimization jvdelisle at gcc dot gnu dot org
2006-01-28 7:12 ` [Bug regression/26001] " jvdelisle at gcc dot gnu dot org
2006-01-28 7:13 ` jvdelisle at gcc dot gnu dot org
2006-01-30 18:42 ` kargl at gcc dot gnu dot org
2006-01-30 18:49 ` [Bug fortran/26001] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-01-30 18:52 ` tobi at gcc dot gnu dot org
2006-01-30 18:59 ` [Bug tree-optimization/26001] " pinskia at gcc dot gnu dot org
2006-01-30 19:02 ` pinskia at gcc dot gnu dot org
2006-01-30 19:07 ` tobi at gcc dot gnu dot org
2006-01-30 19:08 ` [Bug middle-end/26001] " pinskia at gcc dot gnu dot org
2006-01-30 19:13 ` pinskia at gcc dot gnu dot org
2006-01-30 19:23 ` [Bug middle-end/26001] [4.1/4.2 Regression] expand uses the wrong part of the string for array accesses tobi at gcc dot gnu dot org
2006-01-30 19:27 ` pinskia at gcc dot gnu dot org [this message]
2006-01-30 19:32 ` pinskia at gcc dot gnu dot org
2006-01-30 19:37 ` tobi at gcc dot gnu dot org
2006-01-30 19:39 ` pinskia at gcc dot gnu dot org
2006-01-31 4:56 ` pinskia at gcc dot gnu dot org
2006-01-31 5:19 ` pinskia at gcc dot gnu dot org
2006-01-31 5:33 ` pinskia at gcc dot gnu dot org
2006-01-31 6:39 ` jvdelisle at gcc dot gnu dot org
2006-01-31 14:05 ` pinskia at gcc dot gnu dot org
2006-02-01 1:04 ` pinskia at gcc dot gnu dot org
2006-02-01 1:04 ` [Bug middle-end/26001] [4.1 " pinskia at gcc dot gnu dot org
2006-02-01 3:09 ` mmitchel at gcc dot gnu dot org
2006-02-03 18:31 ` pinskia at gcc dot gnu dot org
2006-02-03 18:31 ` pinskia at gcc dot gnu dot org
2006-02-04 7:51 ` fengwang 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=20060130192749.7137.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).