[LLVMbugs] [Bug 23539] ASan broken on Mac OS X 10.8 after merge with UBsan run-time

[bugzilla-daemon at llvm.org]

https://llvm.org/bugs/show_bug.cgi?id=23539

Nico Weber <nicolasweber at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #14 from Nico Weber <nicolasweber at gmx.de> ---
(In reply to comment #12)
> >Our ASan bots are on 10.7 and will stay there for at least a few more months. (We 
> >don't have any plans for upgrading them at the moment.)
> 
> OS X adoption rates are very high; for example, 55% are already on 10.10. I
> suspect only a small percentage of users are running on < 10.9. Is there a
> reason not to upgrade the buildbots 10.10 or 10.9 in the long term?

This is not true in our experience. When a new OS X version is released, many
initial adoption is pretty fast but many people stay around on their current
version for a long time. (And for some reason 10.6 is very popular, it's often
the 2nd-most popular release after the current one.)

samsonov: I'm trying to look at this now. Doing a build of clang with
MACOSX_DEPLOYMENT_TARGET=10.6 now dies in compiler-rt's cmake with

  Too old OS X version: 10.6

It looks like
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20150622/284048.html
added MACOSX_DEPLOYMENT_TARGET as the default deployment version for
compiler-rt. That's not correct. MACOSX_DEPLOYMENT_TARGET at clang build time
specifies which version of OS X the clang I'm building should run on, not the
version of OS X the binaries produced by that clang should run on.

I need to be able to build a clang that runs on 10.6. The asan'd binaries it
produces can assume 10.7, but the compiler itself needs to be able to run on
10.6, and it needs to be able to produce (non-asan) binaries for 10.6.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20150707/5509aef1/attachment.html>