| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 171013687
|
|
|
|
|
|
| |
This is a trivial change with a large file footprint.
PiperOrigin-RevId: 169169864
|
|
|
|
|
|
| |
This is necessary for the upcoming Skylark implementation of param files.
PiperOrigin-RevId: 168744486
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allowing add(Object) is too loose and can easily lead to programmer mistakes.
Because of type erasure, we can't use the same overload name for (eg.) add(NestedSet<String>) and add(NestedSet<Artifact>). The API is overhauled to use the same terms everywhere, eg. "add", "addPaths", "addExecPaths". This is similar to how it used to be a few CLs ago.
The API is overhauled to make sure it's consistent for all types. While tedious, the facade methods immediately dispatch to internal helpers, so implementation wise it's not too heavy.
While large, this CL is almost entirely an automated refactor.
PiperOrigin-RevId: 165358287
|
|
|
|
|
|
|
|
|
| |
This enforces certain memory-efficient patterns. For deliberate use of dynamic strings, explicitly named overloads are introduced, with javadoc that guides the programmer into making the right choice.
This CL is a memory no-op on benchmarks, but it tries to prevent backslide by making sure programmers make conscious choices when they construct their command lines.
RELNOTES: None
PiperOrigin-RevId: 165185997
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 163343931
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel_apple_rules
*** Original change description ***
Make all WithLegacySkylarkName providers declared providers.
RELNOTES: None
PiperOrigin-RevId: 163054821
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 163042362
|
|
|
|
|
|
| |
option on CompilationSupport. In the process correctly respect whether to use the pch file under crosstool compilation mode.
PiperOrigin-RevId: 161156717
|
|
|
|
|
|
|
| |
With a few manual fixes for readability.
RELNOTES: None.
PiperOrigin-RevId: 160582556
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 157857216
|
|
|
|
|
|
| |
to CompilationSupport to clean up that expanding API.
PiperOrigin-RevId: 154077775
|
|
|
|
| |
PiperOrigin-RevId: 152169986
|
|
|
|
|
|
|
|
|
|
|
|
| |
'create' method.
This paves the way for changing PathFragment to e.g. an abstract class with multiple subclasses. This way we can split out the windows-specific stuff into one of these concrete classes, making the code more readable and also saving memory (since the shallow heap size of the NonWindowsPathFragment subclass will hopefully be smaller than that of the current PathFragment).
This also lets us pursue gc churn optimizations. We can now do interning in PathFragment#create and can also get rid of unnecessary intermediate PathFragment allocations.
RELNOTES: None
PiperOrigin-RevId: 152145768
|
|
|
|
|
|
|
|
| |
path. In the process, rename and replace the incorrectly named ObjcCommon.Builder#addUserHeaderSearchPaths
--
PiperOrigin-RevId: 147038434
MOS_MIGRATED_REVID=147038434
|
|
|
|
|
|
|
|
| |
objc_proto_library and objc_import rules.
--
PiperOrigin-RevId: 146410669
MOS_MIGRATED_REVID=146410669
|
|
|
|
|
|
|
|
|
|
| |
--experimental_objc_library and --experimental_objc_use_crosstool_for_binary.
This flag will allow testing of the complete (compilation and linking) rollout
of the objc crosstool.
--
PiperOrigin-RevId: 144864301
MOS_MIGRATED_REVID=144864301
|
|
|
|
|
|
|
|
|
|
| |
--experimental_transparent_compression flag
Also add test to ensure lazy strings aren't forced.
--
PiperOrigin-RevId: 142496520
MOS_MIGRATED_REVID=142496520
|
|
|
|
|
|
|
|
|
|
| |
attribute
This prevents duplicate symbol errors for objects that would otherwise be linked both in the application binary and a dylib the binary is linked against.
--
PiperOrigin-RevId: 141478238
MOS_MIGRATED_REVID=141478238
|
|
|
|
|
|
|
| |
CompilationSupport.
--
MOS_MIGRATED_REVID=138185198
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133989926
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133634326
|
|
|
|
|
|
|
|
|
| |
proto target. Removes module map generation for binary targets.
Filter well known protos from ProtocolBuffers2 as there may be some proto_library targets including them.
--
MOS_MIGRATED_REVID=131093115
|
|
|
|
|
|
|
| |
much smaller. This adds more granularity and helps prevent excessive compilation by minimizing the number of inputs for each action.
--
MOS_MIGRATED_REVID=130359288
|
|
first step into integrating the grouping behavior for proto targets using the new library.
There's no change in functionality, only restructuring of code.
--
MOS_MIGRATED_REVID=129903574
|