| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
PiperOrigin-RevId: 167147239
|
|
|
|
| |
Change-Id: I37ba8d3ade14dc6ab45bca1976776b9cffc98fdc
|
|
|
|
| |
Change-Id: I4facde383f170f12870d22cd3f585b26f77fadb6
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167143657
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167142666
|
|
|
|
|
|
|
| |
Add _'s in proto.transitivedescriptorsets
RELNOTES: none
PiperOrigin-RevId: 167139522
|
|
|
|
|
|
|
|
| |
WORKSPACE file, removing j2objc.WORKSPACE.
Updates J2ObjC version to 2.0.3, which has its own BUILD file.
RELNOTES: J2ObjC version updated to 2.0.3.
PiperOrigin-RevId: 167135399
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 167134267
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 167132537
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the shell command in
ctx.actions.run_shell.command is longer than the
platform's shell's limit, Bazel will dump the
command to a helper shell script and execute that
script in the run_shell action.
Genrules also write a helper script when
genrule.cmd is longer than the shell's limit, and
ctx.actions.run_shell now uses the same machinery.
Fixes https://github.com/bazelbuild/bazel/issues/3589
Change-Id: Ib24dce90182ef69552deb2d400e00ae061537309
PiperOrigin-RevId: 167126560
|
|
|
|
|
|
|
|
|
|
| |
To be true to the layout on disk, one should note the literal directory named `execroot` under the outputBase.
Also fix the indentation on `<workspace-name>/` due to the HTML escapes.
Closes #3520.
PiperOrigin-RevId: 167123497
|
|
|
|
|
|
|
|
|
|
| |
- Move ProfilerInfo into a subpackage (it's not necessary for profiling, just for analyzing a profile).
- Make some fields in Profiler public for ProfileInfo.
- Mark Profiler as ThreadSafe; there's no cyclic dependency here.
This is based on ulfjack's microbazel patch series: https://github.com/ulfjack/bazel/commit/44553fcac0fc876784d8f48c2e577d8c999712de
PiperOrigin-RevId: 167121952
|
|
|
|
|
| |
Change-Id: I41d836bf6ae409f00626a2512d731a6a1adc29c1
RELNOTES: None.
|
|
|
|
|
|
|
| |
Fixes #3525
RELNOTES: None.
PiperOrigin-RevId: 167117507
|
|
|
|
|
| |
RELNOTES: `JavaInfo` is a preferred alias to `java_common.provider`.
PiperOrigin-RevId: 167116971
|
|
|
|
|
|
|
| |
Fixed #556
RELNOTES: None.
PiperOrigin-RevId: 167115644
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167113866
|
|
|
|
| |
PiperOrigin-RevId: 167100515
|
|
|
|
|
|
|
|
|
|
|
| |
The information about whether a converter correctly matches the type of option it is meant to convert strings to is available at compile time. There is no reason to do this check at runtime.
Now, for an option to compile, it will need to have a converter that matches the option's type, taking into account whether the option is expected to accumulate multiple values. If it does not specify its own converter, a matching converter in the Converters.DEFAULT_CONVERTER list must be found, and the default value provided must be parseable by the matching default converter.
Remove tests that were testing failure modes which no longer compile.
RELNOTES: None.
PiperOrigin-RevId: 167092773
|
|
|
|
|
|
|
| |
unwrapped ObjcProvider", after changes made to apple bazel rules to be compatible.
RELNOTES: None.
PiperOrigin-RevId: 167061765
|
|
|
|
|
|
| |
using project support
PiperOrigin-RevId: 167060880
|
|
|
|
| |
PiperOrigin-RevId: 167047092
|
|
|
|
|
|
|
|
| |
This is to avoid having to maintain an almost-equal Java data type once
we start externalizing statistics.
RELNOTES: None.
PiperOrigin-RevId: 167037360
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this CL, if the feature_flags attribute of android_test or
android_binary is not set, no transition takes place when entering that
rule. This means that if it is depended upon by another test or binary, it
will use the enclosing test or binary's flags.
This permits users of feature flags to depend on non-users of feature flags.
The opposite is still not permitted. If a dep sets feature flags, then the
target depending on it must have the exact same feature flags set.
This way, all targets used in an android_test are built the same way, but
it's possible to interoperate with targets which are agnostic to feature
flags.
Note that "not set" is different from "set to the empty dictionary"; the
former reuses the definitions set higher up in the build graph, while the
latter clears all feature flag values and resets them to their defaults.
RELNOTES: None.
PiperOrigin-RevId: 167035122
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167031992
|
|
|
|
|
|
|
| |
SkyframeAwareAction.ExceptionBase.
RELNOTES: None
PiperOrigin-RevId: 167030688
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 167028314
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 167027537
|
|
|
|
|
|
|
| |
the depot.
RELNOTES: None
PiperOrigin-RevId: 167027301
|
|
|
|
|
|
|
|
|
| |
library. Javac9 generates a helper method $closeResource(Throwable,
AutoCloseable) sometimes for try-with-resources. Now we rewrite the call
to call our version to avoid the dependency on AutoCloseable.
RELNOTES: None
PiperOrigin-RevId: 167025276
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167020968
|
|
|
|
|
|
|
|
|
| |
PlatformInfo provider.
Fixes #3631.
Change-Id: I78ed8905e18e3c11c01d6e30512c10491a5ba0f1
PiperOrigin-RevId: 167019469
|
|
|
|
|
|
|
| |
also, AppleConfiguration no longer throws NPE with invalid cpu.
RELNOTES: None.
PiperOrigin-RevId: 167013760
|
|
|
|
| |
PiperOrigin-RevId: 167012083
|
|
|
|
|
|
| |
That is, a c++ toolchain is added, but a Bazel dependency on that toolchain is not.
PiperOrigin-RevId: 167006332
|
|
|
|
|
|
|
|
|
|
|
| |
This makes ControlFlowInfo an ADT handling its own join operation, and combines the list of return statements into that structure. This is less error-prone if a new field is added, and helps simplify the logic in visit(IfStatement).
The invariants regarding the cf field are also clarified: It is "transferred" (in dataflow analysis terminology) from the point before the node to the point after the node by the visit() function. It is also undefined (null) outside of a function definition.
There's a cost to this CL in terms of LOC and maybe even memory allocations, but I suspect that's outweighed by sticking to a known paradigm for flow analysis.
RELNOTES: None
PiperOrigin-RevId: 167005045
|
|
|
|
| |
Change-Id: I6b4c5de8acfb5cacd91f00bc439cd93c05d3a08e
|
|
|
|
|
|
|
|
| |
The code in scheduleLtoBackendAction was attempting to construct the Artifact for a .dwo file when Fission is enabled by getting the related artifact via the ruleContext. This doesn't work for nativedeps files which have a shared _nativedeps/-relative library path, instead of being under the package directory.
Instead, compute the .dwo path the same way we do the ThinLTO imports and index file outputs, using the linkArtifactFactory.
PiperOrigin-RevId: 167002233
|
|
|
|
|
|
|
|
| |
with the new android_binary parameter "proguard_apply_dictionary".
RELNOTES[NEW]: android_binary now supports proguard_apply_dictionary to specify a custom dictionary to use for choosing names to obfuscate classes and members to.
PiperOrigin-RevId: 167000875
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 166993735
|
|
|
|
|
|
|
|
| |
Statement expressions without function calls cannot have an effect
and should be removed, e.g. literals like "['a', 'b']".
RELNOTES: none
PiperOrigin-RevId: 166990862
|
|
|
|
|
|
|
|
| |
Also add a sentence explaining that
"memory-efficient command lines" means Bazel
constructs them lazily.
PiperOrigin-RevId: 166986416
|
|
|
|
|
|
|
|
|
| |
If there is a build failure, don't clobber the terse test summary
by naming all the (usually many) tests that were skipped due to
this failure.
Change-Id: I6daae3efb1594c2b1018f87a50cf63949a34535b
PiperOrigin-RevId: 166983264
|
|
|
|
| |
PiperOrigin-RevId: 166981977
|
|
|
|
| |
PiperOrigin-RevId: 166966182
|
|
|
|
|
|
| |
that is accessible to the c++ rules.
PiperOrigin-RevId: 166934390
|
|
|
|
|
|
|
| |
if --packageForR is not specified.
RELNOTES: None
PiperOrigin-RevId: 166923102
|
|
|
|
|
|
|
| |
while traversing filesets.
RELNOTES: None
PiperOrigin-RevId: 166913262
|
|
|
|
|
|
|
|
|
|
|
| |
Removes some duplicate computation by memoizing the results. Consolidates caching into a single optionDefinition object, instead of having multiple caches that go from the option name to different parts of what defines an option.
Fly-by cleanup of OptionDescription's contents, all contents that are statically defined as part of an option are in OptionDefintion, while expansion data, which depends on the existence of other options, is more clearly stored separately.
Will move the converter-to-option type matching sanity checks to a compile time check in a later change.
RELNOTES: None.
PiperOrigin-RevId: 166912716
|
|
|
|
| |
PiperOrigin-RevId: 166909655
|