From: trevor_smigiel@playstation.sony.com
To: Ben Elliston <bje@au1.ibm.com>
Cc: gcc-patches@gcc.gnu.org, pinskia@gmail.com, Ulrich.Weigand@de.ibm.com
Subject: Re: [PATCH, spu]: implement MFC tag manager
Date: Wed, 07 Nov 2007 02:38:00 -0000 [thread overview]
Message-ID: <20071107023824.GF18349@playstation.sony.com> (raw)
In-Reply-To: <1194401325.26692.2.camel@localhost>
> > I guess I would argue for leaving stdint.h in for compatibility and to
> > keep uint32_t defined. And use an #ifdef while building libgcc.
>
> How about if I use an IN_LIBGCC test to ensure that the code can be
> compiled without spu_mfcio.h for libgcc, but does not change behaviour
> for users #including an installed spu_mfcio.h? OK with that change?
>
> Cheers, Ben
Yeah, I think that's ok.
I'm still testing the patch. I'll let you know ASAP if it is ok.
Trevor
next prev parent reply other threads:[~2007-11-07 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 12:11 Ben Elliston
2007-11-07 1:34 ` trevor_smigiel
2007-11-07 2:09 ` Ben Elliston
2007-11-07 2:38 ` trevor_smigiel [this message]
2007-11-14 23:34 ` trevor_smigiel
2007-11-20 11:33 ` Ben Elliston
2007-10-29 21:22 Ben Elliston
2007-11-07 1:02 ` Ben Elliston
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=20071107023824.GF18349@playstation.sony.com \
--to=trevor_smigiel@playstation.sony.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=bje@au1.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@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).