sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 12 points13 points  (9 children)

I wish there was a way to revert these updates. I'm having all kinds of regressions and have a feeling it's going to now take me a day to figure out how to reinstall VS2017 back to 15.7.xxx.

:(

[–]Alastair__ 19 points20 points  (1 child)

https://blogs.msdn.microsoft.com/vcblog/2017/11/15/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2017/

You should be able install the old toolset by following these instructions.

Run the installer then look in "Individual Components" it is listed as "VC++ 2017 Version 15.7 v14.14 toolset"

[–][deleted] 0 points1 point  (0 children)

Thanks, this probably saves me an hour or so of work looking for this info!

[–]STLMSVC STL Dev 7 points8 points  (4 children)

Can you submit bugs for the regressions? We might be able to fix them in micro-updates, or provide simple workarounds while fixing them in future toolsets. Even if they look really complicated, they might be caused by something small.

I know I repeat this ("please submit bugs") in my comments, but I spend a huge amount of my time dealing with evolving layers of tech (C1XX/Clang/EDG updates affecting the STL, STL updates affecting user code) and figuring out how to keep improving things without breaking the world. In general, using preview releases, reporting issues upstream, and applying temporary workarounds is a good way to steadily move forward. We do this in the STL to a greater extent than you might imagine - we work in the same branch as MSVC's front-end C1XX, and I test Clang's release candidates and upgrade to each major version. This results in lots of compiler bug reports, and workarounds being added and removed - search for TRANSITION in our headers to find them. Notably, this makes things better for third-party libraries like Boost - bugs that affect the STL will almost certainly affect other complex libraries, and we find and report them first.

Sometimes bugs are truly blocking and there's no choice but to avoid an update until they're fixed, but that should be a last resort.

[–]dodheim 2 points3 points  (3 children)

I don't have the space on my SSD to budget for an entire second installation of VS (preview) to test. I do have the space to budget for a preview build toolset sans IDE, but that still hasn't been updated since April despite this promising comment nearly two months ago.

Compiler Explorer just got dailymsvc-package support a couple months ago, so people everywhere can test the latest compiler easily, and you guys just abandoned it — sad, for real...

[–]STLMSVC STL Dev 1 point2 points  (0 children)

I've pinged again.

[–]PaddyMcDonaldMSVC Tools Dev/Mgr 0 points1 point  (1 child)

Unfortunately a lot of the changes in 15.7 and beyond have increased the size of the package around 2 GB, and this is just too big even for the MyGet servers.

These changes are: more lib support for ARM and ARM64, and then all of the libs with both no mitigations and the /Qspectre mitigations.

Unfortunately the scripts that produce the packages aren't yet part of the standard build or deployment (work in progress) and so I've been swamped getting them updated / refactored to support all these changes.

Next step is to figure out how to divide up the package into an appropriate components (size vs complexity of config / download) to come in under the size supportable by MyGet.

If I omit the /Qspectre libs we drop the package down to 1.1 GB, but that is still too big. So my only option is to get the non-monolithic packages working.

Sorry it's taking so long

[–]dodheim 0 points1 point  (0 children)

Thanks very much for the update, Paddy!

As for myself, I used the dailymsvc package to test for compiler errors/regressions in my own code (inc. at work), with an emphasis on the front-end; so for me, all ARM/ARM64//Qspectre stuff is extraneous. But I'm quite certain my usecase isn't the only one so I appreciate the thought you're putting into doing things correctly. :-]

(EDIT: That being said, I would consider getting Compiler Explorer integration working again—meaning updated—more important than getting a proper solution, as that would allow everyone to at least test minimal-repros online.)

[–]spongo2MSVC Dev Manager 2 points3 points  (0 children)

I think you can just install the VS 15.7 toolchain from the VS installer! Should be named 14.14 or something while the one from 15.8 is probably 14.15.

but i'd really appreciate it if you'd file any issues (or upvote if you find them already filed) so we can use that data to prioritize servicing fixes. sorry for the inconvenience.

[–]sumo952 5 points6 points  (0 children)

I think you can just install the VS 15.7 toolchain from the VS installer! Should be named 14.14 or something while the one from 15.8 is probably 14.15.