On Mon, Jun 20, 2022 at 09:48:34AM +0200, Sebastian Huber wrote:
> On 04/04/2022 11:31, Sebastian Huber wrote:
> >Hello Segher,
> >
> >On 15/03/2022 23:29, Segher Boessenkool wrote:
> >>On Tue, Mar 15, 2022 at 03:29:23PM +0100, Sebastian Huber wrote:
> >>>now that the PR104829 is fixed could I back
On 04/04/2022 11:31, Sebastian Huber wrote:
Hello Segher,
On 15/03/2022 23:29, Segher Boessenkool wrote:
On Tue, Mar 15, 2022 at 03:29:23PM +0100, Sebastian Huber wrote:
now that the PR104829 is fixed could I back port
Segher Boessenkool (2):
rs6000: Improve .machine
rs6000: Do not use
Hello Segher,
On 15/03/2022 23:29, Segher Boessenkool wrote:
On Tue, Mar 15, 2022 at 03:29:23PM +0100, Sebastian Huber wrote:
now that the PR104829 is fixed could I back port
Segher Boessenkool (2):
rs6000: Improve .machine
rs6000: Do not use rs6000_cpu for .machine ppc and ppc64 (PR1048
Hi!
On Tue, Mar 15, 2022 at 03:29:23PM +0100, Sebastian Huber wrote:
> now that the PR104829 is fixed could I back port
>
> Segher Boessenkool (2):
> rs6000: Improve .machine
> rs6000: Do not use rs6000_cpu for .machine ppc and ppc64 (PR104829)
>
> to GCC 10 and 11?
I will do it, in a few d
Hello Segher,
On 10/03/2022 11:11, Segher Boessenkool wrote:
On Thu, Mar 10, 2022 at 09:25:21AM +0100, Sebastian Huber wrote:
On 04/03/2022 17:51, Segher Boessenkool wrote:
This adds more correct .machine for most older CPUs. It should be
conservative in the sense that everything we handled b
Hi!
On Thu, Mar 10, 2022 at 09:25:21AM +0100, Sebastian Huber wrote:
> On 04/03/2022 17:51, Segher Boessenkool wrote:
> >This adds more correct .machine for most older CPUs. It should be
> >conservative in the sense that everything we handled before we handle at
> >least as well now. This does n
On 04/03/2022 17:51, Segher Boessenkool wrote:
Hi!
This adds more correct .machine for most older CPUs. It should be
conservative in the sense that everything we handled before we handle at
least as well now. This does not yet revamp the server CPU handling, it
is too risky at this point in ti
On Mon, Mar 07, 2022 at 08:53:42PM +, Joseph Myers wrote:
> This breaks the build of libgcc for powerpc-linux-gnu (32-bit, default
> CPU; configured --disable-multilib --enable-secureplt).
>
> cc1: warning: The '-mfloat128' option may not be fully supported
> /tmp/ccHCPzSh.s: Assembler messag
This breaks the build of libgcc for powerpc-linux-gnu (32-bit, default
CPU; configured --disable-multilib --enable-secureplt).
cc1: warning: The '-mfloat128' option may not be fully supported
/tmp/ccHCPzSh.s: Assembler messages:
/tmp/ccHCPzSh.s:163: Error: unrecognized opcode: `lfiwzx'
/scratch/j
Hi!
This adds more correct .machine for most older CPUs. It should be
conservative in the sense that everything we handled before we handle at
least as well now. This does not yet revamp the server CPU handling, it
is too risky at this point in time.
Tested on powerpc64-linux {-m32,-m64}. Also
10 matches
Mail list logo