Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

coverage flags are broken with LLVM 3.5 on master #7779

Closed
jakebolewski opened this issue Jul 29, 2014 · 4 comments
Closed

coverage flags are broken with LLVM 3.5 on master #7779

jakebolewski opened this issue Jul 29, 2014 · 4 comments
Labels
test This change adds or pertains to unit tests

Comments

@jakebolewski
Copy link
Member

I'm not getting any valid results when using the svn version of LLVM and the latest prerelease build. Malloc line counts are there, just all allocation counts are zero.

Edit: It looks like code coverage is not working either.
@jakebolewski jakebolewski changed the title --track-allocation flag seems to be broken with LLVM 3.5 on master coverage flags are broken with LLVM 3.5 on master Jul 29, 2014
@timholy
Copy link
Member

timholy commented Jul 29, 2014

I confess to being clueless about whether we are shipping anything for 0.3 with this version of LLVM.

@jakebolewski
Copy link
Member Author

Nope, LLVM 3.5 will be the default in 0.4.

@timholy
Copy link
Member

timholy commented Jul 29, 2014

That was my impression too. No hurry, then.

@ihnorton ihnorton added the test This change adds or pertains to unit tests label Jan 15, 2015
@vtjnash vtjnash mentioned this issue Jan 15, 2015
Closed
19 tasks
@vtjnash
Copy link
Member

vtjnash commented Jan 30, 2015

whoops, just saw this one, and it was an easy one. keep 'um coming. (linking from the llvm35 issue definitely helps)

@simonster simonster mentioned this issue Jan 30, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
test This change adds or pertains to unit tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ihnorton @vtjnash @jakebolewski @timholy