This is an archive of the discontinued LLVM Phabricator instance.

[clang] Expose -fprofile-use in clang-cl
ClosedPublic

Authored by thakis on Feb 11 2022, 12:10 PM.

Details

Summary

Less typing than -fprofile-instr-use, and means the same thing.

Diff Detail

Event Timeline

thakis created this revision.Feb 11 2022, 12:10 PM
thakis requested review of this revision.Feb 11 2022, 12:10 PM
hans accepted this revision.Feb 11 2022, 1:07 PM

lgtm

This revision is now accepted and ready to land.Feb 11 2022, 1:07 PM
This revision was landed with ongoing or failed builds.Feb 11 2022, 1:16 PM
This revision was automatically updated to reflect the committed changes.
Herald added a project: Restricted Project. · View Herald TranscriptFeb 11 2022, 1:16 PM

Hi,

I think we hit a test failure due to this patch in Fuchsia's Clang canary for Windows. We've had a lot of breakages on Windows today, so this was hidden until 0574b5fc landed.

The failing test is: Clang :: Driver/cl-options.c

The failing bot can be found here: https://luci-milo.appspot.com/ui/p/fuchsia/builders/toolchain.ci/clang-windows-x64/b8822483567668224209/overview

hans added a comment.Feb 14 2022, 5:49 AM

Hi,

I think we hit a test failure due to this patch in Fuchsia's Clang canary for Windows. We've had a lot of breakages on Windows today, so this was hidden until 0574b5fc landed.

The failing test is: Clang :: Driver/cl-options.c

The failing bot can be found here: https://luci-milo.appspot.com/ui/p/fuchsia/builders/toolchain.ci/clang-windows-x64/b8822483567668224209/overview

I can't seem to find the actual error in that output. What's the exact failure you're seeing?

Sorry, that bot is green now as of 437d4e01fe4c057509dff30efd560049ad07bc99, so it looks like it was just bad timing that led me to suspect your commit, since it touched the test file.

I'm not sure why the bots test output is so limited, they usually point to the failing assert or provide the output from lit. But either way, sorry for the trouble.