From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com, per@bothner.com
Subject: Re: Fix PR gdb/265, 64-bit pointers in Java
Date: Wed, 20 Feb 2002 14:41:00 -0000 [thread overview]
Message-ID: <20020220174154.A29999@nevyn.them.org> (raw)
In-Reply-To: <20020211003818.A26546@nevyn.them.org>
On Mon, Feb 11, 2002 at 12:38:18AM -0500, Daniel Jacobowitz wrote:
> I don't know if Java allows the implicit 0x123456789 -> 0x123456789L
> conversion that we all know and love in C, but it certainly behooves us to
> act that way on the command line. Per, does this patch look OK?
Per never answered me, and I satisfied Tom's objections. I'm committing
this as reasonably obvious, in my quest to shrink the number of "I
should look at this" PRs in my mailbox.
>
> --
> Daniel Jacobowitz Carnegie Mellon University
> MontaVista Software Debian GNU/Linux Developer
>
> 2002-02-11 Daniel Jacobowitz <drow@mvista.com>
>
> Fix PR gdb/265
> * jv-exp.y (parse_number): Handle 64-bit integers.
>
> Index: jv-exp.y
> ===================================================================
> RCS file: /cvs/src/src/gdb/jv-exp.y,v
> retrieving revision 1.3
> diff -u -p -r1.3 jv-exp.y
> --- jv-exp.y 2001/03/06 08:21:09 1.3
> +++ jv-exp.y 2002/02/11 05:32:18
> @@ -764,13 +764,13 @@ parse_number (p, len, parsed_float, puti
> }
>
> c = p[len-1];
> + /* A paranoid calculation of (1<<64)-1. */
> limit = (ULONGEST)0xffffffff;
> + limit = ((limit << 16) << 16) | limit;
> if (c == 'l' || c == 'L')
> {
> type = java_long_type;
> len--;
> - /* A paranoid calculation of (1<<64)-1. */
> - limit = ((limit << 16) << 16) | limit;
> }
> else
> {
> @@ -797,9 +797,13 @@ parse_number (p, len, parsed_float, puti
> n += c;
> }
>
> - putithere->typed_val_int.val = n;
> - putithere->typed_val_int.type = type;
> - return INTEGER_LITERAL;
> + if (type == java_int_type && n > (ULONGEST)0xffffffff)
> + type = java_long_type;
> +
> + putithere->typed_val_int.val = n;
> + putithere->typed_val_int.type = type;
> +
> + return INTEGER_LITERAL;
> }
>
> struct token
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-20 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 21:38 Daniel Jacobowitz
2002-02-11 10:24 ` Tom Tromey
2002-02-11 10:31 ` Daniel Jacobowitz
2002-02-20 14:41 ` Daniel Jacobowitz [this message]
2002-02-20 15:04 ` Per Bothner
2002-02-20 15:44 ` Daniel Jacobowitz
2002-02-20 17:30 ` Per Bothner
2002-02-20 18:05 ` Daniel Jacobowitz
2002-02-20 18:11 ` Per Bothner
2002-02-20 18:55 ` Daniel Jacobowitz
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=20020220174154.A29999@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=per@bothner.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