Here's the coroutine ICE (clang -std=c++17 -fcoroutines-ts):

#define _RESUMABLE_FUNCTIONS_SUPPORTED
#include <winrt/Windows.ApplicationModel.h>

using namespace winrt::Windows::Foundation;
using namespace winrt::Windows::ApplicationModel;

IAsyncOperation<StartupTask> GetApplicationStartupTask()
{
    static auto task = (co_await StartupTask::GetForCurrentPackageAsync()).GetAt(0);
    co_return task;
}

IAsyncOperation<StartupTaskState> GetStartupState()
{
    try
    {
        co_return (co_await GetApplicationStartupTask()).State();
    }
    catch (const winrt::hresult_error &err)
    {
        co_return StartupTaskState::Disabled;
    }
}

Note that I did not even get to the point where linking fails because of the missing intrinsics.

Instruction does not dominate all uses!
  %116 = getelementptr inbounds %"\01?GetStartupState@@YA?AU?$IAsyncOperation@W4StartupTaskState@ApplicationModel@Windows@winrt@@@Foundation@Windows@winrt@@XZ.Frame", %"\01?GetStartupState@@YA?AU?$IAsyncOperation@W4StartupTaskState@ApplicationModel@Windows@winrt@@@Foundation@Windows@winrt@@XZ.Frame"* %15, i32 0, i32 13
  %114 = catchpad within %112 [%rtti.TypeDescriptor25* @"\01??_R0?AUhresult_error@winrt@@@8", i32 8, %"struct.winrt::hresult_error"** %116]
fatal error: error in backend: Broken function found, compilation aborted!

That ICE is not triggered by not naming the catched exception (catch (const winrt::hresult_error &) or just doing catch (…), but then you can't do anything useful with the exception.

I haven't filled an issue for this one, because coroutines are still very experimental, and such a bug will probably not be present in their final release.

There's also another bug, where control flow guard doesn't works when using a string stream.

#include <iostream>
#include <sstream>

int main()
{
    std::wostringstream str;
    str << L"Lorem ipsum dolor sit amet"; // crash here. Investigation lead me to xsputn not being registered somehow in the list of valid function pointers

    std::wcout << str.str();
}

clang-cl /c file.cpp -m32 /guard:cf /MDd
lld-link /guard:cf file.obj

Running the executable will cause a crash because of a control flow guard violation. I did fill an issue for this one: https://bugs.llvm.org/show_bug.cgi?id=39517

Alternative compilers #109

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions