llvm-project/clang
Fangrui Song e3576b0afa [Driver] Simplify -g level computation and its interaction with -gsplit-dwarf
Summary:
When -gsplit-dwarf is used together with other -g options, in most cases
the computed debug info level is decided by the last -g option, with one
special case (see below). This patch drops that special case and thus
makes it easy to reason about:

// If a lower debug level -g comes after -gsplit-dwarf, in some cases
// -gsplit-dwarf is cancelled.
-gsplit-dwarf -g0 => 0
-gsplit-dwarf -gline-directives-only => DebugDirectivesOnly
-gsplit-dwarf -gmlt -fsplit-dwarf-inlining => 1
-gsplit-dwarf -gmlt -fno-split-dwarf-inlining => 1 + split

// If -gsplit-dwarf comes after -g options, with this patch, the net
// effect is 2 + split for all combinations
-g0 -gsplit-dwarf => 2 + split
-gline-directives-only -gsplit-dwarf => 2 + split
-gmlt -gsplit-dwarf -fsplit-dwarf-inlining => 2 + split
-gmlt -gsplit-dwarf -fno-split-dwarf-inlining => 1 + split (before) 2 + split (after)

The last case has been changed. In general, if the user intends to lower
debug info level, place that -g option after -gsplit-dwarf.

Some context:

In gcc, the last of -gsplit-dwarf -g0 -g1 -g2 -g3 -ggdb[0-3] -gdwarf-*
... decides the debug info level (-gsplit-dwarf -gdwarf-* have level 2).
It is a bit unfortunate that -gsplit-dwarf -gdwarf-* ... participate in
the level computation but that is the status quo.

Reviewers: dblaikie, echristo, probinson

Reviewed By: dblaikie, probinson

Subscribers: probinson, aprantl, jdoerfert, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D59923

llvm-svn: 358544
2019-04-17 01:46:27 +00:00
..
INPUTS
bindings [python, tests] Disable Clang Python tests on SPARC 2019-04-08 15:01:06 +00:00
cmake [clang-fuzzer] Include ExternalProject before using it. 2019-04-05 19:47:17 +00:00
docs [clang-format] Add AfterCaseLabel to BraceWrapping 2019-04-08 23:36:25 +00:00
examples [build] Rename clang-headers to clang-resource-headers 2019-03-04 21:19:53 +00:00
include [NFC] Remove unused function (Sema::pushExternalDeclIntoScope) 2019-04-16 22:59:39 +00:00
lib [Driver] Simplify -g level computation and its interaction with -gsplit-dwarf 2019-04-17 01:46:27 +00:00
runtime [cmake] Change deprecated $<CONFIG> to $<CONFIGURATION>. NFC 2019-03-30 14:38:51 +00:00
test [Driver] Simplify -g level computation and its interaction with -gsplit-dwarf 2019-04-17 01:46:27 +00:00
tools Time profiler: small fixes and optimizations 2019-04-15 21:02:47 +00:00
unittests [FileSystemStatCache] Update test for new FileSystemStatCache API 2019-04-16 18:00:43 +00:00
utils Various fixes and additions to creduce-clang-crash.py 2019-03-29 17:50:43 +00:00
www [Analyzer] Checker for non-determinism caused by sorting of pointer-like elements 2019-03-08 20:13:53 +00:00
.arcconfig
.clang-format
.clang-tidy Disable tidy checks with too many hits 2019-02-01 11:20:13 +00:00
.gitignore Adjust documentation for git migration. 2019-01-29 16:37:27 +00:00
CMakeLists.txt Moved everything SMT-related to LLVM and updated the cmake scripts. 2019-03-25 17:47:45 +00:00
CODE_OWNERS.TXT Add myself as code owner for OpenBSD driver 2018-11-30 21:42:34 +00:00
INSTALL.txt
LICENSE.TXT Fix typos throughout the license files that somehow I and my reviewers 2019-01-21 09:52:34 +00:00
ModuleInfo.txt
NOTES.txt PTH-- Remove feature entirely- 2018-12-04 14:34:09 +00:00
README.txt

README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source-level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:             http://clang.llvm.org/
Building and using Clang:         http://clang.llvm.org/get_started.html
Clang Static Analyzer:            http://clang-analyzer.llvm.org/
Information on the LLVM project:  http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/