This is an archive of the discontinued LLVM Phabricator instance.

Differential D56337

[ADT] Remove attribute LLVM_ALWAYS_INLINE from several classes.
ClosedPublic

Authored by davide on Jan 4 2019, 3:09 PM.
Tokens
"Like" token, awarded by jkorous.

Details

Reviewers
chandlerc
JDevlieghere
friss
aprantl
Commits
rG078fb93c3d8c: [Docs] Add a note clarifying how to get good test performances.
rL351885: [Docs] Add a note clarifying how to get good test performances.
Summary

The original motivation for this was trying to get faster turnaround
when running check-llvm at -O0. The impact on debuggability seems
to outweight the benefits, as it makes StringRef and other ADT
classes fairly undebuggable.

Add a section in the developer's documentation explaining that
optimized builds are needed for decent test performances instead.

Based on a discussion on llvm-dev, pending more general consensus.

Diff Detail

Repository
rL LLVM

Event Timeline

davide created this revision.Jan 4 2019, 3:09 PM
Herald added a subscriber: dexonsmith. · View Herald TranscriptJan 4 2019, 3:09 PM
Harbormaster completed remote builds in B26412: Diff 180331.Jan 4 2019, 3:11 PM
chandlerc accepted this revision.Jan 4 2019, 3:40 PM

LGTM.

There are a bunch of others that need to go, but those can be follow-ups.

This revision is now accepted and ready to land.Jan 4 2019, 3:40 PM
JDevlieghere added inline comments.Jan 4 2019, 3:48 PM
llvm/docs/TestingGuide.rst
110 ↗(On Diff #180331)

Should we rephrase this in a way that makes it clear that you don't always have to set the CMake flag, e.g. in release? Maybe something like `build ... in release or at least with -O2"?

chandlerc added inline comments.Jan 4 2019, 3:58 PM
llvm/docs/TestingGuide.rst
110 ↗(On Diff #180331)

That's a good point, we should instead suggest enabling one of teh release build modes rather than hard coding flags here.

Maybe clarify that those are independent of LLVM_ENABLE_ASSERTIONS.

aprantl accepted this revision.Jan 7 2019, 9:27 AM
aprantl added inline comments.
llvm/docs/TestingGuide.rst
110 ↗(On Diff #180331)

nit: I think it should be performance (singular)?

aprantl added inline comments.Jan 7 2019, 9:29 AM
llvm/docs/TestingGuide.rst
115 ↗(On Diff #180331)

Do people manually tune their -O flags? Wouldn't it be more straightforward to just recommend to build/run the tests in -DCMAKE_BUILD_TYPE=Release or RelWithDebInfo mode?

jkorous awarded a token.Jan 8 2019, 1:57 AM
davide updated this revision to Diff 182976.Jan 22 2019, 1:48 PM

Update the wording.

JDevlieghere accepted this revision.Jan 22 2019, 1:49 PM

LGTM

Closed by commit rL351885: [Docs] Add a note clarifying how to get good test performances. (authored by davide). · Explain WhyJan 22 2019, 1:52 PM
This revision was automatically updated to reflect the committed changes.

Revision Contents

PathSize
llvm/
trunk/
docs/
7 lines

Diff 182978

llvm/trunk/docs/TestingGuide.rst

Show First 20 Lines • Show All 101 Lines • ▼ Show 20 Lines
---------------- ----------------
To run all of the LLVM regression tests use the check-llvm target: To run all of the LLVM regression tests use the check-llvm target:
.. code-block:: bash .. code-block:: bash
% make check-llvm % make check-llvm
In order to get reasonable testing performance, build LLVM and subprojects
in release mode, i.e.
.. code-block:: bash
% cmake -DCMAKE_BUILD_TYPE="Release"
If you have `Clang <http://clang.llvm.org/>`_ checked out and built, you If you have `Clang <http://clang.llvm.org/>`_ checked out and built, you
can run the LLVM and Clang tests simultaneously using: can run the LLVM and Clang tests simultaneously using:
.. code-block:: bash .. code-block:: bash
% make check-all % make check-all
To run the tests with Valgrind (Memcheck by default), use the ``LIT_ARGS`` make To run the tests with Valgrind (Memcheck by default), use the ``LIT_ARGS`` make
▲ Show 20 Lines • Show All 468 Lines • Show Last 20 Lines