-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Iztok,
>> Vendor project files are needed for running the tools in both GUI >> or batch CLI mode. The GUI can be avoided, the mouse click >> sequence is usually replace by a TCL script. Almost everything >> the tool offers can be done without a GUI, but project files are >> still needed. In minsoc I believe these are being generated from a language agnostic list. >> There was a point in GIT history which worked well, but I am not >> sure if synthesis works right now. I will retry and fix issues >> later this week. Cool! When you do that, can you take a look at my branch. If you think it still needs more work, you could git cherry-pick any commits you are happy with, and toss the rest back to me for more polish. >> The code in lib files is publicly available, so it is not a big >> (time sensitive) issue, but removing it altogether form Git blobs >> would make sense. I can do it when I get back to simulating top >> level. Never done it, but the web is full of instructions. So the basic formula is $ git rebase -i <some revision before the problem> If the problem is caused by a whole commit you can just remove it from the list, close the editor, and git will rewrite the branch with the commit removed. If the problem is part of a larger commit, set the action from "pick" to "edit", or "e", then close the editor. Git will now drop you at the point right after the commit to edit. "git rm" the files you want to remove, then when you are happy, do a "git commit --amend" to modify the commit. Then finish the rebase with "git rebase --continue". In your case there shouldn't be any merge conflicts to deal with. If you screw up, you can always find the ID of the old commits lying around in history using git reflog. In this case simply attach a branch to it and try again with that. Then when everything is done, push the branch to github. It will complain because of the divergence you just created, so you will need to push it with "git push -f ...." > >> `include is executed before parsing, so it is not clear what the >> tool complaint is about, maybe the path to the include file was >> not specified. Try putting a syntax error inside, to see if the >> file was actually read. If the issue persists it might be a >> language support issue triggered in combination with local >> parameters. Cool! I'll take a look. >> There is actually an integrated function $clog2() in Verilog >> 2001, but it is not supported by Xilinx ISE (it is in most other >> tools), therefore I copied the recommended workaround from Xilinx >> support pages. Anyway, I can look into it this week. Yes, I'm surprised $clog2 only made it into Verilog 2001. I mean it's a pretty fundamental use case: Calculate how many bits I need to store this maximum value. I would have thought it would be have been introduced earlier and much more widely. Joel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRpHHzAAoJEIsWlGmq62IgImkH/RuCng/v1koFxox9ExNsY8ou z8klY1DvWxwqVGiwgfClh4VhnRA4LWqJ1d2zSePpHX16D2KluTWCd92W8KnoO6y9 KVrfW0Xuz52o3EQ9qTtECnhE/iJsn2bQcvYB3NJXxTPB48DHH5nrIQbniy4eXNcE 9tLTJXIhSOAUorPl57Gs6OPM0OfsL5xppnFxn4lGsW5Z5/VG4BzS/GmIxkxTMzzL LYTSGH+qoH+Ah/ICe2pmZaoR49d7fCOyQFLF1Kv10AihqxiH4C7GfyIxWOYJ/omN OpdIoIZ2bW0m5IoohLVx3NfIWuL9/waAy17mv9qPe/E+hNra8serJG2rPg7Jcnc= =kc0m -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
