From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Tobias Platen <tplaten@posteo.de>,
Tobias Platen <hacks2019@platen-software.de>,
Libre-RISCV General Development
<libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] style / commit messages
Date: Fri, 17 Apr 2020 17:38:26 +0100
Message-ID: <CAPweEDwXaPS7ky3WfHncGHokcyFMVzQ3E=sw6eFUFwjE+CH3Rw@mail.gmail.com> (raw)
hi tobias, regarding this commit:
commit f17100d6c435aec47b17acb188272a7e9b3cf67d
Author: Tobias Platen <tplaten@posteo.de>
Date: Fri Apr 17 16:06:25 2020 +0000
add with carry instructions
* the addition of the MUL feature needed to be under a separate commit.
(multiplication doesn't have anything to do with "add with carry instructions")
you'll have to watch out for this in future.
* whitespace was added at the end: this you particularly have to watch out for
with vi. it's why it's specifically in the HDL_workflow.
please therefore can you correct that one.
* spaces and brackets: please try to keep to PEP8 as much as you can
the brackets are redundant in this case (unnecessary) and it's definitely a
style irritation not to have a space between the if and the test.
+ if(cry_out==1):
+ if(result > 0xFFFFFFFF):
please can you correct those.
* if adding some functionality it's critically important to also add a
corresponding
unit test, of at least some basic functionality.
this because if you don't, someone else will have to. the worst outcome is if
you add the functionality and someone *assumes* that a unit test has been
added for it.
i'll assign a bugreport to you to make the necessary corrections.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
reply index
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAPweEDwXaPS7ky3WfHncGHokcyFMVzQ3E=sw6eFUFwjE+CH3Rw@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=hacks2019@platen-software.de \
--cc=libre-riscv-dev@lists.libre-riscv.org \
--cc=tplaten@posteo.de \
/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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git