public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: "'Nick Clifton'" <nickc@redhat.com>
Cc: "'Alexandre Oliva'" <aoliva@redhat.com>,
	<binutils@sources.redhat.com>,
	"'Joern RENNECKE'" <joern.rennecke@st.com>
Subject: RE: Broken SH2a patches
Date: Tue, 11 Jan 2005 18:01:00 -0000	[thread overview]
Message-ID: <003001c4f807$ae922790$0d0f81a4@uk.w2k.superh.com> (raw)
In-Reply-To: <41C70ABC.8050903@redhat.com>

Hi Nick,

I have found another problem with your patch.

Your patch has:

#define arch_sh2a_or_sh3e  (arch_sh2a_sh4_base)
#define arch_sh2a_or_sh4   (arch_sh2a_sh4_base
|arch_sh_dp_fpu)

Which should be:

#define arch_sh2a_or_sh3e  (arch_sh2a_sh4_base|arch_sh_no_mmu
|arch_sh_sp_fpu)
#define arch_sh2a_or_sh4   (arch_sh2a_sh4_base|arch_sh_no_mmu
|arch_sh_dp_fpu)

Otherwise the -isa=sh2a-or-sh3e and -isa=sh2a-or-sh4 options cause the
assembler to reject all instructions, which isn't helpful.

I am developing a new script for the testsuite which will hopefully point
all these issues out in future, should anybody make any broken changes. It
hasn't found any issues with your patch other than the ones I have already
pointed out (although I have had to modifiy sh-opc.h a little to make it
work, so maybe I am not testing the same thing).

Interestingly, one thing my script has exposed is that mul.l is defined
twice! Once for sh2 and once for sh1, which is obviously wrong.

--
Andrew Stubbs
andrew.stubbs@st.com
andrew.stubbs@superh.com

  parent reply	other threads:[~2005-01-11 18:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 17:00 Andrew STUBBS
2004-10-28 20:33 ` Alexandre Oliva
2004-10-29 10:39   ` Nick Clifton
2004-10-29 12:11     ` Andrew STUBBS
2004-10-29 12:28       ` [OT] " Dave Korn
2004-10-29 12:59         ` Andrew STUBBS
2004-10-29 13:03           ` Dave Korn
2004-10-29 13:21             ` Andrew STUBBS
2004-10-29 13:59       ` Ian Lance Taylor
2004-10-29 14:35         ` Andrew STUBBS
2004-10-29 14:58           ` Ian Lance Taylor
2004-10-29 15:44             ` Andrew STUBBS
2004-11-08  9:04       ` Nick Clifton
2004-11-08 15:12         ` Andrew STUBBS
2004-11-08 16:27           ` Joern RENNECKE
2004-11-08 16:36           ` Joern RENNECKE
2004-12-15 17:11           ` Nick Clifton
2004-12-16 13:24             ` Andrew STUBBS
2004-12-20 17:18               ` Nick Clifton
2005-01-05 13:27                 ` Andrew STUBBS
2005-01-06 11:28                 ` Andrew STUBBS
2005-01-12 16:23                   ` Nick Clifton
2005-01-07 12:55                 ` Andrew STUBBS
2005-01-10 13:31                   ` Joern RENNECKE
2005-01-11 18:01                 ` Andrew STUBBS [this message]
2004-12-02 12:19 Andrew STUBBS

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='003001c4f807$ae922790$0d0f81a4@uk.w2k.superh.com' \
    --to=andrew.stubbs@st.com \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=joern.rennecke@st.com \
    --cc=nickc@redhat.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).