[llvm-bugs] [Bug 24394] Bad optimized LLVM IR generation after PowerPC optimization using llopt -O2
https://llvm.org/bugs/show_bug.cgi?id=24394 Hal Finkel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Hal Finkel --- r246372 should fix the underlying issue. This won't make it into 3.7, but we should pull it into 3.7.1 and later. The regression test is in r246373 (but this can't be pulled into 3.7.1 because it relies on infrastructure that will only appear in 3.8). -- 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 24627] New: r246371 caused timeouts in test-suite
https://llvm.org/bugs/show_bug.cgi?id=24627 Bug ID: 24627 Summary: r246371 caused timeouts in test-suite Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: renato.go...@linaro.org CC: llvm-bugs@lists.llvm.org Classification: Unclassified http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/106 Some issue with paq8p: TIMING OUT PROCESS: Output/paq8p.simple error: child terminated by signal 9 TEST Output/paq8p.simple FAILED: process terminated by signal (exit status 137)! I'm also getting segfaults when I run it manually. -- 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 24627] r246371 caused timeouts in test-suite
https://llvm.org/bugs/show_bug.cgi?id=24627 Renato Golin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Renato Golin --- It seems it wasn't this patch, the bot is unstable on that test. -- 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 24628] New: Variable length allocas with large alignments have improper stack probes
https://llvm.org/bugs/show_bug.cgi?id=24628 Bug ID: 24628 Summary: Variable length allocas with large alignments have improper stack probes Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: john.kare.alsa...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified Allocas are aligned after allocation, which means that there are up to bytes potentially unprobed. See http://reviews.llvm.org/D11881 for a failed patch. -- 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
The results of your email commands
The results of your email command are provided below. Attached is your original message. - Results: You are already subscribed! - Unprocessed: subscribe 551594 - Done. --- Begin Message --- subscribe 551594 --- End Message ---
[llvm-bugs] [Bug 24629] New: Crash on explicit instantiation
https://llvm.org/bugs/show_bug.cgi?id=24629 Bug ID: 24629 Summary: Crash on explicit instantiation Product: clang Version: trunk Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: christian.dehn...@gmail.com CC: dgre...@apple.com, llvm-bugs@lists.llvm.org Classification: Unclassified Created attachment 14794 --> https://llvm.org/bugs/attachment.cgi?id=14794&action=edit Runscript, preprocessed source and backtrace. An assertion fails within clang when processing the given source. Apparently, it's related to explicit instantiation and lambdas. I can reproduce the problem using the trunk version as well as the current Apple version (based on llvm 3.6svn). I have attached an archive containing the runscript, the preprocessed source (both produced by clang) as well as the backtrace. -- 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 24630] New: -Wnonnull should not warn when in an unevaluated context.
https://llvm.org/bugs/show_bug.cgi?id=24630
Bug ID: 24630
Summary: -Wnonnull should not warn when in an unevaluated
context.
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: e...@efcs.ca
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified
Currently when a function annotated with __attribute__((nonnull)) is called in
an unevaluated context with a null pointer a -Wnonnull warning is emitted.
However it is useful to be able to pass null pointers to non-null parameters
within meta-programming. For this reason I don't think the following code
should produce a warning with -Wnonnull.
// clang++ -c -fsyntax-only -Wnonnull test.cpp
int foo(int* __attribute__((nonnull))) { return 42; }
int x = sizeof(foo(0));
Note: g++ does not emit a warning on this code.
--
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 24552] LLVM ERROR: Cannot select: 0x100297f3db8: i32 = select_cc 0x100297f1fb8, 0x100297f5248, 0x100297f3918, 0x100297f3a40, 0x100297f36c8 [ORD=2] [ID=29]
https://llvm.org/bugs/show_bug.cgi?id=24552 Hal Finkel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Hal Finkel --- r246400, thanks! -- 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
