llvm-project.git/llvm/lib/ExecutionEngine/Interpreter/Interpreter.cpp, branch main

[LLVM] Use {} instead of std::nullopt to initialize empty ArrayRef (#109133)

2024-09-19T15:16:38+00:00

It is almost always simpler to use {} instead of std::nullopt to
initialize an empty ArrayRef. This patch changes all occurrences I could
find in LLVM itself. In future the ArrayRef(std::nullopt_t) constructor
could be deprecated or removed.

[llvm] Use std::nullopt instead of None (NFC)

2022-12-03T05:11:44+00:00

This patch mechanically replaces None with std::nullopt where the
compiler would warn if None were deprecated.  The intent is to reduce
the amount of manual work required in migrating from Optional to
std::optional.

This is part of an effort to migrate from llvm::Optional to
std::optional:

https://discourse.llvm.org/t/deprecating-llvm-optional-x-hasvalue-getvalue-getvalueor/63716

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

Bitcode: Change the materializer interface to return llvm::Error.

2016-11-09T17:49:19+00:00

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

llvm-svn: 286382

Drop materializeAllPermanently.

2015-12-18T20:13:39+00:00

This inlines materializeAll into the only caller
(materializeAllPermanently) and renames materializeAllPermanently to
just materializeAll.

llvm-svn: 256024

Make ExecutionEngine owning a DataLayout

2015-07-16T16:34:23+00:00

Summary:
This change is part of a series of commits dedicated to have a single
DataLayout during compilation by using always the one owned by the
module.

The ExecutionEngine will act as an exception and will be unsafe to
be reused across context. We don't enforce this rule but undefined
behavior can occurs if the user tries to do it.

Reviewers: lhames

Subscribers: echristo, llvm-commits, rafael, yaron.keren

Differential Revision: http://reviews.llvm.org/D11110

From: Mehdi Amini 
llvm-svn: 242414

Revert "Make ExecutionEngine owning a DataLayout"

2015-07-16T12:20:31+00:00

Reverting to fix buildbot breakage.

This reverts commit r242387.

llvm-svn: 242394

Make ExecutionEngine owning a DataLayout

2015-07-16T06:17:14+00:00

Summary:
This change is part of a series of commits dedicated to have a single
DataLayout during compilation by using always the one owned by the
module.

The ExecutionEngine will act as an exception and will be unsafe to
be reused across context. We don't enforce this rule but undefined
behavior can occurs if the user tries to do it.

Reviewers: lhames

Subscribers: echristo, llvm-commits, rafael, yaron.keren

Differential Revision: http://reviews.llvm.org/D11110

From: Mehdi Amini 
llvm-svn: 242387

[ExecutionEngine] ArrayRefize argument passing.

2015-06-13T19:50:29+00:00

No functionality change intended.

llvm-svn: 239687

Make it explicit that ExecutionEngine takes ownership of the modules.

2014-08-19T04:04:25+00:00

llvm-svn: 215967