On Thu, 2018-02-15 at 14:01 +, Richard Earnshaw (lists) wrote:
>
> Wouldn't it be better to call output_operand_lossage() with a suitable
> diagnostic message? If the operand isn't in Pmode assembly will
> (should) fail anyway.
>
> R.
How about this patch? In addtion to the code change I u
On 02/09/2018 05:14 PM, Segher Boessenkool wrote:
> Hi!
>
> On Fri, Feb 09, 2018 at 09:37:28AM +, Nick Clifton wrote:
>>> I thought you were going to do a patch like the following, to make the
>>> e500 cores less special (they are not):
>>
>> Sorry - my bad. I defer to your patch then. Whate
On Fri, Feb 16, 2018 at 06:05:13PM -0700, Jeff Law wrote:
> > From: Segher Boessenkool
> > Date: Thu, 8 Feb 2018 16:58:33 +
> > Subject: [PATCH] Do not mess with rs6000_{single,double}_float (PR68028)
> >
> > For e500 family cores we do some questionable things with those flags,
> > which doe
Another maybe_record_trace_start issue found by my tester. This time
the rx port.
We failed to add suitable notes for the CFI machinery. There's still
paths (particularly those which save/restore the accumulators) that may
need further adjustment. However, this patch is enough to get
libgcc/ne
101 - 104 of 104 matches
Mail list logo