public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: Richard Sandiford <rdsandiford@googlemail.com>,
	binutils@sourceware.org,     Chao-ying Fu <fu@mips.com>,
	Rich Fuhler <rich@mips.com>,     David Lau <davidlau@mips.com>,
	Kevin Mills <kevinm@mips.com>,     Ilie Garbacea <ilie@mips.com>,
	Catherine Moore <clm@codesourcery.com>,
	    Nathan Sidwell <nathan@codesourcery.com>,
	    Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH] MIPS: microMIPS ASE support
Date: Mon, 26 Jul 2010 13:53:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1007261450140.29495@tp.orcam.me.uk> (raw)
In-Reply-To: <20100726132543.GL9110@codesourcery.com>

On Mon, 26 Jul 2010, Nathan Froyd wrote:

> > > Did you actually test this with n64, say with a gcc bootstrap?  Same
> > > comment goes for elfn32-mips.c.
> > > 
> > > Why only do the linker relaxation for elf32-mips.c (o32, o64 & EABI)?
> > > Why not for n32 and n64 too?
> > 
> >  The answer to all the questions is negative.  There is no 64-bit 
> > microMIPS hardware available at the moment.  The best bet might be QEMU -- 
> > NathanF, have you implemented any of the 64-bit instructions in QEMU?  
> 
> I have implemented support for the 64-bit instructions in QEMU.  I
> haven't really tested whether the instruction translation works
> correctly for those instructions.  (It should; there's nothing unusual
> about the codepaths the 64-bit instructions take vs. their 32-bit
> counterparts...but you never know...)

 OK, thanks.  That's a good starting point, but still some low-level
startup files will need to be updated or at least examined for correct
64-bit microMIPS support before we can link executables suitable for
run-time testing such as with the GCC testsuite, let alone a full native 
GCC bootstrap.

  Maciej

  reply	other threads:[~2010-07-26 13:53 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 18:19 [PATCH] MIPS: microMIPS and MCU ASE instruction set support Maciej W. Rozycki
2010-05-23 21:38 ` Richard Sandiford
2010-05-24 22:25   ` Fu, Chao-Ying
2010-05-26 19:47     ` Richard Sandiford
2010-06-01 14:21   ` Maciej W. Rozycki
2010-06-01 14:39     ` Catherine Moore
2010-06-01 22:04     ` Richard Sandiford
2010-06-01 22:47     ` Fu, Chao-Ying
2010-06-05  9:17     ` Richard Sandiford
2010-07-26 10:56   ` [PATCH] MIPS: microMIPS ASE support Maciej W. Rozycki
2010-07-26 13:25     ` Nathan Froyd
2010-07-26 13:53       ` Maciej W. Rozycki [this message]
2010-07-26 19:03     ` Richard Sandiford
2010-12-07  1:13       ` Maciej W. Rozycki
2010-12-12 14:59         ` Richard Sandiford
2010-12-14 13:30           ` Maciej W. Rozycki
2010-12-14 14:51             ` Richard Sandiford
2010-12-16 11:54               ` Maciej W. Rozycki
2010-12-18 10:26                 ` Richard Sandiford
2010-12-14 17:56             ` Joseph S. Myers
2010-12-16 15:28               ` Maciej W. Rozycki
2010-12-17 20:56             ` Fu, Chao-Ying
2010-12-18 10:09               ` Richard Sandiford
2011-01-02 11:36         ` Richard Sandiford
2011-02-21 15:35           ` Maciej W. Rozycki
2011-02-22 20:12             ` Fu, Chao-Ying
2011-02-22 20:19             ` Fu, Chao-Ying
2011-02-24 10:46               ` Maciej W. Rozycki
2011-02-26 11:41                 ` Richard Sandiford
2011-02-28 16:41                   ` Maciej W. Rozycki
2011-02-26  0:00             ` Maciej W. Rozycki
2011-03-13  9:23               ` Richard Sandiford
2011-07-25  7:49                 ` Richard Sandiford
2011-07-26  2:01                   ` Maciej W. Rozycki
2011-07-29  0:58                     ` Maciej W. Rozycki
2011-07-29 11:30                       ` Richard Sandiford
2011-07-29 22:52                         ` Maciej W. Rozycki
2011-02-26 11:36             ` Richard Sandiford
2011-07-26 14:00               ` Maciej W. Rozycki
2010-05-26 20:19 ` [PATCH] MIPS: microMIPS and MCU ASE instruction set support Richard Sandiford
2010-05-27 21:39 ` Richard Sandiford

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=alpine.DEB.1.10.1007261450140.29495@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=binutils@sourceware.org \
    --cc=clm@codesourcery.com \
    --cc=davidlau@mips.com \
    --cc=froydnj@codesourcery.com \
    --cc=fu@mips.com \
    --cc=ilie@mips.com \
    --cc=joseph@codesourcery.com \
    --cc=kevinm@mips.com \
    --cc=nathan@codesourcery.com \
    --cc=rdsandiford@googlemail.com \
    --cc=rich@mips.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).