Displaying 4 results from an estimated 4 matches for "pr4898".
2018 Apr 12
3
[RFC] __builtin_constant_p() Improvements
Hello again!
I took a stab at PR4898[1]. The attached patch improves Clang's
__builtin_constant_p support so that the Linux kernel is happy. With this
improvement, Clang can determine if __builtin_constant_p is true or false
after inlining.
As an example:
static __attribute__((always_inline)) int foo(int x) {
if (__builtin_const...
2018 Apr 13
0
[RFC] __builtin_constant_p() Improvements
...luate the intrinsic as a constant _false_ in the front-end in some
circumstances, rather than always emitting IR if it cannot tell the answer
is true.
On Thu, Apr 12, 2018 at 5:10 PM Bill Wendling via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hello again!
>
> I took a stab at PR4898[1]. The attached patch improves Clang's
> __builtin_constant_p support so that the Linux kernel is happy. With this
> improvement, Clang can determine if __builtin_constant_p is true or false
> after inlining.
>
> As an example:
>
> static __attribute__((always_inline)) int...
2009 Sep 05
0
[LLVMdev] 2.6 pre-release1 ready for testing
...res or
> unexpected passes)
Tests OK.
Some further testing I did (not all PRs here are regressions):
ClamAV (latest git): clang OK, llvm-gcc OK
Linux 2.6.31-rc8 (patched) build fails for both:
ARCH=x86: clang: PR4689, llvm-gcc/clang: PR4628
ARCH=um: clang: PR4096, PR4689, llvm-gcc: PR4898
(note that at some point LLVM was able to compile these, not sure if it
was 2.5, or after 2.5)
Perl 5.10:
clang: build OK, 1 test fails PR4897
llvm-gcc: OK
valgrind 3.4.1:
clang: build fails PR2461, PR4899;
llvm-gcc build OK, test build fails PR4434
ACE_wrappers: llvm-gcc...
2009 Aug 31
10
[LLVMdev] 2.6 pre-release1 ready for testing
LLVMers,
2.6 pre-release1 is ready to be tested by the community.
http://llvm.org/prereleases/2.6/
You will notice that we have quite a few pre-compiled binaries (of
both clang and llvm-gcc). We have identified several bugs that will be
fixed in pre-release2, so please search the bug database before filing
a new bug.
If you have time, I'd appreciate anyone who can help test the