From: Daniel Jacobowitz <drow@false.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: why use #ifdef __GNUC__ in sim/ppc/words.h??
Date: Mon, 18 Apr 2005 16:26:00 -0000 [thread overview]
Message-ID: <20050418162623.GA11880@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0504181150530.29047@lazy>
On Mon, Apr 18, 2005 at 11:57:48AM -0500, Manoj Iyer wrote:
>
> sim/ppc/words.h has 3 typedefs enclosed in #ifdef __GNUC__, but I dont see
> anything in the typedef that will require this #ifdef.
>
> #ifdef __GNUC__
> typedef long long natural64;
> typedef signed long long signed64;
> typedef unsigned long long unsigned64;
> #endif
>
> The xlc compiler fails to see any other definition of natural64, signed64
> and unsigned64 and reports them as undefined. Is it ok to remove this
> #ifdef ?
>
> I can change #ifdef __GNUC__ to #if, #else statement to accomodate
> _MSC_VER .
If you want to remove the ifdef, you need to find another way to test
whether long long is available. Many C89 compilers do not support it.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-04-18 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 16:24 Manoj Iyer
2005-04-18 16:26 ` Daniel Jacobowitz [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=20050418162623.GA11880@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.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