public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: Matthew Fortune <Matthew.Fortune@imgtec.com>,
	       binutils@sourceware.org
Subject: Re: [committed] MIPS/GAS: Fix an ISA override not lifting ABI restrictions
Date: Fri, 22 Apr 2016 01:12:00 -0000	[thread overview]
Message-ID: <20160422011230.GL24051@linux-mips.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1604212314170.21846@tp.orcam.me.uk>

On Fri, Apr 22, 2016 at 01:26:55AM +0100, Maciej W. Rozycki wrote:

> Hi,
> 
>  The new test suite cases should reasonably cover the semantics of ISA 
> overrides, as far as both code generation and code rejection is concerned.  
> I had to factor in some limitations which I plan to resolve later:
> 
> 1. The list test infrastructure does not allow to name a different source
>    file.  To address this I repeated the same source for output variants.
> 
> 2. There's an outstanding issue with ISA overrides where the new ISA does 
>    not support ISA extensions selected.  A warning is printed in that 
>    case.  I had an off-list discussion a while ago and the consensus was
>    any unsupported ISA extensions should be quietly temporarily disabled.
>    Meanwhile I have added extra patterns for `octeon3' assembly which
>    triggers the problem.
> 
>  This issue was discovered in automatic Linux kernel testing.  Thanks, 
> Ralf, for bringing my attention to it!

Excellent, thank you!

Will the patch also work for 2.25 and 2.26?

  Ralf

  reply	other threads:[~2016-04-22  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22  0:27 Maciej W. Rozycki
2016-04-22  1:12 ` Ralf Baechle [this message]
2016-04-22  1:28   ` Maciej W. Rozycki
2016-04-22  3:36 ` Hans-Peter Nilsson
2016-04-22 13:21   ` Maciej W. Rozycki

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=20160422011230.GL24051@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=binutils@sourceware.org \
    --cc=macro@imgtec.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).