From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [PATCH] Expand fortran array bounds sizes to LONGEST
Date: Sun, 21 Oct 2012 07:44:00 -0000 [thread overview]
Message-ID: <20121021131337.0ff8afa2@spoyarek> (raw)
In-Reply-To: <20121015185626.GA27290@host2.jankratochvil.net>
On Mon, 15 Oct 2012 20:56:26 +0200, Jan wrote:
> On Mon, 15 Oct 2012 15:25:55 +0200, Jan Kratochvil wrote:
> > I have filed for it now:
> > Invalid debug/ array bounds w/-fno-range-check and 32-bit
> > target http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54934
>
> Therefore it looks as a valid gfortran FSF GCC HEAD bug so provided
> a hand-patched .S file for i386; patched GDB PASSes with it.
Thanks, I'll update my stash with this test.
Siddhesh
prev parent reply other threads:[~2012-10-21 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 9:56 Siddhesh Poyarekar
2012-08-21 11:12 ` Siddhesh Poyarekar
2012-08-21 18:22 ` Tom Tromey
2012-08-21 18:10 ` Siddhesh Poyarekar
2012-08-21 18:21 ` Tom Tromey
2012-08-21 18:22 ` Tom Tromey
2012-10-15 13:26 ` Jan Kratochvil
2012-10-15 18:56 ` Jan Kratochvil
2012-10-21 7:44 ` Siddhesh Poyarekar [this message]
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=20121021131337.0ff8afa2@spoyarek \
--to=siddhesh@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=sergiodj@redhat.com \
/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