From: Brian Koropoff <bkoropoff@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jilles Tjoelker <jilles@stack.nl>, dash@vger.kernel.org
Subject: Re: [PATCH 1/3] Port to Solaris
Date: Sat, 12 Mar 2011 17:18:32 -0800 [thread overview]
Message-ID: <1299979112.3797.9.camel@gemini> (raw)
In-Reply-To: <20110310121659.GC10824@gondor.apana.org.au>
I'll send an updated and rebased patch shortly. Once we've agreed about
what to do with _LARGEFILE64_SOURCE in the HP-UX patch, I'll send a new
version of that as well.
-- Brian
On Thu, 2011-03-10 at 20:16 +0800, Herbert Xu wrote:
> On Fri, Jan 21, 2011 at 01:06:02PM +0000, Jilles Tjoelker wrote:
> >
> > What you can do is use PRIdMAX from <inttypes.h>, normally defined as
> > "jd". You can then define this to "lld" or "jd" if it is not defined.
> > I think this makes the code uglier (just like your change), but oh well.
>
> I agree. Brian, please update your patch accordingly.
>
> Thanks!
>
> > By the way, I wonder what the advantage of imaxdiv() above separate %
> > and / is. Compilers can detect the matching between a % b and a / b and
> > do it in one operation, and any use of imaxdiv() trips gcc's
> > -Waggregate-return.
>
> It used to generate smaller code with gcc. If gcc now knows how
> to optimise it properly then I guess we can remove imaxdiv.
>
> I just checked and gcc 4.4.5 still generates two divisions without
> imaxdiv. On the other hand gcc doesn't even inline imaxdiv.
>
> Cheers,
next prev parent reply other threads:[~2011-03-13 1:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 5:07 Portability patches Brian Koropoff
2011-01-19 5:15 ` [PATCH 1/3] Port to Solaris Brian Koropoff
2011-01-21 13:06 ` Jilles Tjoelker
2011-03-10 12:16 ` Herbert Xu
2011-03-13 1:18 ` Brian Koropoff [this message]
2011-03-13 1:25 ` [PATCH] " Brian Koropoff
2011-03-15 7:36 ` Herbert Xu
2011-01-19 5:15 ` [PATCH 2/3] Port to AIX Brian Koropoff
2011-03-10 12:25 ` Herbert Xu
2011-01-19 5:16 ` [PATCH 3/3] Port to HP-UX Brian Koropoff
2011-03-10 12:26 ` Herbert Xu
2011-03-12 23:54 ` Brian Koropoff
2011-03-15 7:38 ` Herbert Xu
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=1299979112.3797.9.camel@gemini \
--to=bkoropoff@gmail.com \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jilles@stack.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.