[llvm-bugs] [Bug 30202] notify_all_at_thread_exit seg faults if run from a raw pthread context.
https://llvm.org/bugs/show_bug.cgi?id=30202 Eric Fiselier changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Eric Fiselier --- r280588. -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30266] New: [CWG 909] C-style cast necessitating static_cast -> const_cast fails for conversion operator
https://llvm.org/bugs/show_bug.cgi?id=30266
Bug ID: 30266
Summary: [CWG 909] C-style cast necessitating static_cast ->
const_cast fails for conversion operator
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++14
Assignee: unassignedclangb...@nondot.org
Reporter: r...@gmx.net
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
struct S {
operator const int* ();
};
void f(S& s) {
const_cast(static_cast(s)); // #1
(int*) s; // #2
}
#2 is intended to be valid (see core issue 909), yet fails to compile.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30267] New: Linker script orphan sections get an invalid address on AArch64
https://llvm.org/bugs/show_bug.cgi?id=30267 Bug ID: 30267 Summary: Linker script orphan sections get an invalid address on AArch64 Product: lld Version: unspecified Hardware: PC OS: FreeBSD Status: NEW Severity: normal Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: and...@fubar.geek.nz CC: ema...@freebsd.org, llvm-bugs@lists.llvm.org Classification: Unclassified Created attachment 17211 --> https://llvm.org/bugs/attachment.cgi?id=17211&action=edit objdump -x of the linked kernel While trying to link the FreeBSD arm64 kernel I received around 45141 of the following error: relocation R_AARCH64_ADR_PREL_PG_HI21 out of range After commenting out the check I linked the kernel and found the orphaned sections were placed at the end of the file and started with a virtual address of 0. This caused an overflow in the relocation. It would seem binutils has a heuristic to put these sections after a section with similar attributes: https://sourceware.org/binutils/docs/ld/Orphan-Sections.html -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30268] New: lld treats "operator delete[]" as a wildcard
https://llvm.org/bugs/show_bug.cgi?id=30268
Bug ID: 30268
Summary: lld treats "operator delete[]" as a wildcard
Product: lld
Version: unspecified
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P
Component: ELF
Assignee: unassignedb...@nondot.org
Reporter: ema...@freebsd.org
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
While testing linking linking FreeBSD/amd64 with lld at r280548, lld produces:
unsupported wildcard: operator delete[](void*)
from this snippet of libc++ version script:
...
GLIBCXX_3.4 {
extern "C++" {
"operator delete[](void*)";
"operator delete(void*)";
...
--
You are receiving this mail because:
You are on the CC list for the bug.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 23214] [META] Using LLD as FreeBSD's system linker
https://llvm.org/bugs/show_bug.cgi?id=23214 Bug 23214 depends on bug 30221, which changed state. Bug 30221 Summary: linker script expression parser does not accept '~' https://llvm.org/bugs/show_bug.cgi?id=30221 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30221] linker script expression parser does not accept '~'
https://llvm.org/bugs/show_bug.cgi?id=30221 Simon Atanasyan changed: What|Removed |Added Status|NEW |RESOLVED CC||si...@atanasyan.com Resolution|--- |FIXED Assignee|unassignedb...@nondot.org |si...@atanasyan.com --- Comment #1 from Simon Atanasyan --- Fixed at r280546. -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30269] New: lld: implement --section-start, aka -Ttext etc.
https://llvm.org/bugs/show_bug.cgi?id=30269
Bug ID: 30269
Summary: lld: implement --section-start, aka -Ttext etc.
Product: lld
Version: unspecified
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P
Component: ELF
Assignee: unassignedb...@nondot.org
Reporter: ema...@freebsd.org
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
The build for FreeBSD's boot loader components was recently reworked to use a
linker script instead of -N, but we've now encountered another issue in the
lack of -Ttext.
GNU ld documents them as:
--section-start sectionname=org
Locate a section in the output file at the absolute address given
by org. You may use this option as many times as necessary to
locate multiple sections in the command line. org must be a single
hexadecimal integer; for compatibility with other linkers, you may
omit the leading 0x usually associated with hexadecimal values.
Note: there should be no white space between sectionname, the
equals sign ("="), and org.
-Tbss org
-Tdata org
-Ttext org
Same as --section-start, with ".bss", ".data" or ".text" as the
sectionname.
However, see this note about Gold's -Ttext / -Ttext-segment:
Gold's -Ttext option is approximately the same as GNU ld's
-Ttext-segment option. This patch adds -Ttext-segment to gold as an
alias for -Ttext, so that scripts can use both linkers the same way.
This was prompted in particular by
http://gcc.gnu.org/ml/gcc-patches/2013-02/msg00699.html .
--
You are receiving this mail because:
You are on the CC list for the bug.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30270] New: BPF target: implement assembly parsing
https://llvm.org/bugs/show_bug.cgi?id=30270 Bug ID: 30270 Summary: BPF target: implement assembly parsing Product: new-bugs Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: dan...@iogearbox.net CC: llvm-bugs@lists.llvm.org Classification: Unclassified The BPF target does not yet support assembly parsing, example: $ clang -target bpf -O2 -c foo.c -S -o foo.S $ llvm-mc -arch bpf foo.S -filetype=obj -o foo.o llvm-mc: error: this target does not support assembly parsing. Would be great to have this support implemented. -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30271] New: TestGdbRemoteExitCode.py tests fail on some builders
https://llvm.org/bugs/show_bug.cgi?id=30271 Bug ID: 30271 Summary: TestGdbRemoteExitCode.py tests fail on some builders Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: todd.fi...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified For example, here: http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/19041/steps/test1/logs/stdio Track this down. These tests were lifted out of the monolithic test suite, so I'm not sure why they would fail when pulled out. Needs investigation. I'm XFAILing them until I work it out. -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 27200] Incorrect LOCK_FREE macro names
https://llvm.org/bugs/show_bug.cgi?id=27200 Jörg Sonnenberger changed: What|Removed |Added Status|NEW |RESOLVED CC||jo...@netbsd.org Resolution|--- |FIXED --- Comment #2 from Jörg Sonnenberger --- Thanks for the bug report, fixed in r280607. I'll take care of getting it merged into the release branches. -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 29151] clang-cl assertion failed: MemoMap.count(UselessPad) || MemoMap[UselessPad] == nullptr
https://llvm.org/bugs/show_bug.cgi?id=29151 Joseph Tremoulet changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Joseph Tremoulet --- Fix (verified against "reduced IR repro" below) checked in to LLVM at r280610. -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 27721] PowerPC64: fast isel issue with 16 bit signed constant
https://llvm.org/bugs/show_bug.cgi?id=27721 Hal Finkel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Hal Finkel --- Fixed by r280614. -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
