From: Dave Brolley <brolley@redhat.com>
To: Mehak Mahajan <mehak.mahajan@gmail.com>
Cc: cgen@sources.redhat.com
Subject: Re: Is there a function in cgen for parsing short integers?
Date: Sat, 19 Apr 2008 00:09:00 -0000 [thread overview]
Message-ID: <4809134F.8070703@redhat.com> (raw)
In-Reply-To: <480907B5.8020201@gmail.com>
Why would you want to issue a diagnostic for -1? It's not out of range
for a 16 bit literal. I would think you would be more interested in
cases like 65536 or -65535. As for the user specifying 0xffffffff, I'm
wondering if cgen_parse_signed_integer will indicate an error since (in
C at least) that's out range of a signed 32 bit integer.
Mehak Mahajan wrote:
> Hi,
>
> Thanks for your reply. :)
> I am doing precisely what you have decribed.
> However, I need to differentiate between -1 which is represented as a
> 16 bit number (0xFFFF) and -1 which is represented as a 32 bit number
> (0xFFFFFFFF).
> Is there a way to do that?
>
> Cheers,
> Mehak
WARNING: multiple messages have this Message-ID
From: Dave Brolley <brolley@redhat.com>
To: Mehak Mahajan <mehak.mahajan@gmail.com>
Cc: cgen@sources.redhat.com
Subject: Re: Is there a function in cgen for parsing short integers?
Date: Sat, 19 Apr 2008 17:24:00 -0000 [thread overview]
Message-ID: <4809134F.8070703@redhat.com> (raw)
Message-ID: <20080419172400.ZtL4ItoH2t5sYDUeM9lIxvkv9W3UiajP1peCBt3t6Fw@z> (raw)
In-Reply-To: <480907B5.8020201@gmail.com>
Why would you want to issue a diagnostic for -1? It's not out of range
for a 16 bit literal. I would think you would be more interested in
cases like 65536 or -65535. As for the user specifying 0xffffffff, I'm
wondering if cgen_parse_signed_integer will indicate an error since (in
C at least) that's out range of a signed 32 bit integer.
Mehak Mahajan wrote:
> Hi,
>
> Thanks for your reply. :)
> I am doing precisely what you have decribed.
> However, I need to differentiate between -1 which is represented as a
> 16 bit number (0xFFFF) and -1 which is represented as a 32 bit number
> (0xFFFFFFFF).
> Is there a way to do that?
>
> Cheers,
> Mehak
next prev parent reply other threads:[~2008-04-19 0:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 20:42 Mehak Mahajan
2008-04-19 0:09 ` Dave Brolley [this message]
2008-04-19 17:24 ` Dave Brolley
-- strict thread matches above, loose matches on Subject: below --
2008-04-17 23:10 Mehak Mahajan
2008-04-18 15:24 ` Dave Brolley
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=4809134F.8070703@redhat.com \
--to=brolley@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=mehak.mahajan@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).