-
Notifications
You must be signed in to change notification settings - Fork 70
/
Herc31_COptsGNU.cmake
297 lines (228 loc) · 11.4 KB
/
Herc31_COptsGNU.cmake
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
# Herc31_COptsGNU.cmake - Set C compiler options - used for GNU gcc on
# other than Apple platforms.
#[[ Copyright 2017 by Stephen Orso.
Distributed under the Boost Software License, Version 1.0.
See accompanying file BOOST_LICENSE_1_0.txt or copy at
http://www.boost.org/LICENSE_1_0.txt)
]]
#[[
Set C compiler options - used for any gcc except for gcc versions
4.2.1 or less on Apple platforms.
Some options are needed for a correct build, for example
-mstructure-size-boundary=8 for certain ARM flavors, and
-fno-strict-aliasing when it is required. Other options are
truly optimization related, such as -frename-registers on ARM.
Options that are required to build Hercules are *always* added
to the C command line options, as are the debugger options
("-W -Wall -g3 -ggdb3"). If OPTIMIZE="<whatever>" is coded on the
CMake command line, the builder's options are appended to the *always*
created options, which gives the builder the opportunity to add any
preferred optimization options, such as -O3 (which is never added
by this CMake script), and to negate any of the *always* created
options, because when options conflict, the last one wins.
It is not clear what happens in GCC when one specifies -O3 *after*
turning off something enabled by -O3, for example -fno-strict-aliasing.
But that is the builder's problem. Ours here is to make sure the
optimize flag selection process is clear.
OPTIMIZE=YES means this script will interpret the target system's
and compiler's capabilities and nature and craft a reasonable and
workable set of optimization flags, starting with -O2.
OPTIMIZE=NO means only the options required to build Hercules and
the debugger options -W, -Wall, -g3, and -ggdb3 are included, as
is -O0. No other options are included.
See https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html for
specifics of the optimizations turned on at each level of -O. In
particular, note that any optimization level other than -Os or -O0
include -fomit-frame-pointer if doing so preserves the ability to
use the debugger.
So rather than mess around with whether -fomit-frame-pointer should
or should not be included, we shall let the compiler include it
based on the optimization profile (-O0 through -O2) that is to be
used for the build. Anyone feeling strongly about can always
override the compiler flags by passing -DOPTIMIZATION="whatever"
to CMake.
For processor-based stuff, we will use CMAKE_SYSTEM_PROCESSOR for
the processor name; this is what config.guess does in autotools.
CMAKE_SYSTEM_PROCESSOR is set to the host's uname -p output unless
cross-compiling, in which case the builder must set things up
on their own.
Gcc 4.3.0 included support for the option -minline-stringops-dynamically
(see https://gcc.gnu.org/onlinedocs/gcc-4.3.0/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options)
The gcc option summary was not updated for -minline-stringops-dynamically
until 4.4.0.)
The most recent Hercules configure.ac checks for a GNU compiler issue
that breaks implicit __alloca calls. This issue affects only MinGW
and Cygwin versions of the GNU compilers, and then only versions 3.0.x
and 3.1.x. A patch was written for 3.3 and backported to 3.2. Because
this is a MinGW/Cygwin issue only, and Hercules does not use either
tool to build Hercules, testing around this issue has not been included
in CMake scripts for Hercules. See:
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=8750 (desc. and 3.3 patch)
- https://gcc.gnu.org/ml/gcc-patches/2003-02/msg01482.html (3.2 patch)
]]
# Basic C flags. Enable all warnings, and enable gdb debugging options
# including macro definitions. Set the calculated set of optimization
# flags to the null string.
set( CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -DHAVE_CONFIG_H -g3 -ggdb3" )
# Flags needed to deal with issues in the toolchain.
if( HAVE_VERY_STRICT_ALIASING )
set( CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -fno-strict-aliasing" )
endif( HAVE_VERY_STRICT_ALIASING )
# If structures are padded and the target is ARM-like, then we must
# tell the compiler to pad to an 8-bit (one byte) boundary.
if( ("${target_processor}" MATCHES "ARM")
OR ("${target_processor}" MATCHES "XSCALE") )
if( NOT STRUCT_NOT_PADDED )
set( CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -mstructure-size-boundary=8" )
endif( )
endif( )
# ----------------------------------------------------------------------
# Above this point, everything that has been added to c flags is needed
# for compilation and has nothing to do with optimization.
# Below this point, everything affects the optimization flags. We will
# set CMAKE_C_FLAGS_RELEASE only based on -DOPTIMIZE string or the flags
# determined by this script.
# ----------------------------------------------------------------------
# Builder-specified automatic optimization not YES nor NO. So the
# builder has provided an optimization string that we shall use.
if( NOT ("${OPTIMIZATION}" STREQUAL "") )
if( NOT (${OPTIMIZATION} IN_LIST herc_YES_NO) )
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} ${OPTIMIZATION}" )
return( )
endif( )
endif( )
# If automatic optimization is specified or defaulted to NO, or if this
# is a debug build, then add -O0 to the c flags and we are done.
if( DEBUG_BUILD
OR ("${OPTIMIZATION}" STREQUAL "NO")
OR ( ("${buildWith_OPTIMIZATION}" STREQUAL "NO")
AND ("${OPTIMIZATION}" STREQUAL "") )
)
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -fno-omit-frame-pointer -O0" )
return( )
endif( )
# Not a debug build, builder-specified automatic optimization is not
# NO, and if builder-specified automatic optimization is not blank,
# the builder-specified automatic optimization is not NO.
# Determine automatic optizimation options.
# ----------------------------------------------------------------------
# Automatic optimization requested or defaulted
# ----------------------------------------------------------------------
# Automatic optimization specified as or defaulted to YES. Now the fun
# begins. The first part is easy: -O2. We do not do -O3; there is no
# consensus that it represents a better choice. And if -O3 is the
# builder's wish, OPTIMIZATION="-O3" is the way to do it. Note: the
# spaces at the beginning and end of the input expression are essential.
string(REGEX REPLACE " -O3 " " "
CMAKE_C_FLAGS_RELEASE " ${CMAKE_C_FLAGS_RELEASE} "
)
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -O2" )
# Now see if we can improve on things. Improvements are typically
# target-processor dependent, and that is the case now, but who knows
# the future brings....
# Determine if this is this a cross-platform build.
if( "${CMAKE_HOST_SYSTEM_PROCESSOR}" STREQUAL "${CMAKE_SYSTEM_PROCESSOR}" )
set( host_is_target 1 )
else( )
set( host_is_target 0 )
endif( )
# Make the target processor uppercase to simplify testing
string( TOUPPER "${CMAKE_SYSTEM_PROCESSOR}" target_processor )
# For Intel processors, two checks apply to both 32-bit and 64-bit
# processors: -minline-stringops-dynamically and -march=native.
# We will test both here. If -minline-stringops-dynamically is
# accepted, we will add it to the option string. -march=native
# availability will be addressed based on processor bitness.
if( "${target_processor}" IN_LIST herc_Intel )
CHECK_C_COMPILER_FLAG("-march=native" HAVE__MARCH_NATIVE)
CHECK_C_COMPILER_FLAG("-minline-stringops-dynamically" HAVE__MINLINE-STRINGOPS-DYNAMICALLY)
if( HAVE__MINLINE-STRINGOPS-DYNAMICALLY )
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -minline-stringops-dynamically" )
endif( )
endif( )
# Intel 64-bit processor-specific compiler flags.
# Some notes:
# 1) if the builder is cross-compiling, it is the builder's
# responsibility to set a system processor that is valid for the
# GNU compiler in use.
# 2) GNU compilers 4.2.0 and better accept -march=native. Prior to
# 4.2.0, Hercules used -march=K8 for all 64-bit processors, even on
# Apple builds (which use a script separate from this one).
# 3) One target/compiler combination, NetBSD 7.0.1 and gcc 4.8.4,
# reject -march=native. Use -march=x86-64 instead.
if( "${target_processor}" IN_LIST herc_Intel_64 )
if( NOT host_is_target )
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -march=x86-64" )
elseif( CMAKE_C_COMPILER_VERSION VERSION_LESS "4.2.0" )
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -march=K8" )
elseif( HAVE__MARCH_NATIVE )
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -march=native" )
else( )
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -march=x86-64" )
endif( )
unset( target_processor )
unset( host_is_target )
return( )
endif( )
# Intel 32-bit processor-specific compiler flags.
# Some notes:
# 1) if the builder is cross-compiling, it is the builder's
# responsibility to set a system processor that is valid for the
# GNU compiler in use.
# 2) Apparently, some systems report i786, but GNU does not accept
# that. Use Pentium4 instead.
# 3) The GNU compiler built with selected very old Red Had distros
# apparently report version 2.9.6, even though that was never a
# valid GNU release number. And compilers reporting 2.9.6 do not
# understand i686.
# 4) GNU compilers 4.2.0 and better accept -march=native.
# 6) One target/compiler combination, NetBSD 7.0.1 and gcc 4.8.4,
# reject -march=native. Use ${CMAKE_SYSTEM_PROCESSOR} instead.
if( "${target_processor}" IN_LIST herc_Intel_32 )
if( "${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "i786" )
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -march=pentium4" )
elseif( ("${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "i686")
AND (CMAKE_C_COMPILER_VERSION VERSION_EQUAL "2.9.6")
)
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -march=i586" )
elseif( host_is_target
AND ( HAVE__MARCH_NATIVE )
)
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -march=native" )
else( )
set( CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -march=${CMAKE_SYSTEM_PROCESSOR}" )
endif( )
unset( target_processor )
unset( host_is_target )
return( )
endif( )
# Optimization flags for ARM
set( optimization_flags "")
if( "${target_processor}" STREQUAL "ARM" )
# The older ARM processor is just reported as "ARM" in CMAKE_SYSTEM_PROCESSOR.
# There is not much that can be added for the original ARM.
string( CONCAT optimization_flags "${optimization_flags} "
"-frename-registers"
)
elseif( "${target_processor}" MATCHES "ARM" )
# Newer ARM prcoessors, those with a number after "ARM", apparently
# benefit from -mcpu and -mtune, while older ones do not. This is
# apparently true for Xscale cpus too, but it is not clear how those
# systems are identified.
string( CONCAT optimization_flags "${optimization_flags} "
"-mcpu=${CMAKE_SYSTEM_PROCESSOR} "
"-mtune=${CMAKE_SYSTEM_PROCESSOR} "
"-frename-registers"
)
elseif( "${target_processor}" MATCHES "XSCALE" )
# XSCALE processors are based on ARM and also apparently benefit from
# -mcpu and -mtune.
string( CONCAT optimization_flags "${optimization_flags} "
"-mcpu=${CMAKE_SYYTEM_PROCESSOR} "
"-mtune=${CMAKE_SYSTEM_PROCESSOR} "
"-frename-registers"
)
endif( )
unset( target_processor )
unset( host_is_target )
return( )