<OmniMancer>
I believe it is not quite like REP in x86 since x86 will trap if it is used in a non supported place, it just has a bunch of unrelated places it can occur
<sorear>
I just read a 8086 manual and a recent-ish intel SDM (2016) because I was curious and neither of them commits to it trapping :/
<omnitechnomancer>
Probably so they can add semantics, but neither of them will say it does nothing either right?
<whitequark>
:/
<omnitechnomancer>
I don't really care what the processor does with them just if I need to explain the prefixed forms of every instruction to the disassembler
<cr1901_modern>
I wouldn't be surprised one bit if in 8086-world the semantics for using "REP" in an unsupported position is "don't do that". Kinda like "pop cs"
<omnitechnomancer>
Indeed, I suppose boneless is also not aiming for binary compatibility forever across a whole processor family?
<sorear>
Repeat prefixes (F2H, F3H) cause an instruction to be repeated for each element of a string. Use these prefixes only with string and I/O instructions (MOVS, CMPS, SCAS, LODS, STOS, INS, and OUTS). Use of repeat prefixes and/or undefined opcodes with other Intel 64 or IA-32 instructions is reserved; such use may cause unpredictable behavior.
<sorear>
Some instructions may use F2H,F3H as a mandatory prefix to express distinct functionality
<sorear>
there's also no clear mention of what happens if you use REPNE for other than SCAS/CMPS
<sorear>
I suspect that for Intel historically a precise specification of the instruction set is a liability
<cr1901_modern>
You wouldn't be able to distinguish 8086 up to 486 if it weren't for some small semantic changes :D!
mumptai_ has joined ##openfpga
mumptai has quit [Ping timeout: 265 seconds]
<omnitechnomancer>
Well the performance would differ if nothing else
Bike has quit [Quit: leaving]
Degi has quit [Ping timeout: 256 seconds]
Degi has joined ##openfpga
<awygle>
is there a pic-style minimum-area soft core that people use?
<awygle>
thinking an accumulator-type architecture
<awygle>
also a) why is there a toaru majutsu no index-style version of the boneless logo b) does it say "a certain boneless CPU" c) why does it have a III when afaict boneless is currently rev II?
<pie_>
awygle: 4) you gotta link it man we gotta seee
<cr1901_modern>
I believe it is time for you to stop posting.
<azonenberg>
awygle: boneless-chan, lol
<azonenberg>
you HAVE seen the far side cartoon of the boneless chicken ranch, right?
Asu has joined ##openfpga
mumptai_ has quit [Read error: Connection reset by peer]
mumptai_ has joined ##openfpga
mkru has joined ##openfpga
<gruetzkopf>
remember "rep ret"
Bike has joined ##openfpga
pointfree has quit [Ping timeout: 260 seconds]
pointfree has joined ##openfpga
Lord_Nightmare has quit [Ping timeout: 258 seconds]
Lord_Nightmare has joined ##openfpga
mkru has quit [Remote host closed the connection]
Zorix has quit [Ping timeout: 240 seconds]
Zorix has joined ##openfpga
renze has quit [Ping timeout: 244 seconds]
renze has joined ##openfpga
jfcaron has joined ##openfpga
genii has joined ##openfpga
Stary- is now known as Stary
X-Scale` has joined ##openfpga
X-Scale has quit [Ping timeout: 256 seconds]
X-Scale` is now known as X-Scale
OmniMancer has quit [Quit: Leaving.]
emeb has joined ##openfpga
<emeb>
I realize this is slightly OT but can anyone confirm that Xilinx Vivado 2019 and later no longer allow a free unlimited duration install for low-end products via WebPack or equivalent?
<emeb>
I just went to the trouble of installing 2019.2 and when it took me to the Xilinx site to get a license it seems that the only things available were 30-day trials.
<tnt>
AFAIK the webpack is still a thing ...
<emeb>
It seems to work for older versions
<emeb>
I can still run 2017.x Vivado with a free license that doesn't time out.
<emeb>
But if the newer stuff allows that they've hidden the options to do so pretty well.