Line
Link Here
|
0 |
-- make.conf.example |
0 |
++ make.conf.example |
Lines 22-27
Link Here
|
22 |
# Example: |
22 |
# Example: |
23 |
#USE="X gtk gnome -alsa" |
23 |
#USE="X gtk gnome -alsa" |
24 |
|
24 |
|
|
|
25 |
# Host Setting |
26 |
# =========== |
27 |
# |
28 |
# All RV64 systems should use this host setting: |
29 |
CHOST="riscv64-unknown-linux-gnu" |
30 |
|
31 |
# whereas all RV32 ones should use: |
32 |
#CHOST="riscv-unknown-linux-gnu" |
33 |
|
25 |
# Host and optimization settings |
34 |
# Host and optimization settings |
26 |
# ============================== |
35 |
# ============================== |
27 |
# |
36 |
# |
Lines 39-47
Link Here
|
39 |
# -frecord-gcc-switches, since otherwise the check could result in false |
48 |
# -frecord-gcc-switches, since otherwise the check could result in false |
40 |
# positive results. |
49 |
# positive results. |
41 |
# |
50 |
# |
42 |
# Please refer to the GCC manual for a list of possible values. |
51 |
# -mcpu=<cpu-type> tells the compiler to take full advantage of the ABI and |
|
|
52 |
# instructions available on a certain CPU. This will produce code which may |
53 |
# not run on other RISC-V CPUs, even if they support the same ISA. |
54 |
# |
55 |
# -mtune=<cpu-type-or-series> results in code optimised for a specific CPU |
56 |
# (e.g. SiFive U74) or family (e.g. the SiFive 7 series) without breaking |
57 |
# compatibility with other RISC-V CPUs supporting the same ISA. |
58 |
# |
59 |
# -march=<isa-string> specifies the exact ISA for which to generate code. |
60 |
# This is normally not needed if you set -mcpu but might be useful for CPUs |
61 |
# not explicitly supported by gcc yet. Should that be the case and you aren't |
62 |
# sure what ISA string to use, the output of /proc/cpuinfo might give you a hint. |
63 |
# |
64 |
# -mabi=<abi-string> specifies the integer and floating-point calling convention |
65 |
# to use. Again, this is normally not needed if you set -mcpu. Care should be |
66 |
# taken while setting both -march and -mabi, as some calling conventions are |
67 |
# impossible to implement on some ISAs. |
68 |
# |
69 |
# Please refer to the section "RISC-V Options" of the GCC manual for a list |
70 |
# of possible ABI, architecture, CPU and feature values. |
71 |
# |
72 |
# Decent examples: |
43 |
# |
73 |
# |
44 |
#CFLAGS="-O2 -pipe" |
74 |
#CFLAGS="-mcpu=sifive-u74 -O2 -pipe" |
|
|
75 |
#CFLAGS="-mtune=sifive-7-series -O2 -pipe" |
45 |
# |
76 |
# |
46 |
# If you set a CFLAGS above, then this line will set your default C++ flags to |
77 |
# If you set a CFLAGS above, then this line will set your default C++ flags to |
47 |
# the same settings. |
78 |
# the same settings. |
Lines 76-82
Link Here
|
76 |
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST. |
107 |
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST. |
77 |
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS. |
108 |
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS. |
78 |
# |
109 |
# |
79 |
#ACCEPT_KEYWORDS="~arch" |
110 |
#ACCEPT_KEYWORDS="~riscv" |
80 |
|
111 |
|
81 |
# ACCEPT_LICENSE is used to mask packages based on licensing restrictions. |
112 |
# ACCEPT_LICENSE is used to mask packages based on licensing restrictions. |
82 |
# It may contain both license and group names, where group names are |
113 |
# It may contain both license and group names, where group names are |