From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Expand fortran array bounds sizes to LONGEST
Date: Tue, 21 Aug 2012 11:12:00 -0000 [thread overview]
Message-ID: <20120821164151.0e69b8e8@spoyarek> (raw)
In-Reply-To: <20120821152540.013b4d99@spoyarek>
On Tue, 21 Aug 2012 15:25:40 +0530, Siddhesh wrote:
> Range bounds for a gdb type can have LONGEST values for low and high
> bounds. Fortran range bounds functions however use only int. The
> larger ranges don't compile by default on gcc, but it is possible to
> override the check in the compiler by using -fno-range-check. As a
> result, this check is necessary so that we don't print junk in case
> of an overflow.
Sorry, I forgot to mention that this goes on top of the bitpos patch
since it needs some changes from the bitpos patch as well.
Regards,
Siddhesh
next prev parent reply other threads:[~2012-08-21 11:12 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 [this message]
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
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=20120821164151.0e69b8e8@spoyarek \
--to=siddhesh@redhat.com \
--cc=gdb-patches@sourceware.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