From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: libc-ports@sourceware.org
Subject: Re: Avoid endian.h include in MIPS string functions
Date: Sun, 06 May 2012 05:55:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.00.1205060642240.19691@eddie.linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1204261923210.30855@digraph.polyomino.org.uk>
On Thu, 26 Apr 2012, Joseph S. Myers wrote:
> Similar to a recent SH libc change, I've applied this patch to avoid MIPS
> string .S functions including <endian.h> and getting errors from C source
> code from that header.
Hmm, <endian.h> is a user header and I could imagine software to rely on
it even in handcoded assembly. And it used to work just fine. Are you
sure the problematic stuff in <endian.h> or pulled by it shouldn't be
wrapped into:
#ifndef __ASSEMBLER__
or suchlike instead?
Maciej
next prev parent reply other threads:[~2012-05-06 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 19:25 Joseph S. Myers
2012-04-28 10:42 ` Joseph S. Myers
2012-05-06 5:55 ` Maciej W. Rozycki [this message]
2012-05-06 6:28 ` Mike Frysinger
2012-05-19 18:33 ` Maciej W. Rozycki
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=alpine.LFD.2.00.1205060642240.19691@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
/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).