Hi!
On Mon, Nov 26, 2018 at 08:41:24AM +0700, Arseny Solokha wrote:
> > On Fri, Nov 23, 2018 at 06:15:47PM +0700, Arseny Solokha wrote:
> >> I've found recently that rs6000 and powerpcspe backends can easily trip
> >> over
> >> various gcc_unreachable()'s and gcc_assert()'s in their respective co
> Hi Arseny,
>
> On Fri, Nov 23, 2018 at 06:15:47PM +0700, Arseny Solokha wrote:
>> I've found recently that rs6000 and powerpcspe backends can easily trip over
>> various gcc_unreachable()'s and gcc_assert()'s in their respective copies of
>> print_operand() when provided with some invalid assemb
Hi Arseny,
On Fri, Nov 23, 2018 at 06:15:47PM +0700, Arseny Solokha wrote:
> I've found recently that rs6000 and powerpcspe backends can easily trip over
> various gcc_unreachable()'s and gcc_assert()'s in their respective copies of
> print_operand() when provided with some invalid assembly (i.e.
Hi,
I've found recently that rs6000 and powerpcspe backends can easily trip over
various gcc_unreachable()'s and gcc_assert()'s in their respective copies of
print_operand() when provided with some invalid assembly (i.e. assembly written
for other architectures). For example, when feeding
gcc/te
