| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
| |
..until issue #2848 is fixed. In this way, they do not shadow
new breakages on CI.
Change-Id: I95ff1aafc1431cadf387119018dfd2443185e7db
PiperOrigin-RevId: 153574737
|
|
|
|
|
|
|
|
| |
This is the Blaze side of the support for emitting and using minimized bitcode files during the LTO indexing (thin link) step of a ThinLTO build. The llvm support has already been released to stable, and this needs to be submitted after the companion Crosstool support (unknown commit, will send for review once this larger part is reviewed).
This enables large applications successfully build using ThinLTO and -g, otherwise the bitcode files that are input to the LTO indexing step are huge and the maximum input size is exceeded.
PiperOrigin-RevId: 153549687
|
|
|
|
| |
PiperOrigin-RevId: 153545346
|
|
|
|
| |
PiperOrigin-RevId: 153531483
|
|
|
|
|
|
|
|
| |
If minimum_os is unspecified on an apple_binary target and ios_multi_cpus is not set, no
apple_binary configuration transition is made.
RELNOTES: None.
PiperOrigin-RevId: 153529598
|
|
|
|
|
|
|
| |
of xctest apps are seen by ios_test
RELNOTES: None.
PiperOrigin-RevId: 153529262
|
|
|
|
|
|
|
|
| |
restrictions.
Prevent the old category strings "undocumented," "hidden," or "internal" from being used as categories, to prevent developers from relying on deprecated behavior.
PiperOrigin-RevId: 153525499
|
|
|
|
|
|
| |
docker_build.
PiperOrigin-RevId: 153508081
|
|
|
|
|
|
|
|
|
|
| |
The key change is to eliminate the need to transition from the data to the target configuration by relying on out-of-band configuration state. Specifically, the old model drops LIPO options from the data configuration. In the cases when we have to switch back (i.e. TARGET_CONFIG_FOR_LIPO), those options have to get re-injected somehow. Static configurations achieve this with the global configuration transitions table. But dynamic configs have no comparable source (and they consciously eschew global state).
This cl changes the model to *keep* LIPO settings in the data config, then use a new "enableOrDisable" flag to determine whether or not to actually use them. With this model, the data -> target transition is now as simple as toggling that flag.
This change doesn't actually add dynamic config LIPO support. It's doing enough as it is, and we need to make sure it doesn't break existing LIPO semantics. Dynamic support will come as a followup.
PiperOrigin-RevId: 153504240
|
|
|
|
|
|
| |
#2147
PiperOrigin-RevId: 153494286
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/2743.
RELNOTES: android_library exports_manifest now defaults to True.
PiperOrigin-RevId: 153493900
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153489730
|
|
|
|
|
|
|
|
|
|
| |
This is already fixed in the CachedLocalSpawnRunner, with tests there, which
will replace RemoteSpawnStrategy in the near future. For now, I'd like to get
this in in time for 0.5.0 to get test caching working.
Fixes #1413.
PiperOrigin-RevId: 153486592
|
|
|
|
| |
PiperOrigin-RevId: 153485708
|
|
|
|
| |
PiperOrigin-RevId: 153474001
|
|
|
|
| |
PiperOrigin-RevId: 153473961
|
|
|
|
|
|
|
| |
This type is no longer used and has removed from bazel.
RELNOTES: None
PiperOrigin-RevId: 153471066
|
|
|
|
|
|
| |
All genjar actions have very short command lines.
PiperOrigin-RevId: 153468708
|
|
|
|
|
|
|
| |
They were added in https://github.com/bazelbuild/bazel/commit/3a5d3db6436bbaf5351da9ea9c19a41ae7c95ca9 by Yours Truly.
RELNOTES: None.
PiperOrigin-RevId: 153468590
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 1cd2096284959ead26687d1d58b695d2abffb8e2.
That commit tried to find a more suitable python binary by
following symlinks. That, however, is not necessary, as
our follow-up infrastructure can call symbolic links and
our tests os.path.isfile(path) and os.access(path, os.X_OK)
follow symbolic links as well.
Fixes #2836.
Change-Id: If37589622d141265577eb3872f68342ae1c263dc
PiperOrigin-RevId: 153461118
|
|
|
|
|
|
|
|
|
| |
It has been disabled in https://github.com/bazelbuild/bazel/commit/bce889840f91f14c05418d960984bcf1a5f59411 and in https://github.com/bazelbuild/bazel/commit/21fb8cac60c36cb527d6131ab0092bcdf138d99a and then was not re-enabled.
Also update src/java_tools/junitrunner/java/com/google/testing/coverage/BUILD to which I accidentally submitted a change directly to our OSS repository.
RELNOTES: None.
PiperOrigin-RevId: 153460778
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke //src/test/shell/bazel:cc_inc_library_test on darwin
see http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=darwin-x86_64/704/console
*** Original change description ***
Basic open-source crosstool to support targetting apple platform types.
RELNOTES: None.
PiperOrigin-RevId: 153460334
|
|
|
|
|
|
|
|
|
|
| |
Only write a cache entry when the spawn executed successfully, and with a 0
exit code. In the test, we only check that uploadFileContents is called exactly
twice.
Progress on #1413.
PiperOrigin-RevId: 153458240
|
|
|
|
|
|
|
|
|
| |
Reduce spaghetti code by exposing the parser's OptionsData as package-private, rather than exposing individual methods ad hoc between OptionsParser and OptionsParserImpl.
Also change some calls from static constructors to diamond syntax.
RELNOTES: None
PiperOrigin-RevId: 153457442
|
|
|
|
| |
Change-Id: I468ab58151a6e62fa9d5d640142c38cd8886737b
|
|
|
|
|
|
|
|
| |
This is a prerequisite for Google to use it; there's no consistent logging
strategy yet, but Google internally requires logging, and it needs to be
somewhat backwards compatible.
PiperOrigin-RevId: 153454160
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153449924
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Add /Z7 as compiler flag in CROSSTOOL, this causes full debugging
infomation built into object files, no PDB file is generated.
2. Add /DEBUG as linker flag so that a PDB file will be generated for
executable or dll.
* /DEBUG:FULL for dbg mode. the full PDB can be used to debug the
executable when no other build products are available, such as
when the executable is deployed.
* /DEBUG:FASTLINK for fastbuild mode. object files are still needed
when debugging the executable, but linking speed can be two to four
times faster that full PDB generation.
* No option is added for opt mode.
More detailed info: https://msdn.microsoft.com/en-us/library/xe4t6fc1.aspx
3. Add an empty feature in MSVC CROSSTOOL to tell Bazel we need PDB file
4. Add PDB file artifact in an output named pdb_file of cc_binary,
then you can build the pdb file by bazel build //foo/bar:bin --output_groups=pdb_file
5. Add test for PDB file generation
Change-Id: Ia5096470187ebca72f2c804f32d5b723f40c0b85
PiperOrigin-RevId: 153449059
|
|
|
|
| |
PiperOrigin-RevId: 153444516
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It appears that jarjar is not actually used except for renaming classes
in the coverage collecting Java test runner as verified by
`find . -name BUILD | xargs grep jarjar`
Yak shaving for #2820.
This is necessary because the current version of jarjar does not work
with Java 8 classes because it embeds a version of ASM that doesn't
support that yet.
Change-Id: I6ac59b84bbbc1e85fe8e7f4f4876b98fc6129df0
|
|
|
|
|
|
|
|
|
| |
This is necessary for vendoring jarjar, which is in turn necessary to
get Java coverage collection to work again.
Yak shaving for #2820.
Change-Id: Idfd45e7322e0763fd316a4f67b1a048c93bf54ba
|
|
|
|
| |
PiperOrigin-RevId: 153403092
|
|
|
|
|
|
|
|
|
| |
These are two different concepts. Do not remove category overload compatibility in this CL, to keep this change limited to converting the current uses of category.
With some flyby formatting fixes on affected OptionsBases.
RELNOTES: None.
PiperOrigin-RevId: 153390002
|
|
|
|
|
|
|
| |
This lets us easily get all options classes of a parser, or all fields of those options classes, in a deterministic way.
RELNOTES: None
PiperOrigin-RevId: 153376699
|
|
|
|
|
|
|
| |
message.
RELNOTES: None.
PiperOrigin-RevId: 153372617
|
|
|
|
|
|
|
|
| |
This prevents having to parse the category, and allows the category to potentially be used in the future for information about all options, included undocumented, hidden, or internal options.
Also rename DocumentationLevel to OptionUsageRestrictions, since INTERNAL was not really documentation related.
PiperOrigin-RevId: 153367769
|
|
|
|
|
|
|
|
|
| |
repositories.
Fixes https://github.com/bazelbuild/bazel/issues/2830
RELNOTES: None
PiperOrigin-RevId: 153367521
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
broken tests
*** Original change description ***
Init absent action configs for CppCompile actions
So far only link actions were initialized in CppLinkActionConfigs. This cl
changes this class to also initialize CppCompile actions. This is needed for
our ongoing work removing hard-coded flags from Bazel and moving them into
Crosstool.
RELNOTES: None.
PiperOrigin-RevId: 153366563
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153360877
|
|
|
|
|
|
|
|
|
|
|
|
| |
The logic is already in Bazel but wasn't available to build rules.
This change makes it available, but still requires data binding's
{build|run}time libraries to be checked into appropriate depot
spots for everything to work.
Followup changes will make those libraries easily available.
Issue: #2694
PiperOrigin-RevId: 153359861
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
breaks tests
*** Original change description ***
Extract --sysroot flag from bazel and move it into crosstool
This is an encore of https://github.com/bazelbuild/bazel/commit/6127358c1799d8d83cebbd499edac89f869df41b .
RELNOTES: None.
PiperOrigin-RevId: 153351147
|
|
|
|
| |
PiperOrigin-RevId: 153349925
|
|
|
|
|
|
|
|
|
|
|
| |
OptionsParserTest is kind of massive. This CL splits off tests that only concern IsolatedOptionsData. For example, tests that deal with malformed option specifications, but not string parsing, would go here.
A followup CL will add tests of IsolatedOptionsData's accessor methods.
Also added a unit test for the warning added by https://github.com/bazelbuild/bazel/commit/e11775c2394fc48ac7fe5b632b47ae952dd552b4.
RELNOTES: None
PiperOrigin-RevId: 153346363
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks internal tests that use nonstandard crosstools
*** Original change description ***
Make C++ archiving use action_configs instead of hardcoded flags
RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag.
PiperOrigin-RevId: 153344597
|
|
|
|
|
|
|
|
| |
There's no reason an expansion flag should not expand to multiple values for a repeatable flag (a flag with allowMultiple set to true.) If this expansion flag is set in a SetValue policy, group its repeatable subflags into a single SetValue per subflag.
For an overridable SetValue policy on an expansion, any repeatable flag that it expands to should append its value, and not override the user's original values.
PiperOrigin-RevId: 153233784
|
|
|
|
|
| |
RELNOTES: n/a
PiperOrigin-RevId: 153230139
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 153223511
|
|
|
|
|
|
|
|
|
| |
Canonicalize-flags will provide the expanded and filtered version of the policy passed to it as a command argument if also passed the command arg --canonicalize_policy. This is the version that would be actually applied to the command line in another command.
In this mode, it will not also print out the interpretation of the flags passed after "--", so to get both outputs, it will have to be run twice. This was to keep the output clean and easy to parse.
RELNOTES: new option for bazel canonicalize-flags, --canonicalize_policy
PiperOrigin-RevId: 153215518
|
|
|
|
| |
PiperOrigin-RevId: 153202296
|
|
|
|
|
|
|
| |
Refactoring: Wrapped the SymbolLoader and SymbolWriter in a single class.
RELNOTES: None
PiperOrigin-RevId: 153194543
|