Michael Popoloski

It looks like this is caused by having the compiler pdb named the same as the linker pdb (two separate output files, one specified with /Fd for the compiler and...

Oops, sorry about this. I should have tested with VS 2015 before committing. Maybe we should just gate this change behind a version check? I was under the understanding that...

Note that a full rebuild in 2017 should always cause the issue to occur. Normal builds might not. On Mar 11, 2017 9:13 PM, "Mike Popoloski" wrote: > Oops, sorry...

So I think my fix works as long as we exclude it for *static library* projects (which is what was breaking things for @beevik ). The fix you just checked...

It works correctly in my repo right? I see that you've changed the code, so I can only assume you've introduced a bug or aren't handling some part of the...

It's certainly possibly that there's a bug in my interpreter. Other things to check though: are there embedded bitmaps at this strike size? Also remember that GDI has 3x horizontal...

I started looking at this and had some questions about the model. Normally when using VPI the model is entirely the instantiated design, so each "module" is actually an instantiated...

The instances in topModules does not seem to contain all of the information in the module though. For example, I don't seen any vpiProcesses and associated statements in there, or...

Ah, ok. Is there documentation of what gets elaborated and what does not? It's pretty confusing as-is. I see that continuous assigns don't show up in topModules, unless they're in...

Thanks, that makes sense. Have you thought about alternative models that would more compactly represent the elaborated design? It seems like if you require all downstream consumers to reimplement all...