From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: Joel Sherrill <joel.sherrill@oarcorp.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: Mon, 17 May 2010 16:59:00 -0000 [thread overview]
Message-ID: <20100517165023.GF2805@adacore.com> (raw)
In-Reply-To: <AANLkTikjRxHbSDd_ROeUlpwomwb-L6n0ewm4n0izHoaj@mail.gmail.com>
> > Unfortunately, this change breaks the build when stdint.h is not
> > available (Eg. sparc-solaris).
>
> How old is this solaris?
It's solaris 2.8.
> > Doug: Would that be OK to commit? I think that the cleanest thing to do
> > Â Â Â here would be to have some configury that would provide our own
> > Â Â Â stdint.h when missing. Â We already do that for GDB by using gnulib
> > Â Â Â so perhaps one way to do so would be to share the gnulib between
> > Â Â Â GDB and the sim (probably meaning moving it to the root directory).
>
> For reference sake, there's bfd_stdint.h generated by
> config/stdint.m4. I don't know all that it handles, but again gdb
> itself just includes stdint.h unconditionally.
This is because GDB relies on gnulib providing stdint.h for us if
the system doesn't already provide it. See gdb/gnulib/.
--
Joel
next prev parent reply other threads:[~2010-05-17 16:50 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 [this message]
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
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=20100517165023.GF2805@adacore.com \
--to=brobecker@adacore.com \
--cc=T.Schut@sron.nl \
--cc=dje@google.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