3 ms·
Compilers are a moving target - and you'd be surprised what you can find. Here's one I recently ran into (with a different repro:) https://connect.microsoft.c
by MaulingMonkey 11y ago
Compilers are a moving target - and you'd be surprised what you can find. Here's one I recently ran into (with a different repro:)
https://connect.microsoft.com/VisualStudio/feedback/details/758711/incorrect-expansion-of-line-with-enabled-edit-and-continue-line-var https://connect.microsoft.com/VisualStudio/feedback/details/...
I didn't file a bug as it'd already been reported - although in my case, the trigger was using a logging macro which used __LINE__ from a lambda IIRC. Nothing terribly spectacular.
The last bug I remember reporting was default constructor parameters not instantiating templates correctly. Something like void f(int i = some_template<int>::func()); would fail to generate, and thus link against, some_template<int>::func. f might've needed to be a constructor. Sadly the connect bug is 404 and web.archive.org didn't capture the page. They said they would fix it in VS2008 SP2, but I ended up checking and finding they'd fixed it in SP1.
Even ignoring ICEs, I'd say I probably hit at least one confirmed compiler bug a year minimum when doing regular C++ development.