From: Staf Verhaegen <staf@fibraservi.eu>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: Re: [libre-riscv-dev] Introduction and Questions
Date: Sat, 16 May 2020 11:47:27 +0200
Message-ID: <ff622773af59baea76786e85e28649a3941e69e5.camel@fibraservi.eu> (raw)
In-Reply-To: <CAEoCstS+xz_K6AYNkq-nXB=e7B4FqdC5nzdOXRaNyiqNOuCC7w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 686 bytes --]
Jeremy Singher schreef op vr 15-05-2020 om 16:49 [-0700]:
>
> >
> > sigh over a year ago i understood this enough to be able to answer.
> > what we will have to do is simply ignore the optimisation opportunity.
>
>
> Hmmm, ignoring WAW will significantly limit the ability of the core to
> exploit ILP, which is one of the fundamental reasons for going OOO.
I've wondered about this myself. Can you give concrete example of where
not supporting a WAW hazard blocks ILP ?
I am asking because just a WAW hazard could be easily avoided by a good
peep hole optimizer in software because it would see that the output of
the first write is never used.
greets,
Staf.
[-- Attachment #2: Type: text/plain, Size: 177 bytes --]
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 18:24 Jeremy Singher
2020-05-15 18:45 ` Yehowshua
2020-05-15 19:15 ` Jeremy Singher
2020-05-15 19:20 ` Yehowshua
2020-05-15 19:24 ` Yehowshua
2020-05-15 19:33 ` Yehowshua
2020-05-15 20:11 ` Luke Kenneth Casson Leighton
2020-05-15 20:50 ` Jeremy Singher
2020-05-15 21:03 ` Yehowshua
2020-05-15 21:19 ` Jacob Lifshay
2020-05-15 21:55 ` Luke Kenneth Casson Leighton
2020-05-15 21:53 ` Luke Kenneth Casson Leighton
2020-05-15 22:15 ` Jeremy Singher
2020-05-15 22:29 ` Yehowshua
2020-05-15 22:51 ` Luke Kenneth Casson Leighton
2020-05-15 22:47 ` Luke Kenneth Casson Leighton
2020-05-15 23:49 ` Jeremy Singher
2020-05-16 0:40 ` Luke Kenneth Casson Leighton
2020-05-16 9:47 ` Staf Verhaegen [this message]
2020-05-16 11:30 ` Staf Verhaegen
2020-05-16 12:30 ` Luke Kenneth Casson Leighton
2020-05-16 20:34 ` Jeremy Singher
2020-05-16 21:42 ` Luke Kenneth Casson Leighton
2020-05-16 9:43 ` Staf Verhaegen
2020-05-16 12:14 ` Luke Kenneth Casson Leighton
2020-05-15 18:47 ` Yehowshua
2020-05-16 12:11 ` Luke Kenneth Casson Leighton
-- strict thread matches above, loose matches on Subject: below --
2020-05-15 6:50 Jeremy Singher
2020-06-06 22:47 ` Yehowshua
2020-06-06 22:48 ` Luke Kenneth Casson Leighton
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=ff622773af59baea76786e85e28649a3941e69e5.camel@fibraservi.eu \
--to=staf@fibraservi.eu \
--cc=libre-riscv-dev@lists.libre-riscv.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
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