rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2023-11-06	warn when using an unstable feature with -Ctarget-feature	Ralf Jung	-2/+6

2023-09-23	allow LTO on `proc-macro` crates with `-Zdylib-lto`	onur-ozkan	-0/+2
	Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-09-08	debuginfo: add compiler option to allow compressed debuginfo sections	Augie Fackler	-0/+2
	LLVM already supports emitting compressed debuginfo. In debuginfo=full builds, the debug section is often a large amount of data, and it typically compresses very well (3x is not unreasonable.) We add a new knob to allow debuginfo to be compressed when the matching LLVM functionality is present. Like clang, if a known-but-disabled compression mechanism is requested, we disable compression and emit uncompressed debuginfo sections. The API is different enough on older LLVMs we just pretend the support is missing on LLVM older than 16.
2023-07-17	Better diagnostics for dlltool errors.	James Farrell	-1/+2
	When dlltool fails, show the full command that was executed. In particular, llvm-dlltool is not very helpful, printing a generic usage message rather than what actually went wrong, so stdout and stderr aren't of much use when troubleshooting.
2023-06-01	Use translatable diagnostics in `rustc_const_eval`	Deadbeef	-2/+6

2023-05-25	Ensure Fluent messages are in alphabetical order	clubby789	-54/+54

2023-05-06	Rollup merge of #111203 - Kobzol:remark-print-kind, r=tmiasko	Matthias Krüger	-1/+1
	Output LLVM optimization remark kind in `-Cremark` output Since https://github.com/rust-lang/rust/pull/90833, the optimization remark kind has not been printed. Therefore it wasn't possible to easily determine from the log (in a programmatic way) which remark kind was produced. I think that the most interesting remarks are the missed ones, which can lead users to some code optimization. Maybe we could also change the format closer to the "old" one: ``` note: optimization remark for tailcallelim at /checkout/src/libcore/num/mod.rs:1:0: marked this call a tail call candidate ``` I wanted to programatically parse the remarks so that they could work e.g. with https://github.com/OfekShilon/optview2. However, now that I think about it, probably the proper solution is to tell rustc to output them to YAML and then use the YAML as input for the opt remark visualization tools. The flag for enabling this does not seem to work though (https://github.com/rust-lang/rust/issues/96705#issuecomment-1117632322). Still I think that it's good to output the remark kind anyway, it's an important piece of information. r? ```@tmiasko```
2023-05-04	Output LLVM optimization remark kind in `-Cremark` output	Jakub Beránek	-1/+1

2023-04-18	Stablize raw-dylib, link_ordinal and -Cdlltool	Daniel Paoliello	-1/+1

2023-03-29	Check for escape sequences in Fluent resources	clubby789	-1/+2

2023-03-11	Simplify message paths	est31	-0/+89
	This makes it easier to open the messages file while developing on features. The commit was the result of automatted changes: for p in compiler/rustc_; do mv $p/locales/en-US.ftl $p/messages.ftl; rmdir $p/locales; done for p in compiler/rustc_; do sed -i "s#\.\./locales/en-US.ftl#../messages.ftl#" $p/src/lib.rs; done