From bfccd832782353a000b430870a6602cc591c8b7a Mon Sep 17 00:00:00 2001 From: John Ericson Date: Tue, 21 May 2019 23:00:27 -0400 Subject: Inline `Settings` into `DynFlags` After the previous commit, `Settings` is just a thin wrapper around other groups of settings. While `Settings` is used by GHC-the-executable to initalize `DynFlags`, in principle another consumer of GHC-the-library could initialize `DynFlags` a different way. It therefore doesn't make sense for `DynFlags` itself (library code) to separate the settings that typically come from `Settings` from the settings that typically don't. --- compiler/deSugar/DsForeign.hs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'compiler/deSugar/DsForeign.hs') diff --git a/compiler/deSugar/DsForeign.hs b/compiler/deSugar/DsForeign.hs index 4df053d845..dd0cc4860a 100644 --- a/compiler/deSugar/DsForeign.hs +++ b/compiler/deSugar/DsForeign.hs @@ -541,7 +541,7 @@ mkFExportCBits dflags c_nm maybe_target arg_htys res_hty is_IO_res_ty cc | otherwise = text ('a':show n) -- generate a libffi-style stub if this is a "wrapper" and libffi is enabled - libffi = sLibFFI (settings dflags) && isNothing maybe_target + libffi = platformMisc_libFFI (platformMisc dflags) && isNothing maybe_target type_string -- libffi needs to know the result type too: -- cgit v1.2.1