Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Tiemen Schut <T.Schut@sron.nl>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] sim/erc32/ max simulation time extended by using 64bit 	ints
Date: Fri, 21 May 2010 17:13:00 -0000	[thread overview]
Message-ID: <AANLkTikccYKQ6K4pjASy4xdz0CL9-z3PdUgyx9_MxTu-@mail.gmail.com> (raw)
In-Reply-To: <4BF6A36A.4040308@oarcorp.com>

On Fri, May 21, 2010 at 8:14 AM, Joel Sherrill
<joel.sherrill@oarcorp.com> wrote:
> On 05/21/2010 10:05 AM, Joel Brobecker wrote:
>>>>>
>>>>>         * sis.h: Remove #include<stdint.h>.
>>>>>         (uint64, int64): Redefine without using stdint.h.
>>>>>         (UINT64_MAX): Define.
>>>>>
>>>>
>>>> FYI: I just checked that one in.
>>>>
>>>>
>>>
>>> Doug do you still want that VAL ->  strtol/ll change?
>>>
>>
>> Can you provide more info, which change is that?
>>
>
> Doug seemed to want to get rid of the "VAL" macros
> in the sim/erc32 source code.  I handled one file in
> this patch because it was only used once in the file
> and it seemed silly to even have the macro.  The other
> two files had more uses so I wanted to wait until
> the maximum time to 64 bits was committed.
>
> Here is his comment
>
>   1)
>
>   -#define     VAL(x)  strtol(x,(char **)NULL,0)
>   +#define     VAL(x)  strtoull(x,(char **)NULL,0)
>
>
>   I realize VAL is only used once in interf.c but it's also defined in
>   other files as well.
>   While one could consolidate them, having the macro at all is probably
>   less preferable to just calling strtoul{,l} directly.
>   I would just remove it from interf.c and call strtoull directly.
>
> I have fixed this in interf.c.  But didn't touch the other files.
> Is this OK?

I only mentioned it because the original patch changed its definition
and instead of doing that it seemed better to just get rid of it.
But it's not critical or anything, just "IWBN".


      reply	other threads:[~2010-05-21 16:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 13:25 Tiemen Schut
2010-04-23 20:28 ` Doug Evans
2010-05-04 21:16   ` Joel Sherrill
2010-05-07 17:48     ` Doug Evans
2010-05-17  2:08     ` Joel Brobecker
2010-05-17  3:23       ` Joel Sherrill
2010-05-17 16:37       ` Doug Evans
2010-05-17 16:59         ` Joel Brobecker
2010-05-20 23:13       ` Joel Brobecker
2010-05-21 13:47         ` Joel Sherrill
2010-05-21 15:06           ` Joel Brobecker
2010-05-21 15:15             ` Joel Sherrill
2010-05-21 17:13               ` Doug Evans [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=AANLkTikccYKQ6K4pjASy4xdz0CL9-z3PdUgyx9_MxTu-@mail.gmail.com \
    --to=dje@google.com \
    --cc=T.Schut@sron.nl \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joel.sherrill@oarcorp.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