From: Segher Boessenkool <segher@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: "atomic" 64-bit math on 32-bit ppc's?
Date: Thu, 6 Sep 2007 16:09:53 +0200 [thread overview]
Message-ID: <b976a70bd1942da7e31b9a409b2de569@kernel.crashing.org> (raw)
In-Reply-To: <20070906134354.GA16153@ld0162-tx32.am.freescale.net>
>> Either way, it's a bit late to change this, no?
>
> Sure, I was just whining due to having been bitten by this sort of bug
> in
> the past. :-)
Write a song about it, it's therapeutical it seems!
Segher
next prev parent reply other threads:[~2007-09-06 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 11:09 "atomic" 64-bit math on 32-bit ppc's? Matt Sealey
2007-09-04 11:39 ` Gabriel Paubert
2007-09-04 12:31 ` Matt Sealey
2007-09-04 16:02 ` Gabriel Paubert
2007-09-04 17:40 ` Matt Sealey
2007-09-05 1:04 ` David Gibson
2007-09-04 18:48 ` Scott Wood
2007-09-06 13:21 ` Segher Boessenkool
2007-09-06 13:43 ` Scott Wood
2007-09-06 14:09 ` Segher Boessenkool [this message]
2007-09-10 20:39 ` Jon Loeliger
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=b976a70bd1942da7e31b9a409b2de569@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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 NNTP newsgroup(s).