Page MenuHomeFreeBSD

Exclude assembly files from LLVM IR Builds
AbandonedPublic

Authored by bkidney_briankidney.ca on Mar 2 2017, 2:05 AM.
Tags
None
Referenced Files
F152344660: D9853.id25856.diff
Tue, Apr 14, 8:07 AM
Unknown Object (File)
Sat, Apr 11, 2:48 PM
Unknown Object (File)
Fri, Apr 10, 7:22 AM
Unknown Object (File)
Tue, Apr 7, 8:49 AM
Unknown Object (File)
Mon, Apr 6, 11:03 AM
Unknown Object (File)
Sat, Apr 4, 3:15 PM
Unknown Object (File)
Sat, Mar 28, 3:27 PM
Unknown Object (File)
Sat, Mar 28, 1:08 AM
Subscribers

Details

Reviewers
jonathan
bdrewery
Summary

Excludes machine dependant code (*.S) that were causing builds to fail.

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 7835
Build 7979: arc lint + arc unit

Event Timeline

bkidney_briankidney.ca retitled this revision from to Exclude assembly files from LLVM IR Builds.
bkidney_briankidney.ca updated this object.
bkidney_briankidney.ca edited the test plan for this revision. (Show Details)
share/mk/bsd.lib.mk
203

How does this interact with STATICOBJS? I think that only gets used in libpam, but it would be worth checking whether we need to do the same thing there.

  • Adds filtering to STATICOBJS for BCOJBS and LLOBJS list creation.

Roling back last commit.

As I hit enter I realized that though it is safe to filer the STATICOBJS list it doesn't make sense. STATICOBJS list only include .o files.

share/mk/bsd.lib.mk
203

STATICOBJS is initialized in the Makefile for individual builds (libc, libc++, libpam, and libgcc). In this build file it is only a list of ".o" files and we do not know there origin to determine if they should be filtered.