[llvm-bugs] [Bug 31476] New: LLD failed to link symbols with "protected" visibility
https://llvm.org/bugs/show_bug.cgi?id=31476 Bug ID: 31476 Summary: LLD failed to link symbols with "protected" visibility Product: lld Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: mail+l...@tzik.jp CC: llvm-bugs@lists.llvm.org Classification: Unclassified On ToT LLD, I hit a link error when I try to use protected symbol in a .so from an elf binary. Here is a repro: $ cat > foo.c < bar.c <___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 31477] New: Update llvm.org certificate
https://llvm.org/bugs/show_bug.cgi?id=31477 Bug ID: 31477 Summary: Update llvm.org certificate Product: Bugzilla Admin Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: UI Assignee: unassignedb...@nondot.org Reporter: gros...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified Current llvm.org certificate use sha1WithRsaEncryption which is deprecated in modern browsers. It should be updated with cert chain use sha2 (e.g. sha256WithRsaEncryption or sha512WithRsaEncryption). As simple way is to use LetsEncrypt's cert with automatic update (it usually has 3 month validity). -- 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 31478] New: No optimization of 'round' when arguments are known constants.
https://llvm.org/bugs/show_bug.cgi?id=31478
Bug ID: 31478
Summary: No optimization of 'round' when arguments are known
constants.
Product: libraries
Version: 3.9
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: brunoji...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
Hi,
When checking the assembly output of a program I discovered that calls to
'round' wouldn't get optimized away when the argument is a known constant.
For example, with this little test case (the printf is there so the compiler
wouldn't just remove the call to round)
#include
#include
int main(int argc, char *argv[])
{
printf("%lf\n",round(0.9));
return 0;
}
using `clang -O2 -S` I get that there's a call to round in the assembly, while
`gcc -O2 -S` can remove the call to round.
More interesting is the case with '1.' instead of '0.9', in which the assembly
shows '1.' as float, a call to roundf and a conversion from float to double.
This may be a duplicate of https://llvm.org/bugs/show_bug.cgi?id=22944 but that
is about simplifying the calls, while this is about constant propagation.
Thanks in advance!
--
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 31479] New: Provide ability to download gpg key via https
https://llvm.org/bugs/show_bug.cgi?id=31479 Bug ID: 31479 Summary: Provide ability to download gpg key via https Product: Packaging Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: deb packages Assignee: unassignedb...@nondot.org Reporter: gros...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified Install commands on [1] include adding unchecked gpg key [2] downloaded via plain http to Debian/Ubuntu apt trust store. These key should be downloaded via https. As a simple solution to this I'll suggest using LetsEncrypt cert with automatic renew (their certs currently have validity of 3 months). [1]: http://apt.llvm.org/ [2]: http://apt.llvm.org/llvm-snapshot.gpg.key -- 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 31477] Update llvm.org certificate
https://llvm.org/bugs/show_bug.cgi?id=31477 Anton Korobeynikov changed: What|Removed |Added Status|NEW |RESOLVED CC||an...@korobeynikov.info Resolution|--- |DUPLICATE --- Comment #1 from Anton Korobeynikov --- *** This bug has been marked as a duplicate of bug 31474 *** -- 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 31479] Provide ability to download gpg key via https
https://llvm.org/bugs/show_bug.cgi?id=31479 Anton Korobeynikov changed: What|Removed |Added Status|NEW |RESOLVED CC||an...@korobeynikov.info Resolution|--- |DUPLICATE --- Comment #1 from Anton Korobeynikov --- *** This bug has been marked as a duplicate of bug 15653 *** -- 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 31480] New: newgvn miscompilation
https://llvm.org/bugs/show_bug.cgi?id=31480 Bug ID: 31480 Summary: newgvn miscompilation Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: matthias.krue...@famsik.de CC: llvm-bugs@lists.llvm.org Classification: Unclassified test code: https://github.com/danmar/cppcheck @ 85ae3adeb2d3c79b775181380c9eae43d76c4d63 llvm @r290606 compile cppcheck with "-std=c++0x -O2", except for the file "lib/symboldatabase.cpp" which additionally needs "-mllvm -enable-newgvn". cppcheck will then crash when selfchecking ./cppcheck . on the file cli/filelister.cpp with the configuration _WIN32 Internal error: cppcheck received signal SIGSEGV - SEGV_MAPERR (reading at 0x26f6000). Stackoverflow? *** Error in `./cppcheck': malloc(): memory corruption (fast): 0x025e03e0 *** which does not happen if symboldatabase.cpp is compiled without newgvn. -- 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 31431] [AsmParser] Using .set/.equ defined symbol doesn't work with optional shift operand.
https://llvm.org/bugs/show_bug.cgi?id=31431 Chad Rosier changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Chad Rosier --- Should be fixed with r290609. -- 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 31481] New: 3+ parameter common_type isn't sufficiently SFINAE-friendly
https://llvm.org/bugs/show_bug.cgi?id=31481
Bug ID: 31481
Summary: 3+ parameter common_type isn't sufficiently
SFINAE-friendly
Product: libc++
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: rs2...@gmail.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
Classification: Unclassified
#include
struct A {};
template class std::common_type;
In file included from prog.cc:1:
/usr/local/llvm-head/include/c++/v1/type_traits:2029:8: error: no type named
'type' in 'std::__1::common_type'
>::type type;
~~~^~~~
/usr/local/llvm-head/include/c++/v1/type_traits:2034:7: note: in instantiation
of template class 'std::__1::__common_type_impl, void>' requested here
: __common_type_impl<__common_types<_Tp, _Up, _Vp...> > {};
^
prog.cc:4:22: note: in instantiation of template class
'std::__1::common_type' requested here
template struct std::common_type;
^
The __void_t check for this case only verified the existence of
common_type<_Tp, _Up>::type, not common_type::type, _Vp...>::type. The simplest fix is to inherit from
common_type::type, _Vp...> instead.
Of course, P0435R1 is touching this area again, but the principal change is to
the two-parameter version and not >2, so figured I'd file this anyway.
--
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 31459] llvm/lib/Analysis/ModuleSummaryAnalysis.cpp:272: possible &/&&/|/|| mixup ?
https://llvm.org/bugs/show_bug.cgi?id=31459 Teresa Johnson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Teresa Johnson --- Fixed by r290610 -- 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 31456] UB when left shifting at llvm/lib/Fuzzer/FuzzerDriver.cpp:443
https://llvm.org/bugs/show_bug.cgi?id=31456 Kostya Serebryany changed: What|Removed |Added Status|NEW |RESOLVED CC||k...@google.com Resolution|--- |FIXED --- Comment #2 from Kostya Serebryany --- Thanks! fixed in r290622. -- 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 31482] New: Attributes in a type-specifier-seq
https://llvm.org/bugs/show_bug.cgi?id=31482 Bug ID: 31482 Summary: Attributes in a type-specifier-seq Product: clang Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: C++11 Assignee: aa...@aaronballman.com Reporter: aa...@aaronballman.com CC: dgre...@apple.com, llvm-bugs@lists.llvm.org Classification: Unclassified According to [dcl.type]p1, a type-specifier-seq allows an attribute after the type specifier, but Clang does not appear to allow an attribute in this position. Consider: volatile int *ip = new volatile [[]] int [[]]; F:\Aaron Ballman\Desktop\test.cpp:1:33: error: an attribute list cannot appear here volatile int *ip = new volatile [[]] int [[]]; ^~~~ 1 error generated. GCC 6.2 and MSVC 2015 compile this construct without diagnosing. -- 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 31481] 3+ parameter common_type isn't sufficiently SFINAE-friendly
https://llvm.org/bugs/show_bug.cgi?id=31481 Eric Fiselier changed: What|Removed |Added Status|NEW |RESOLVED CC||e...@efcs.ca Resolution|--- |FIXED --- Comment #1 from Eric Fiselier --- This bug was fixed in r290624 (4.0). I also implemented P0435R1 in r290627. Thanks for the report. -- 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 31483] New: New GVN causes a failure in some lnt tests on PowerPC
https://llvm.org/bugs/show_bug.cgi?id=31483
Bug ID: 31483
Summary: New GVN causes a failure in some lnt tests on PowerPC
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: nemanja.i@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
The following has been reduced by creduce from
projects/test-suite/SingleSource/UnitTests/2003-08-11-VaListArg.c
#include
test(char *fmt, va_list ap) {
char *s;
while (*fmt)
switch (*fmt++) {
case 's':
s = va_arg(ap, char *);
printf("string %s\n", s);
break;
case 'i':
case 'c':
va_arg(ap, int);
}
va_end(ap);
}
testVaListArg(*fmt, ...) {
va_list ap;
va_start(ap, fmt);
test(fmt, ap);
}
main() {
testVaListArg("ssicis", "", "def", 3, 'a', 3, 6, 7, 8, 9, "10 args
done");
}
That is one of the test cases that fails with -mllvm -new-gvn.
The complete command line to build it is:
clang -I $LNT_BUILD_DIR/SingleSource/UnitTests -I
$LLVM_SRC/projects/test-suite/SingleSource/UnitTests -I
$LLVM_SRC/projects/test-suite/include -I../../include -D_GNU_SOURCE
-D__STDC_LIMIT_MACROS -DNDEBUG -O3 -mllvm -enable-newgvn -ffp-contract=off
-ffp-contract=off -fomit-frame-pointer 2003-08-11-VaListArg.c
I understand that access to a PPC machine is sometimes tricky to get so if this
is somehow unique to PPC, I'm happy to assist with providing further
information.
This is with revision 290604 of trunk.
--
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 31286] Instcombine(?) should factor broadcasts across math
https://llvm.org/bugs/show_bug.cgi?id=31286 Michael Kuperstein changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Michael Kuperstein --- Fixed in r290641, by canonicalizing the broadcasts in instcombine. -- 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 31484] New: Emit @object instead of @function when using prefix data
https://llvm.org/bugs/show_bug.cgi?id=31484 Bug ID: 31484 Summary: Emit @object instead of @function when using prefix data Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: demioben...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified There is no good reason to emit symbols with type @function when prefix data is being emitted: the linker will redirect pointers to such symbols through a trampoline, and the trampoline does not have the prefix data next to it. This is one of the reasons that GHC needs a mangler that post-processes LLVM-generated assembly. -- 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 31485] New: LLDB-MI: data-disassemble command doesn't follow target.x86-disassemble-flavor setting
https://llvm.org/bugs/show_bug.cgi?id=31485
Bug ID: 31485
Summary: LLDB-MI: data-disassemble command doesn't follow
target.x86-disassemble-flavor setting
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-...@lists.llvm.org
Reporter: a...@unlimitedcodeworks.xyz
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
-data-disassemble command doesn't follow target.x86-disassemble-flavor setting.
The output is always in att style, e.g.
^done,asm_insns=[{address="0x00400537",func-name="main",offset="0",size="3",inst="movl
-0x8(%rbp), %esi"}]
Even when the flavor was set explicitly to intel.
The expected output should be like:
^done,asm_insns=[{address="0x00400537",func-name="main",offset="0",size="3",inst="mov
esi, dword ptr [rbp - 0x8]"}]
--
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
