Simonas Kazlauskas b995dc944c No branch protection metadata unless enabled ... Even if we emit metadata disabling branch protection, this metadata may conflict with other modules (e.g. during LTO) that have different branch protection metadata set. This is an unstable flag and feature, so ideally the flag not being specified should act as if the feature wasn't implemented in the first place. Additionally this PR also ensures we emit an error if `-Zbranch-protection` is set on targets other than the supported aarch64. For now the error is being output from codegen, but ideally it should be moved to earlier in the pipeline before stabilization.		2022-02-19 17:31:40 +02:00
..
cgu_reuse_tracker.rs	Make Diagnostic::span_fatal unconditionally raise an error	2021-05-08 23:12:04 -04:00
code_stats.rs	mv compiler to compiler/	2020-08-30 18:45:07 +03:00
config.rs	Rollup merge of #93915 - Urgau:rfc-3013, r=petrochenkov	2022-02-18 23:23:10 +01:00
cstore.rs	Import SourceFiles from crate before decoding foreign Span	2021-12-23 12:56:12 -05:00
filesearch.rs	Inline and remove FileSearch::search.	2022-02-02 09:06:34 +11:00
lib.rs	No branch protection metadata unless enabled	2022-02-19 17:31:40 +02:00
options.rs	No branch protection metadata unless enabled	2022-02-19 17:31:40 +02:00
output.rs	Auto merge of #91957 - nnethercote:rm-SymbolStr, r=oli-obk	2021-12-19 09:31:37 +00:00
parse.rs	Implement --check-cfg option (RFC 3013)	2022-02-16 13:03:12 +01:00
search_paths.rs	Make SearchPathFile::file_name_str non-optional.	2022-02-02 13:16:25 +11:00
session.rs	Remove DiagnosticBuilder.quiet	2022-01-23 00:11:13 -06:00
utils.rs	Implement RFC 2951: Native link modifiers	2021-05-05 16:04:25 -07:00