On Tue, Feb 07, 2023 at 03:22:41PM +0100, Richard Biener via Gcc-patches wrote:
> > He did not specify --with=cpu= or --with-tune=, which means he got
> > power8 defaults for both of those. It's hard for me to believe that
> > --with-tune=power9 could hide the issue, but we'll try that configurati
On Mon, Feb 6, 2023 at 7:28 PM Peter Bergner wrote:
>
> On 2/3/23 1:42 AM, Richard Biener wrote:
> > On Fri, Feb 3, 2023 at 6:44 AM Michael Meissner via Gcc-patches
> > wrote:
> >>
> >> I'm reposting these two patches that allow GCC to build on Fedora 36 just
> >> to be
> >> clear which patches
On 2/3/23 1:42 AM, Richard Biener wrote:
> On Fri, Feb 3, 2023 at 6:44 AM Michael Meissner via Gcc-patches
> wrote:
>>
>> I'm reposting these two patches that allow GCC to build on Fedora 36 just to
>> be
>> clear which patches I'm talking about. The issue is that if GCC is
>> configured
>> wit
On Fri, Feb 3, 2023 at 6:44 AM Michael Meissner via Gcc-patches
wrote:
>
> I'm reposting these two patches that allow GCC to build on Fedora 36 just to
> be
> clear which patches I'm talking about. The issue is that if GCC is configured
> with long double using the IEEE 128-bit representation, i
I'm reposting these two patches that allow GCC to build on Fedora 36 just to be
clear which patches I'm talking about. The issue is that if GCC is configured
with long double using the IEEE 128-bit representation, it currently cannot
build _mulkc3 and _divkc3 in libgcc.
Note, these patches do not
