llvm-project.git/llvm/tools/bugpoint/FindBugs.cpp, branch users/nico/python-2

[bugpoint] Use a range-based for loop (NFC) (#140743)

2025-05-20T21:34:44+00:00

[llvm] Use true/false instead of 1/0 (NFC)

2022-01-07T08:39:14+00:00

Identified with modernize-use-bool-literals.

Avoid shuffle self-assignment in EXPENSIVE_CHECKS builds

2021-03-10T11:17:34+00:00

Some versions of libstdc++ perform self-assignment in std::shuffle. This
breaks the EXPENSIVE_CHECKS builds of TableGen due to an incorrect assertion
in libstdc++.

See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85828.

Fixes https://llvm.org/PR37652

Reviewed By: RKSimon

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

Update the file headers across all of the LLVM projects in the monorepo

2019-01-19T08:50:56+00:00

to reflect the new license.

We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.

Essentially, all code in the project is now made available by the LLVM
project under our new license, so you will see that the license headers
include that license only. Some of our contributors have contributed
code under our old license, and accordingly, we have retained a copy of
our old license notice in the top-level files in each project and
repository.

llvm-svn: 351636

Change the BugDriver to store the current module with std::unique_ptr.

2018-02-14T21:44:34+00:00

While there, change a bunch of helper functions to take references to
avoid adding calls to get().

This should conclude the bugpoint yak shaving.

llvm-svn: 325177

Remove redundant includes from tools.

2017-12-13T21:31:10+00:00

llvm-svn: 320631

Remove uses of deprecated std::random_shuffle in the LLVM code base. Reviewed as https://reviews.llvm.org/D29780.

2017-02-16T14:37:03+00:00

llvm-svn: 295325

bugpoint: Return Errors instead of passing around strings

2016-09-06T17:18:22+00:00

This replaces the threading of `std::string &Error` through all of
these APIs with checked Error returns instead. There are very few
places here that actually emit any errors right now, but threading the
APIs through will allow us to replace a bunch of exit(1)'s that are
scattered through this code with proper error handling.

This is more or less NFC, but does move around where a couple of error
messages are printed out.

llvm-svn: 280720

Revert "bugpoint: Stop threading errors through APIs that never fail"

2016-09-06T04:45:37+00:00

This isn't the right thing to do - it turns out a number of the APIs
that "never fail" just exit(1) if something bad happens. We can and
should thread Error through this instead.

That diff will make more sense with this reverted. Sorry for the
noise.

This reverts r280690

llvm-svn: 280691

bugpoint: Stop threading errors through APIs that never fail

2016-09-06T04:04:13+00:00

This simplifies ListReducer and most of its subclasses by removing the
std::string &Error that was threaded through all of them but almost
never used. If we end up needing error handling in more places here we
can reinstate it using llvm::Error instead of these unwieldy strings.

The 2 cases (out of 12) that actually can hit the error cases are a
little bit awkward now, but those will clean up as I refactor this API
further.

llvm-svn: 280690