All of lore.kernel.org
 help / color / mirror / Atom feed
From: BAndViG <bandvig@mail.ru>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] OpenRISC 1.3 spec
Date: Thu, 2 May 2019 15:22:56 +0300	[thread overview]
Message-ID: <9933DA48659E43DFAFC830C56C0699A0@BAndViG> (raw)
In-Reply-To: <20190426222242.GH32284@lianli.shorne-pla.net>

> > On Sun, Apr 14, 2019 at 12:41:56PM +0300, BAndViG wrote:
> > > Hi, Stafford, Richard
> > >
> > > > > > I propose:
> > > > > >
> > > > > >   bit-10 - 1 indicates if rd2 is +2
> > > > > >   bit-9  - 1 indicates if ra2 is +2
> > > > > >   bit-8  - 1 indicates if rb2 is +2
> > > > >
> > > > > Thanks.  LGTM.
> >
> > Sorry, it took time, I had visitors at home last week, and I needed to 
> > relearn
> > how cgen worked.
> >
> > This is implemented in binutils now. See my patches here:
> >
> >   - https://github.com/stffrdhrn/binutils-gdb/commits/orfpx64a32-3
> >
> > I have not squashed the commits because it makes it a bit easier for 
> > reviewing
> > what I did to get these flags working.
>
> I have the GCC patches up as well now.
>
>  - https://github.com/stffrdhrn/gcc/commits/or1k-fpu-2
>
> Initial tests look fine.
>
> -Stafford

I've updated mor1kx's FPU stuff with various things. In particular 
OPTION_FTOI_ROUNDING was ported from MAROCCHINO (see description in Readme.md). 
I also created "fp_unordered_cmp" branches in both - mor1kx and 
or1k_marocchino - repos. The branches contain initial implementation of 
unordered comparison as I described in another post of the thread. The 
MAROCCHINO's branch also implements offset for a2, b2 and d2 copied from your 
pull request. I hope verilog models are ready for your upcoming GCC9-spec1.3 
port.

WBR
Andrey 


  reply	other threads:[~2019-05-02 12:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 20:56 [OpenRISC] OpenRISC 1.3 spec Stafford Horne
2019-04-12 21:17 ` Richard Henderson
2019-04-12 21:48   ` Stafford Horne
2019-04-13  8:11     ` Richard Henderson
2019-04-13  8:47       ` Stafford Horne
2019-04-14  9:41         ` BAndViG
2019-04-25 21:17           ` Stafford Horne
2019-04-26 22:22             ` Stafford Horne
2019-05-02 12:22               ` BAndViG [this message]
2019-05-07 15:28             ` Richard Henderson
2019-05-07 21:12               ` Stafford Horne
2019-05-08 18:05                 ` BAndViG
2019-05-09 20:29                   ` Stafford Horne
2019-05-09 21:47                   ` Richard Henderson
2019-05-10  7:56                     ` BAndViG
2019-05-11 10:04                       ` Stafford Horne
2019-05-12 19:58                         ` BAndViG
2019-05-12 23:09                           ` Stafford Horne
2019-06-06 22:11                           ` Stafford Horne
2019-06-15  6:14                             ` Stafford Horne
2019-04-13  8:03 ` Richard Henderson
2019-04-14  6:30   ` Stafford Horne
2019-04-14  6:48     ` Stafford Horne

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=9933DA48659E43DFAFC830C56C0699A0@BAndViG \
    --to=bandvig@mail.ru \
    --cc=openrisc@lists.librecores.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.