[llvm-bugs] [Bug 40737] New: X86 flag output parameters broken/incomplete, breaks compiling third party code
https://bugs.llvm.org/show_bug.cgi?id=40737
Bug ID: 40737
Summary: X86 flag output parameters broken/incomplete, breaks
compiling third party code
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: mar...@martin.st
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
Created attachment 21483
--> https://bugs.llvm.org/attachment.cgi?id=21483&action=edit
Reproduction example
Since SVN r354053 ([X86] Add clang support for X86 flag output parameters.),
compiling of the mingw-w64 runtime is broken.
The issue seems to boil down to a construct like this:
/* GCC v6 added support for outputting flags. This allows better code to be
produced for a number of intrinsics. */
#ifndef __GCC_ASM_FLAG_OUTPUTS__
#define __buildbitscan(x, y, z) unsigned char x(unsigned int *Index, y Mask) \
{ \
y n; \
__asm__ (z \
: [Index] "=r" (n) \
: [Mask] "r" (Mask) \
: "cc"); \
*Index = n; \
return Mask!=0; \
}
#else
#define __buildbitscan(x, y, z) unsigned char x(unsigned int *Index, y Mask) \
{ \
y n; \
unsigned char old; \
__asm__ (z \
: "=@ccnz" (old), [Index] "=r" (n) \
: [Mask] "r" (Mask)); \
*Index = n; \
return old; \
}
#endif
__buildbitscan(_BitScanForward, unsigned int, "bsf{l %[Mask],%[Index] |
%[Index],%[Mask]}")
(The testcase is simplified from the original form from mingw-w64, making it
buildable for any target.)
Prior to this change, clang used the older form and everything assembled fine.
After this change, compilation now fails like this:
$ bin/clang -c test.c
clang-9: ../lib/CodeGen/SelectionDAG/ScheduleDAGSDNodes.cpp:352: void
llvm::ScheduleDAGSDNodes::BuildSchedUnits(): Assertion `N->getNodeId() == -1 &&
"Node already inserted!"' failed.
Stack dump:
0. Program arguments: /home/martin/code/llvm-bisect/build/bin/clang-9 -cc1
-triple x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free
-main-file-name test.c -mrelocation-model static -mthread-model posix
-mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
-munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info
-debugger-tuning=gdb -coverage-notes-file
/home/martin/code/llvm-bisect/build/test.gcno -resource-dir
/home/martin/code/llvm-bisect/build/lib/clang/9.0.0 -internal-isystem
/usr/local/include -internal-isystem
/home/martin/code/llvm-bisect/build/lib/clang/9.0.0/include
-internal-externc-isystem /usr/include/x86_64-linux-gnu
-internal-externc-isystem /include -internal-externc-isystem /usr/include
-fdebug-compilation-dir /home/martin/code/llvm-bisect/build -ferror-limit 19
-fmessage-length 207 -fobjc-runtime=gcc -fdiagnostics-show-option
-fcolor-diagnostics -o test.o -x c test.c -faddrsig
1. parser at end of file
2. Code generation
3. Running pass 'Function Pass Manager' on module 'test.c'.
4. Running pass 'X86 DAG->DAG Instruction Selection' on function
'@_BitScanForward'
#0 0x01b6fb0a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x1b6fb0a)
#1 0x01b6d8ac llvm::sys::RunSignalHandlers()
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x1b6d8ac)
#2 0x01b6da17 SignalHandler(int)
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x1b6da17)
#3 0x7fde9fe93390 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x11390)
#4 0x7fde9ec05428 gsignal
/build/glibc-Cl5G7W/glibc-2.23/signal/../sysdeps/unix/sysv/linux/raise.c:54:0
#5 0x7fde9ec0702a abort /build/glibc-Cl5G7W/glibc-2.23/stdlib/abort.c:91:0
#6 0x7fde9ebfdbd7 __assert_fail_base
/build/glibc-Cl5G7W/glibc-2.23/assert/assert.c:92:0
#7 0x7fde9ebfdc82 (/lib/x86_64-linux-gnu/libc.so.6+0x2dc82)
#8 0x0264e0c8 llvm::ScheduleDAGSDNodes::BuildSchedUnits()
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x264e0c8)
#9 0x02650831
llvm::ScheduleDAGSDNodes::BuildSchedGraph(llvm::AAResults*)
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x2650831)
#10 0x026450a8 (anonymous namespace)::ScheduleDAGRRList::Schedule()
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x26450a8)
#11 0x025bee2e llvm::SelectionDAGISel::CodeGenAndEmitDAG()
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x25bee2e)
#12 0x025c892b
llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&)
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x25c892b)
#13 0x025ca894
llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&)
(.part.899.constprop.925)
(/home/martin/code/llvm-bisect/build/bin/clang-9+0x25ca894)
#14 0x00e00680 (anonymous
namespace)::X86DAGToDAGISel::runOnMachineFunction(llvm::MachineFunction
[llvm-bugs] [Bug 40738] New: Assertion `isAvailableAtLoopEntry(LHS, L) && "LHS is not available at Loop Entry"' failed.
https://bugs.llvm.org/show_bug.cgi?id=40738 Bug ID: 40738 Summary: Assertion `isAvailableAtLoopEntry(LHS, L) && "LHS is not available at Loop Entry"' failed. Product: clang Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: iarspi...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Created attachment 21484 --> https://bugs.llvm.org/attachment.cgi?id=21484&action=edit preprocessed source (GZip-ed) Clang7 fails when building CLHEP program. Crash report: https://pastebin.com/CnU5kDAz Full build log: http://cdash.cern.ch/upload/82d0ff3b626b1a37f4719fae7847d7a4edb4ecb1/CLHEP-2.4.1.0-build.log Command line: https://pastebin.com/jXvTmgmJ Preprocessed source: attached -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40739] New: ccc-analyzer doesn't understand @
https://bugs.llvm.org/show_bug.cgi?id=40739 Bug ID: 40739 Summary: ccc-analyzer doesn't understand @ Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Static Analyzer Assignee: dcough...@apple.com Reporter: johan...@sipsolutions.net CC: dcough...@apple.com, llvm-bugs@lists.llvm.org Due to ccc-analyzer not understanding @file command line, where gcc reads the file into the command line, I couldn't use it on my project. I've made a very hacky patch to illustrate it here: https://p.sipsolutions.net/ce91b486a527de5b.txt (working on some 9.0 version from debian) -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13111 in oss-fuzz: llvm/clang-fuzzer: ASSERT: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup into record
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2019-02-15 Type: Bug New issue 13111 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup into record https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13111 Detailed report: https://oss-fuzz.com/testcase?key=5707915397169152 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup into record clang::Sema::LookupSpecialMember clang::Sema::LookupDestructor Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902140416:201902150428 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5707915397169152 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40625] Crash in FindLastStoreBRVisitor after false positive found by alpha.core.CallAndMessageUnInitRefArg
https://bugs.llvm.org/show_bug.cgi?id=40625 Ádám Balogh changed: What|Removed |Added Fixed By Commit(s)||https://reviews.llvm.org/rC ||353943 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40642] After 350404, clang drops volatile load
https://bugs.llvm.org/show_bug.cgi?id=40642 Nico Weber changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #9 from Nico Weber --- http://reviews.llvm.org/rC354090 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13112 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: castIsValid(op, S, Ty) && "Invalid cast!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2019-02-15 Type: Bug New issue 13112 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: castIsValid(op, S, Ty) && "Invalid cast!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13112 Detailed report: https://oss-fuzz.com/testcase?key=5066728655028224 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-gvn Fuzz target binary: llvm-opt-fuzzer--x86_64-gvn Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: castIsValid(op, S, Ty) && "Invalid cast!" llvm::CastInst::Create llvm::VNCoercion::getStoreValueForLoad Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901010410:201901030410 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5066728655028224 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40740] New: [PowerPC64] [ELFv2] wrong .init section for large binaries (long branch thunk)
https://bugs.llvm.org/show_bug.cgi?id=40740 Bug ID: 40740 Summary: [PowerPC64] [ELFv2] wrong .init section for large binaries (long branch thunk) Product: lld Version: unspecified Hardware: Other OS: FreeBSD Status: NEW Severity: normal Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: alfredo.jun...@eldorado.org.br CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org A large powerpc64 ELFv2 executable linked with lld (i.e. clang) may have an incorrect .init section and it will crash with SIGTRAP. In the example bellow, where I'd expect "bl n ", there's a "trap" instruction instead, followed by function "<__long_branch_frame_dummy>": [root@alfredo-1 /home/alfredo.junior/tmp]# /usr/local/bin/objdump clang -d -j .init clang: file format elf64-powerpc-freebsd Disassembly of section .init: 13ca9f10 <_init>: 13ca9f10: 3c 4c 00 1d addis r2,r12,29 13ca9f14: 38 42 76 38 addir2,r2,30264 13ca9f18: f8 21 ff d1 stdur1,-48(r1) 13ca9f1c: 7c 08 02 a6 mflrr0 13ca9f20: f8 01 00 40 std r0,64(r1) 13ca9f24: 7f e0 00 08 trap 13ca9f28 <__long_branch_frame_dummy>: 13ca9f28: 3d 82 ff e4 addis r12,r2,-28 13ca9f2c: e9 8c bf 00 ld r12,-16640(r12) 13ca9f30: 7d 89 03 a6 mtctr r12 13ca9f34: 4e 80 04 20 bctr 13ca9f38: 4b ff ff f1 bl 13ca9f28 <__long_branch_frame_dummy> 13ca9f3c: 60 00 00 00 nop 13ca9f40: 4b ff ff 59 bl 13ca9e98 <__do_global_ctors_aux+0x8> 13ca9f44: 60 00 00 00 nop 13ca9f48: e8 21 00 00 ld r1,0(r1) 13ca9f4c: e8 01 00 10 ld r0,16(r1) 13ca9f50: 7c 08 03 a6 mtlrr0 13ca9f54: 4e 80 00 20 blr Looks like long-branch-thunk code need to handle .init section as an special case when the second part of init lands in a higher address. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13106 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Comment #1 on issue 13106 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13106#c1 ClusterFuzz has detected this issue as fixed in range 201902140416:201902150428. Detailed report: https://oss-fuzz.com/testcase?key=5649333754527744 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc640a6e58 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::ActOnBlockArguments Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902120430:201902130429 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902140416:201902150428 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5649333754527744 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40331] [meta] 8.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=40331 Bug 40331 depends on bug 40714, which changed state. Bug 40714 Summary: 8.0.0-rc2 binary diff between stage 2 and stage 3 in X86ISelLowering.cpp.o https://bugs.llvm.org/show_bug.cgi?id=40714 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40714] 8.0.0-rc2 binary diff between stage 2 and stage 3 in X86ISelLowering.cpp.o
https://bugs.llvm.org/show_bug.cgi?id=40714 Clement Courbet changed: 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13106 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 13106 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13106#c2 ClusterFuzz testcase 5649333754527744 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40236] _ARCH_PWR6X defined for incompatible processors
https://bugs.llvm.org/show_bug.cgi?id=40236 hst...@ca.ibm.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from hst...@ca.ibm.com --- Addressed by rC353975. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40741] New: Strange 2D array formatting with AlignAfterOpenBracket: DontAlign
https://bugs.llvm.org/show_bug.cgi?id=40741
Bug ID: 40741
Summary: Strange 2D array formatting with
AlignAfterOpenBracket: DontAlign
Product: clang
Version: 8.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: bna...@netflix.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Hi,
Withe the "AlignAfterOpenBracket: DontAlign" setting, I get strange formatting
of a two dimensional array. Doing this:
> clang-format -style="{AlignAfterOpenBracket: DontAlign}"
int arr[2][2] = { { 1234, 5678, }, { 9876, 4321, } };
Results in:
int arr[2][2] = {{
1234,
5678,
},
{
9876,
4321,
}};
I'm assuming this is not expected. Apologies if this is a duplicate, I have
found some other opens issues related to AlignAfterOpenBracket, but I'm not
sure whether they have the same root cause.
Thanks,
Benbuck
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40742] New: Merge r354035 into 8.0
https://bugs.llvm.org/show_bug.cgi?id=40742 Bug ID: 40742 Summary: Merge r354035 into 8.0 Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: riccib...@gmail.com CC: h...@chromium.org, htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Blocks: 40331 r354035 fixes a crash when typo correction is attempted in C on a malformed function call expression with not enough arguments. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=40331 [Bug 40331] [meta] 8.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40743] New: [MIR] Bad MF Property with -start-before=codegenprepare
https://bugs.llvm.org/show_bug.cgi?id=40743 Bug ID: 40743 Summary: [MIR] Bad MF Property with -start-before=codegenprepare Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: pauls...@linux.vnet.ibm.com CC: llvm-bugs@lists.llvm.org The llc input file is under test/CodeGen/SystemZ/ This works fine: llc -mtriple=s390x-linux-gnu -mcpu=z10 fp-conv-18.ll -o - -verify-machineinstrs But this results in an error: llc -mtriple=s390x-linux-gnu -mcpu=z10 fp-conv-18.ll -o tc.mir -stop-before=codegenprepare llc -mtriple=s390x-linux-gnu -mcpu=z10 tc.mir -o - -verify-machineinstrs -start-before=codegenprepare # After Instruction Selection # Machine code for function fun1: IsSSA, NoPHIs, TracksLiveness, NoVRegs bb.0.bb: %1:addr64bit = IMPLICIT_DEF %0:fp64bit = LDEB killed %1:addr64bit, 0, $noreg :: (load 4 from `<4 x float>* undef` + 12, align 16) %2:gr64bit = LARL @.str $r2d = COPY %2:gr64bit $f0d = COPY %0:fp64bit %3:fp64bit = IMPLICIT_DEF $f2d = COPY %3:fp64bit $f4d = COPY %0:fp64bit %4:fp64bit = IMPLICIT_DEF $f6d = COPY %4:fp64bit CallJG @printf, , implicit $r2d, implicit $f0d, implicit $f2d, implicit $f4d, implicit $f6d # End machine code for function fun1. *** Bad machine code: Function has NoVRegs property but there are VReg operands *** - function:fun1 LLVM ERROR: Found 1 machine code errors. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40737] X86 flag output parameters broken/incomplete, breaks compiling third party code
https://bugs.llvm.org/show_bug.cgi?id=40737 Nirav Dave changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Nirav Dave --- Landed in rL354163. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40744] New: [RFE] allow offsetof() in constexpr
https://bugs.llvm.org/show_bug.cgi?id=40744
Bug ID: 40744
Summary: [RFE] allow offsetof() in constexpr
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: s...@list.ru
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
The below examples reject:
struct A {
char a;
static constexpr int b = offsetof(A, a);
};
struct A {
char a;
B b;
};
And there seem to be no easy work-around.
On stackoverflow people suggest the reinterpret_cast-based
solutions, which are illegal in constexpr too.
Is there anything in standard, that makes this code invalid?
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40744] [RFE] allow offsetof() in constexpr
https://bugs.llvm.org/show_bug.cgi?id=40744 Richard Smith changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #1 from Richard Smith --- Those are both contexts in which the class is not yet complete. It's not reasonable to expect Clang to be able to know the offset of a field before the class is complete, even though the ABIs we currently support don't typically allow later-declared members to affect the layout of earlier-declared ones. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40591] Symbolizer should ignore undefined symbols
https://bugs.llvm.org/show_bug.cgi?id=40591 Matt Davis changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Matt Davis --- The fix for this landed at: https://reviews.llvm.org/rL354083 The aforementioned patch prevents the Symbolizer from collecting symbols that belong to invalid sections. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40745] New: Merge r353642 to the 8.0 branch
https://bugs.llvm.org/show_bug.cgi?id=40745 Bug ID: 40745 Summary: Merge r353642 to the 8.0 branch Product: lldb Version: 8.0 Hardware: All OS: OpenBSD Status: NEW Severity: release blocker Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: b...@comstyle.com CC: llvm-bugs@lists.llvm.org Blocks: 40331 Merge r353642 back to the 8.0 branch. Fixes lldb build on OpenBSD. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=40331 [Bug 40331] [meta] 8.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40746] New: Please backport multiple LLDB fixes to 8.0.0
https://bugs.llvm.org/show_bug.cgi?id=40746 Bug ID: 40746 Summary: Please backport multiple LLDB fixes to 8.0.0 Product: lldb Version: 8.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: mgo...@gentoo.org CC: lab...@google.com, llvm-bugs@lists.llvm.org, n...@gmx.com Blocks: 40331 I'm sorry for requesting it this late but we haven't suspected that LLDB on NetBSD could be fixed so easily. Please backport the following fixes: 354029 - [lldb] [MainLoop] Report errno for failed kevent() 354122 - [lldb] [MainLoop] Add kevent() EINTR handling (the former is required for the latter to apply cleanly) TIA. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=40331 [Bug 40331] [meta] 8.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
