lkml.org 
[lkml]   [2017]   [Jun]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 13/17] RISC-V: Add include subdirectory
    Hi Dan,

    On Tue, Jun 27, 2017 at 12:07:20AM +0000, Daniel Lustig wrote:
    > > > https://github.com/riscv/riscv-isa-manual/releases/download/riscv-user
    > > > -2.2/riscv-spec-v2.2.pdf
    > >
    > > That's the most up to date spec.
    >
    > Yes, that's the most up to date public spec. Internally, the RISC-V memory
    > model task group has been working on fixing the memory model spec for the
    > past couple of months now. We're aiming to release it for public review
    > well before the end of the year. Hopefully in the coming weeks even.

    Excellent, cheers for the update.

    > > > which, on the one hand is reassuring (because ignoring dependency
    > > > ordering is plain broken), but on the other it doesn't go quite far
    > > > enough in defining exactly what constitutes a "syntactic data
    > > > dependency". The cumulativity of your fences also needs defining,
    > > > because I think this was up in the air at some point and the document
    > > > above doesn't seem to tackle it (it doesn't seem to describe what
    > > > constitutes being a memory of the predecessor or successor sets)
    >
    > That will all covered in the new spec.
    >
    > > > P.S. You should also totally get your architects to write a formal
    > > > model ;)
    >
    > Also in progress :)

    3/3 :)

    > Were there any more specific questions I can answer in the meantime? Or
    > any specific concern you'd like to point me to?

    Nothing specific, but we won't be able to review the
    memory-ordering/atomics/locking parts of this patch series until we have
    a spec.

    Will

    \
     
     \ /
      Last update: 2017-06-27 10:50    [W:6.943 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site