[LU-6264] Enable strict compiler defence modes Created: 20/Feb/15  Updated: 25/Aug/15  Resolved: 25/Aug/15

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.8.0

Type: Improvement Priority: Major
Reporter: Oleg Drokin Assignee: Dmitry Eremin (Inactive)
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Related
is related to LU-6835 lfs.c:481: error: implicit declaratio... Resolved
is related to LU-6931 Luster build is failed with gcov enabled Closed
Rank (Obsolete): 17558

 Description   

It seems some of our customers/users are building Lustre with a lot more restrictive gcc options than we are (e.g see http://review.whamcloud.com/#/c/13654/1)

To avoid such things in the future, we really need to be building Lustre with the most protections and checks allowed by a particular compiler being used (need to detect this in configure somehow).
We'll also need to do it twice - once for the kernel where we are more restricted to remain compatible with the rest of the kernel,
and another time for our userspace tools and libraries - there we probably need to go full in with all the checks.



 Comments   
Comment by Oleg Drokin [ 20/Feb/15 ]

Dmitry, can you please take at lest an initial stab at it?

Comment by James A Simmons [ 31/Jul/15 ]

With the patch from John Hammond for LU-6835 the compiler has strict defense mode for the user land code.

Comment by Andreas Dilger [ 25/Aug/15 ]

Fixed with http://review.whamcloud.com/15392 "LU-6835 build: add -Wall to CFLAGS for test/ and utils/".

Generated at Sat Feb 10 01:58:42 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.