Displaying 6 results from an estimated 6 matches for "fastdebug".
2018 Sep 10
2
OpenJDK8 failed to work after compiled by LLVM 8 for X86
...nJDK 64-Bit Server VM (build 25.71-b00-debug, mixed mode)
$ strings
./build/linux-x86_64-normal-server-slowdebug/images/j2sdk-image/bin/java
| grep clang
clang version 3.9.1 (tags/RELEASE_391/final)
But it failed to work after compiled with LLVM 8 for X86:
$
./build/linux-x86_64-normal-server-fastdebug/images/j2sdk-image/bin/java
-version
Segmentation fault
$ gdb --ex run --args
./build/linux-x86_64-normal-server-fastdebug/images/j2sdk-image/bin/java
-version
GNU gdb (GDB) Fedora 7.12.1-48.fc25
...
Starting program:
/home/xiangzhai/project/jdk8u-llvm/build/linux-x86_64-normal-server-fastdebu...
2018 Sep 11
3
OpenJDK8 failed to work after compiled by LLVM 8 for X86
...>>
>> $ strings ./build/linux-x86_64-normal-server-slowdebug/images/j2sdk-image/bin/java | grep clang
>> clang version 3.9.1 (tags/RELEASE_391/final)
>>
>> But it failed to work after compiled with LLVM 8 for X86:
>>
>> $ ./build/linux-x86_64-normal-server-fastdebug/images/j2sdk-image/bin/java -version
>> Segmentation fault
>>
>> $ gdb --ex run --args ./build/linux-x86_64-normal-server-fastdebug/images/j2sdk-image/bin/java -version
>> GNU gdb (GDB) Fedora 7.12.1-48.fc25
>> ...
>> Starting program: /home/xiangzhai/project/jdk...
2018 Sep 12
2
OpenJDK8 failed to work after compiled by LLVM 8 for X86
...ux-x86_64-normal-server-slowdebug/images/j2sdk-image/bin/java | grep clang
>>>> clang version 3.9.1 (tags/RELEASE_391/final)
>>>>
>>>> But it failed to work after compiled with LLVM 8 for X86:
>>>>
>>>> $ ./build/linux-x86_64-normal-server-fastdebug/images/j2sdk-image/bin/java -version
>>>> Segmentation fault
>>>>
>>>> $ gdb --ex run --args ./build/linux-x86_64-normal-server-fastdebug/images/j2sdk-image/bin/java -version
>>>> GNU gdb (GDB) Fedora 7.12.1-48.fc25
>>>> ...
>>>&g...
2013 Nov 27
0
[LLVMdev] Disabling certain optimizations at -O1?
...special flag was a bad idea to begin with. But the
need to make -O1 be debuggable could very well be the just the thing I
needed to give names to the optimization options.
Earlier this year I proposed we have names, rather than numbers, that
would represent our optimization levels:
0 = Debug
1 = FastDebug
2 = Speed
3 = Aggressive
S = Space
Z = SpaceAggressive
I'm assuming there is little value in -O1 than just a faster debug
experience, so why not make it take decisions on the debug illusion as
well? Ie. ignore my -g/-O1 dependency I proposed.
> Intuitively I'd expect that the set of p...
2013 Nov 27
2
[LLVMdev] Disabling certain optimizations at -O1?
> AFAIU, it's not OK for -g to affect code generation. I agree with the
> rest of your plan.
That's correct, -g must not affect code generation. This is a
fundamental mantra among debug-info people.
>
>
> On Wed, Nov 27, 2013 at 2:16 PM, Renato Golin <renato.golin at linaro.org>
> wrote:
> > On 27 November 2013 08:43, Evgeniy Stepanov
>
2013 Nov 28
2
[LLVMdev] Disabling certain optimizations at -O1?
...th. But the
> need to make -O1 be debuggable could very well be the just the thing I
> needed to give names to the optimization options.
>
> Earlier this year I proposed we have names, rather than numbers, that
> would represent our optimization levels:
>
> 0 = Debug
> 1 = FastDebug
> 2 = Speed
> 3 = Aggressive
> S = Space
> Z = SpaceAggressive
>
> I'm assuming there is little value in -O1 than just a faster debug
> experience, so why not make it take decisions on the debug illusion as
> well? Ie. ignore my -g/-O1 dependency I proposed.
Okay. I w...