programmerjake | lkcl: please don't add important details only by editing comments, no one looking through their emails sees any of the edits: https://bugs.libre-soc.org/page.cgi?id=editcomments.html&bug_id=858&comment_id=9273 | 12:03 |
---|---|---|
lkcl | programmerjake, i was on a call making notes, trying to concentrate on not losing track of the conversation. | 13:01 |
lkcl | and i don't expect people to read all the email notifications, i expect people to go to the bugreport and read all comments in full, so as to retain context | 13:01 |
programmerjake | ok | 13:05 |
programmerjake | well, I, at least, keep up-to-date on the bug tracker by reading my email, not by reading each bug's list of comments everytime I think something might have changed...I highly doubt I'm the only one who does that | 13:07 |
programmerjake | context is easily seen by looking at previous emails | 13:08 |
lkcl | i find the bugzilla email almost impossible to read, it's so badly formatted | 13:08 |
octavius | It's usually the emails that get me to check bugs, cause my client gives me pop ups | 13:08 |
octavius | I have a bit of time before lunch lkcl, what should I get started on? Move the svp64-proposal.tex and try to put the primer and spec in it? | 13:09 |
programmerjake | imho the formatting for comments in emails is fine, the formatting for other field changes is often terrible | 13:10 |
programmerjake | well, ttyl, 5am here | 13:11 |
octavius | gn programmerjake | 13:11 |
programmerjake | thx | 13:11 |
lkcl | eek! :) | 13:11 |
lkcl | night | 13:11 |
lkcl | i'd suggest instead starting putting in a new book into the spec .tex | 13:12 |
lkcl | containing the primer | 13:12 |
octavius | yes, good idea | 13:12 |
lkcl | don't trash the ability to build the primer, though | 13:13 |
octavius | sure | 13:13 |
octavius | lkcl, are you able to compile the spec? | 13:20 |
octavius | Currently I'm getting a 100 errors, but I can't identify the origin file | 13:20 |
octavius | looks like simple_v_spec.toc | 13:21 |
octavius | line 681 has too many brackets {} XD | 13:22 |
lkcl | yes | 13:26 |
lkcl | make clean | 13:26 |
lkcl | your first response on compile errors: make clean | 13:27 |
lkcl | however | 13:27 |
octavius | already done that | 13:27 |
lkcl | bear in mind that "proper" latex build makefiles are fantastically complex | 13:27 |
lkcl | because they involve generating things like a toc | 13:27 |
lkcl | which needs to be re-read in a 2nd pass | 13:28 |
lkcl | which then needs to be read in a 3rd pass | 13:28 |
lkcl | so you *may* need to do "make pdf" *three times* | 13:28 |
lkcl | it's so complex that "proper" latex Makefile creation has a special script to help do it properly | 13:28 |
octavius | 10 times, same problem | 13:28 |
octavius | Is it working for you? | 13:29 |
lkcl | 1 sec | 13:30 |
lkcl | yep all good here | 13:32 |
octavius | git reset, git pulled, cleaned, make pdf again 3 times, not working | 13:33 |
octavius | Also updated openpower-isa repo | 13:33 |
octavius | hmm, I'll try updating my packages I guess | 13:33 |
lkcl | no don't do that | 13:35 |
lkcl | stick with the known-good debian/10 set | 13:36 |
octavius | I meant apt update | 13:36 |
lkcl | yes. don't do that | 13:36 |
octavius | Unfortunately I started it before you mentioned that | 13:36 |
lkcl | aside from anything if you are on debian/testing it will go horribly wrong | 13:36 |
lkcl | stop it right now | 13:37 |
lkcl | kill it before it starts the installs | 13:37 |
lkcl | if it's during the download you're fine | 13:37 |
octavius | Ah ok | 13:37 |
lkcl | you really, *really* must not do a full system upgrade except as a scheduled event | 13:38 |
lkcl | during which time you expect to completely do absolutely nothing but deal with the potential problems that result | 13:38 |
octavius | Ok, well I can't get the tex to compile | 13:38 |
lkcl | i.e. you must terminate all and any work, potentially for several days or weeks | 13:38 |
lkcl | start looking back through git commit history | 13:38 |
lkcl | find the last point at which it worked using either git bisect or do it manually. | 13:39 |
lkcl | i had the same error occur last week, it went away after i did "make clean" | 13:39 |
octavius | I agreed to meet with a friend for lunch, so I'll do some testing once I'm back. | 13:40 |
lkcl | you also need to actually look at the log file rather than treat the log file itself as a "black box" | 13:40 |
lkcl | ok | 13:40 |
octavius | These are the lines I was planning to add: | 13:40 |
octavius | \part{Scalable Vectors Primer} | 13:40 |
octavius | \include{../svp64-primer/summary} | 13:40 |
octavius | speak to you in a bit | 13:40 |
lkcl | i think that would work great. | 13:45 |
lkcl | ok | 13:45 |
octavius | lkcl, tried a commit from 6th Jul (last time I worked on spec), still the same problem of too many brackets {}. Which version of texlive-full are you using? Maybe at some point I installed the testing version | 15:38 |
lkcl | octavius, use a new chroot | 15:41 |
octavius | sure | 15:41 |
lkcl | dpkg -l | grep texlive | 15:42 |
lkcl | ii texlive 2017.20171128-1 | 15:42 |
lkcl | but i seem to recall there's some package needed | 15:42 |
lkcl | temp files get created.... hang on... | 15:42 |
lkcl | rright. i know. do this: | 15:42 |
lkcl | rm *.aux *.out *.toc | 15:43 |
lkcl | you could have inspected the log file and found that out. | 15:44 |
lkcl | took me a while to remember that's what it was. | 15:44 |
octavius | I just wanted to check what your version was. Mine is from 2018, so probably mucked up the packages at some point. Hopefully the new chroot will fix that | 15:45 |
octavius | Ah, removing the temp files worked | 15:46 |
octavius | Perhaps I should add "rm *.aux *.out *.toc" to make clean? | 15:46 |
octavius | Sorry about that | 15:47 |
octavius | Ah you did already | 15:47 |
octavius | Problem I just realised, is that latex doesn't allow including files above the root directory | 15:59 |
octavius | So either the primer dir has to be moved where simple_v_spec.tex is, or a symbolic link to the primer summary has to be added (but that doesn't include the images) | 16:01 |
lkcl | yep move the primer, in its entirety | 16:10 |
lkcl | and remember to update this | 16:11 |
lkcl | openpower/sv/overview.mdwn:![Single-Issue concept](/svp64-primer/img/power_pipelines.svg) | 16:11 |
lkcl | openpower/sv/overview.mdwn:![Multi-Issue with Predicated SIMD back-end ALUs](/svp64-primer/img/sv_multi_issue.svg) | 16:11 |
lkcl | openpower/sv/overview.mdwn:![image](/svp64-primer/img/svp64_regs.svg){ width=40% } | 16:11 |
lkcl | and check pandoc_img.py as well | 16:11 |
lkcl | don't mess about, just move the whole lot into openpower/sv | 16:12 |
octavius | sure | 16:12 |
* lkcl still doing the table | 16:12 | |
octavius | lkcl, moved svp64-primer and added primer to the spec | 16:51 |
octavius | currently it occurs before the Preamble and TOC, probably worth thinking about where to best place it | 16:52 |
lkcl | that should work well | 18:41 |
lkcl | tplaten, the gram headless example should run under iverilog. | 18:42 |
lkcl | make sure to use this though https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=iverilog-install;hb=HEAD | 18:43 |
lkcl | octavius, hmm the preamble needs to come first | 18:47 |
octavius | ok | 18:47 |
lkcl | also hmm adding the summary has broken something | 18:49 |
octavius | Adding references didn't work either | 18:49 |
lkcl | let me see if i can work it out | 18:51 |
lkcl | suspect missing usepackage{}s | 18:56 |
octavius | Ah, hm | 18:56 |
lkcl | got it | 18:57 |
lkcl | committting in 1min... | 18:57 |
lkcl | done | 18:58 |
octavius | Added the acronyms as well | 19:03 |
octavius | Also in the primer, section 1.2.4, where I listed the hybrid workloads (CPU, GPU, VPU, 3D?), I left question mark. Possibly because I didn't know if the point was explained enough | 19:06 |
lkcl | yeah leave out questionmarks like that, it causes lack of confidence | 19:08 |
octavius | sure | 19:08 |
lkcl | acronyms good | 19:09 |
lkcl | acronyms need to go before heading, and without a number. | 19:11 |
lkcl | i know how to do that (use *) | 19:11 |
octavius | Sure. I noticed page 59 (sv register example fig) is stretched | 19:12 |
lkcl | ehhm.... | 19:14 |
lkcl | i did put in a width-scaling somewhere | 19:16 |
octavius | Shall I add a contact section after the summary? | 19:16 |
lkcl | yes. in the preamble | 19:18 |
octavius | will do | 19:18 |
tplaten | I've read that install manual. An its not the first time that I installed and used iverilog, that is maybe ten years ago or so. | 19:25 |
tplaten | I only see ecp5 modules here, but I know that there is an emulation of the ecp5 ddr phy in iverilog | 19:28 |
tplaten | ls shows | 19:28 |
tplaten | crg.py ecp5_crg.py firmware headless headless-ecpix5.py headless-versa-85.py soc.py uartbridge.py | 19:28 |
tplaten | done, installed iverilog | 19:49 |
octavius | lkcl, added the contacts section. Not sure if the description is correct, or if everyone needs to be on there | 19:59 |
octavius | I was thinking konstantinos might be good to add given his experience with svp64 | 20:00 |
lkcl | yes good idea | 21:30 |
octavius | lkcl, I didn't put konstantinos under the Libre-SOC team, is that correct? I seem to remember he works for a different organisation (but I guess we all do to some extent) | 21:45 |
lkcl | his company is Vectorcamp.gr | 21:51 |
octavius | Thanks, added his info | 21:58 |
octavius | Table looks really nice :D | 23:33 |
octavius | lkcl, may be worth to check with david and toshaan, but sections 3.1/3.2 (Other Vector ISAs) maybe a little sarcastic (I don't think it's drastically so, but worth checking) | 23:40 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!