From: Timothy Pearson <tpearson@raptorengineering.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Michael Ellerman" <mpe@ellerman.id.au>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"Alex Deucher" <alexdeucher@gmail.com>,
amd-gfx <amd-gfx@lists.freedesktop.org>,
linux@roeck-us.net, linux-kernel <linux-kernel@vger.kernel.org>,
"Dan Horák" <dan@danny.cz>
Subject: Re: [PATCH] drm/amdgpu: Re-enable DCN for 64-bit powerpc
Date: Mon, 25 Jul 2022 14:34:08 -0500 (CDT) [thread overview]
Message-ID: <1446417444.13111032.1658777648586.JavaMail.zimbra@raptorengineeringinc.com> (raw)
In-Reply-To: <CAHk-=wihON4Ytte5zLHWNQtTapUvCpkToxY06OjX-_2B+Gq6Gg@mail.gmail.com>
----- Original Message -----
> From: "Linus Torvalds" <torvalds@linux-foundation.org>
> To: "Michael Ellerman" <mpe@ellerman.id.au>
> Cc: "linuxppc-dev" <linuxppc-dev@lists.ozlabs.org>, "Alex Deucher" <alexdeucher@gmail.com>, "amd-gfx"
> <amd-gfx@lists.freedesktop.org>, linux@roeck-us.net, "linux-kernel" <linux-kernel@vger.kernel.org>, "Dan Horák"
> <dan@danny.cz>, "Timothy Pearson" <tpearson@raptorengineering.com>
> Sent: Monday, July 25, 2022 2:19:57 PM
> Subject: Re: [PATCH] drm/amdgpu: Re-enable DCN for 64-bit powerpc
> On Mon, Jul 25, 2022 at 5:39 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> Further digging shows that the build failures only occur with compilers
>> that default to 64-bit long double.
>
> Where the heck do we have 'long double' things anywhere in the kernel?
>
> I tried to grep for it, and failed miserably. I found some constants
> that would qualify, but they were in the v4l colorspaces-details.rst
> doc file.
>
> Strange.
We don't, at least not that I can see. The affected code uses standard doubles.
What I'm wondering is if the compiler is getting confused between standard and long doubles when they are both the same bit length...
next prev parent reply other threads:[~2022-07-25 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 12:39 Michael Ellerman
2022-07-25 15:45 ` Dan Horák
2022-07-25 18:12 ` Deucher, Alexander
2022-07-25 19:19 ` Linus Torvalds
2022-07-25 19:34 ` Timothy Pearson [this message]
2022-07-25 20:42 ` Segher Boessenkool
2022-07-25 22:40 ` Guenter Roeck
2022-07-26 0:31 ` Segher Boessenkool
2022-07-26 0:47 ` Michael Ellerman
2022-07-26 0:56 ` Michael Ellerman
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=1446417444.13111032.1658777648586.JavaMail.zimbra@raptorengineeringinc.com \
--to=tpearson@raptorengineering.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dan@danny.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®