mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add note to readme

Browse Source
This commit is contained in:
Antoni Boucher 2023-09-14 21:49:14 -04:00
parent 44b9c75359
commit f3b82df8f8
2 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Readme.md
View File

@ -111,6 +111,8 @@ $ LIBRARY_PATH=$(cat gcc_path) LD_LIBRARY_PATH=$(cat gcc_path) rustc +$(cat $CG_
object files when their content should have been changed by a change to cg_gccjit.</dd> object files when their content should have been changed by a change to cg_gccjit.</dd>
<dt>CG_GCCJIT_DISPLAY_CG_TIME</dt> <dt>CG_GCCJIT_DISPLAY_CG_TIME</dt>
<dd>Display the time it took to perform codegen for a crate</dd> <dd>Display the time it took to perform codegen for a crate</dd>
<dt>CG_RUSTFLAGS</dt>
<dd>Send additional flags to rustc. Can be used to build the sysroot without unwinding by setting `CG_RUSTFLAGS=-Cpanic=abort`.</dd>
</dl> </dl>
## Licensing ## Licensing

5
src/gcc_util.rs
View File

@ -22,7 +22,7 @@ pub(crate) fn global_gcc_features(sess: &Session, diagnostics: bool) -> Vec<Stri
// * function specific features. // * function specific features.
// //
// [^1]: target-cpu=native is handled here, other target-cpu values are handled implicitly // [^1]: target-cpu=native is handled here, other target-cpu values are handled implicitly
// through GCC TargetMachine implementation. // through GCC march implementation.
// //
// FIXME(nagisa): it isn't clear what's the best interaction between features implied by // FIXME(nagisa): it isn't clear what's the best interaction between features implied by
// `-Ctarget-cpu` and `--target` are. On one hand, you'd expect CLI arguments to always // `-Ctarget-cpu` and `--target` are. On one hand, you'd expect CLI arguments to always
@ -33,8 +33,6 @@ pub(crate) fn global_gcc_features(sess: &Session, diagnostics: bool) -> Vec<Stri
// should be taken in cases like these. // should be taken in cases like these.
let mut features = vec![]; let mut features = vec![];
// TODO(antoyo): -Ctarget-cpu=native
// Features implied by an implicit or explicit `--target`. // Features implied by an implicit or explicit `--target`.
features.extend( features.extend(
sess.target sess.target
@ -144,7 +142,6 @@ fn backend_feature_name(s: &str) -> Option<&str> {
Some(feature) Some(feature)
} }
// TODO(antoyo): maybe move to a new module gcc_util.
// To find a list of GCC's names, check https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html // To find a list of GCC's names, check https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html
pub fn to_gcc_features<'a>(sess: &Session, s: &'a str) -> SmallVec<[&'a str; 2]> { pub fn to_gcc_features<'a>(sess: &Session, s: &'a str) -> SmallVec<[&'a str; 2]> {
let arch = if sess.target.arch == "x86_64" { "x86" } else { &*sess.target.arch }; let arch = if sess.target.arch == "x86_64" { "x86" } else { &*sess.target.arch };