diff options
Diffstat (limited to 'config')
-rw-r--r-- | config/companion_libs.in | 22 | ||||
-rw-r--r-- | config/companion_libs/ppl.in | 33 |
2 files changed, 52 insertions, 3 deletions
diff --git a/config/companion_libs.in b/config/companion_libs.in index 49dc662..d581d80 100644 --- a/config/companion_libs.in +++ b/config/companion_libs.in @@ -9,10 +9,11 @@ config GMP_MPFR prompt "GMP and MPFR" help gcc 4.3.0 and above requires both GMP and MPFR to build some frontends, - and some other components can use them as well (eg. binutils and gdb). + and some other components can use them as well. - Say 'Y' here if you want to build those two libraries specifically - for crosstool-NG. + These will be automatically selected if you choose gcc>=4.3.0, but you + can say 'Y' here if you want to build those two libraries for the other + components (that don't select them by default). The packages that can use GMP and MPFR are: - binutils @@ -35,4 +36,19 @@ source config/companion_libs/gmp.in source config/companion_libs/mpfr.in endif +config PPL_CLOOG + bool + prompt "PPL and GLooG/PPL" + help + gcc-4.4.0 and above requires both PPL and CLooG/PPL to build some + parts of the optimiser (GRAPHITE loop optimisation, to be precise). + + These will be automatically selected if you choose gcc>=4.4.0, but you + can say 'Y' here, although it is unknown yet if any other component + can use them. + +if PPL_CLOOG +source config/companion_libs/ppl.in +endif + endmenu diff --git a/config/companion_libs/ppl.in b/config/companion_libs/ppl.in new file mode 100644 index 0000000..d8f5906 --- /dev/null +++ b/config/companion_libs/ppl.in @@ -0,0 +1,33 @@ +# PPL options + +choice + bool + prompt "PPL version" + +config PPL_V_0_10_2 + bool + prompt "0.10.2" + +# CT_INSERT_VERSION_ABOVE +# Don't remove above line! +endchoice + +config PPL_VERSION + string + default "0.10.2" if PPL_V_0_10_2 +# CT_INSERT_VERSION_STRING_ABOVE +# Don't remove above line! + +config PPL_CHECK + bool + prompt "Check PPL (!!! README !!!)" + default n + help + Checking PPL is very intensive and takes a loooong time. + The PPL folks do not recommend checking the library, but they do + not recommend not checking it, either. + + Checking PPL is thus disabled by default. + + If you suspect that your PPL library is the cause for incorrectly + generated code, you should answer 'Y' here. |