llvm-project.git/lld/test/ELF/version-script-err.s, branch main

[ELF] Don't cause assertion failure if --dynamic-list or --version-script takes an empty file

2020-06-05T22:59:54+00:00

Fixes PR46184
Report line 1 of the last memory buffer.

[ELF][test] Change -o %t to -o /dev/null if the output is not needed

2020-02-13T05:54:50+00:00

[ELF] - Remove ScriptLexer::Error field and check ErrorCount instead.

2017-08-04T10:34:14+00:00

D35945 introduces change when there is useless to check Error flag
in few places, but ErrorCount must be checked instead.

But then we probably can just check ErrorCount always. That should simplify
things. Patch do that.

Differential revision: https://reviews.llvm.org/D36266

llvm-svn: 310046

[ELF] Better error reporting for linker scripts

2016-11-21T15:49:56+00:00

Differential revision: https://reviews.llvm.org/D26795

llvm-svn: 287547

Revert "Add a space to work around a Windows CPython / MSys quoting bug"

2016-10-31T20:13:41+00:00

This reverts commit r284768.

After LLVM r285237, the lit shell interpreter works around this bug for
us.

llvm-svn: 285629

Add a space to work around a Windows CPython / MSys quoting bug

2016-10-20T20:02:24+00:00

Summary:
The rules for quoting the command line that a subprocess receives are
user space conventions implemented by the C runtime. Python's quoting
rules are implemented here:
https://github.com/python/cpython/blob/c30098c8c6014f3340a369a31df9c74bdbacc269/Lib/subprocess.py#L725

The result is that the final command line C string computed by Python is
'echo \"'. Mingw doesn't appear to interpret that backslash as escaping
the quote because it is not already inside a quoted region. As a result,
our echo command prints a single backslash instead of a quote.

The whole issue can be sidestepped by adding a space a forcing Python to
put the argument to echo in double quotes.

Reviewers: inglorion, ruiu

Subscribers: llvm-commits

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

llvm-svn: 284768

Recommit r275257 "[ELF] - Implement extern "c++" version script tag"

2016-07-16T12:26:39+00:00

BSD toolchain contains a bug:
https://sourceforge.net/p/elftoolchain/tickets/491/

In short demangler works differently, fix was to update the testcase.
It should fix the FreeBSD bot failture:
http://lab.llvm.org:8011/builders/lld-x86_64-freebsd/builds/19432/steps/test_lld/logs/stdio

Original commit message was:
[ELF] - Implement extern "c++" version script tag

Patch implements 'extern' version script tag.
Currently only values in quotes(") are supported.

Matching of externs is performed in the same pass as exact match of globals.

Differential revision: http://reviews.llvm.org/D21930

llvm-svn: 275682

Reverted r275257 "[ELF] - Implement extern "c++" version script tag"

2016-07-13T08:19:04+00:00

It broke build bots:
http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast/builds/8204
http://lab.llvm.org:8011/builders/lld-x86_64-freebsd/builds/19432

llvm-svn: 275258

[ELF] - Implement extern "c++" version script tag

2016-07-13T07:46:00+00:00

Patch implements 'extern' version script tag.
Currently only values in quotes(") are supported.

Matching of externs is performed in the same pass as exact match of globals.

Differential revision: http://reviews.llvm.org/D21930

llvm-svn: 275257

[ELF] - Show explicit error if extern keyword is used in version script.

2016-06-22T15:02:57+00:00

Since we do not have plans to support it in closest future,
it is better than common script parsing error.

llvm-svn: 273426