Just for the records...
[ OBJDUMP irq_work_tick() ]
$ objdump -d -S --start-address=0x$(grep irq_work_tick System.map |
sed -e "s/ \+.*//") vmlinux | less
[ OBJDUMP native_save_fl() ]
$ objdump -d -S --start-address=0x$(grep native_save_fl System.map |
sed -e "s/ \+.*//") vmlinux | less
-
Just for the records...
[ OBJDUMP irq_work_tick() ]
$ objdump -d -S --start-address=0x$(grep irq_work_tick System.map |
sed -e "s/ \+.*//") vmlinux | less
[ OBJDUMP native_save_fl() ]
$ objdump -d -S --start-address=0x$(grep native_save_fl System.map |
sed -e "s/ \+.*//") vmlinux | less
-
For the sake of completeness...
[ CLANG VERSION ]
# dpkg -l | grep clang-7
ii clang-7
1:7~svn332830-1~exp1+0~20180521091322.1776~1.gbp198359 amd64C,
C++ and Objective-C compiler
[ OBJDUMP native_save_fl() ]
$ objdump -d -S --start-address=0x$(grep native_save_fl System.map |
sed -e
For the sake of completeness...
[ CLANG VERSION ]
# dpkg -l | grep clang-7
ii clang-7
1:7~svn332830-1~exp1+0~20180521091322.1776~1.gbp198359 amd64C,
C++ and Objective-C compiler
[ OBJDUMP native_save_fl() ]
$ objdump -d -S --start-address=0x$(grep native_save_fl System.map |
sed -e
Hi,
I looked again into the llvm-bug #37512 and mentioned patches, so I
give this a 2nd try (see attached patchset).
Regards,
- Sedat -
From 6b78d2ecfae1cd3de35c8871605f0881df174b35 Mon Sep 17 00:00:00 2001
From: Nick Desaulniers
Date: Sat, 7 Oct 2017 13:23:23 -0700
Hi,
I looked again into the llvm-bug #37512 and mentioned patches, so I
give this a 2nd try (see attached patchset).
Regards,
- Sedat -
From 6b78d2ecfae1cd3de35c8871605f0881df174b35 Mon Sep 17 00:00:00 2001
From: Nick Desaulniers
Date: Sat, 7 Oct 2017 13:23:23 -0700
Subject: [PATCH 1/4] kbuild:
On Tue, May 22, 2018 at 10:04 AM, Sedat Dilek wrote:
> On Tue, May 22, 2018 at 9:39 AM, Sedat Dilek wrote:
>> On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
>> wrote:
>>> Sedat,
>>> Thanks for the report. We have a
On Tue, May 22, 2018 at 10:04 AM, Sedat Dilek wrote:
> On Tue, May 22, 2018 at 9:39 AM, Sedat Dilek wrote:
>> On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
>> wrote:
>>> Sedat,
>>> Thanks for the report. We have a fix ready in
>>> https://bugs.llvm.org/show_bug.cgi?id=37512. Can you
On Tue, May 22, 2018 at 9:39 AM, Sedat Dilek wrote:
> On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
> wrote:
>> Sedat,
>> Thanks for the report. We have a fix ready in
>> https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
>>
On Tue, May 22, 2018 at 9:39 AM, Sedat Dilek wrote:
> On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
> wrote:
>> Sedat,
>> Thanks for the report. We have a fix ready in
>> https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
>> version of clang you were using and if earlier
On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
wrote:
> Sedat,
> Thanks for the report. We have a fix ready in
> https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
> version of clang you were using and if earlier versions of clang have
> this issue?
On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
wrote:
> Sedat,
> Thanks for the report. We have a fix ready in
> https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
> version of clang you were using and if earlier versions of clang have
> this issue?
> Thanks,
Can you give
On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
wrote:
> Sedat,
> Thanks for the report. We have a fix ready in
> https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
> version of clang you were using and if earlier versions of clang have
> this issue?
On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
wrote:
> Sedat,
> Thanks for the report. We have a fix ready in
> https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
> version of clang you were using and if earlier versions of clang have
> this issue?
> Thanks,
Hi Nick,
Sedat,
Thanks for the report. We have a fix ready in
https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
version of clang you were using and if earlier versions of clang have
this issue?
Thanks,
~Nick
Sedat,
Thanks for the report. We have a fix ready in
https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
version of clang you were using and if earlier versions of clang have
this issue?
Thanks,
~Nick
On Mon, May 7, 2018 at 7:49 PM, Matthias Kaehlcke wrote:
> On Sun, May 06, 2018 at 09:42:09AM +0200, Sedat Dilek wrote:
>> On Wed, Apr 25, 2018 at 1:06 AM, Matthias Kaehlcke wrote:
>> > On Tue, Apr 24, 2018 at 01:54:29PM +0200, Sedat Dilek wrote:
>> >> Hi
On Mon, May 7, 2018 at 7:49 PM, Matthias Kaehlcke wrote:
> On Sun, May 06, 2018 at 09:42:09AM +0200, Sedat Dilek wrote:
>> On Wed, Apr 25, 2018 at 1:06 AM, Matthias Kaehlcke wrote:
>> > On Tue, Apr 24, 2018 at 01:54:29PM +0200, Sedat Dilek wrote:
>> >> Hi Matthias,
>> >>
>> >> a big thank you
On Sun, May 06, 2018 at 09:42:09AM +0200, Sedat Dilek wrote:
> On Wed, Apr 25, 2018 at 1:06 AM, Matthias Kaehlcke wrote:
> > On Tue, Apr 24, 2018 at 01:54:29PM +0200, Sedat Dilek wrote:
> >> Hi Matthias,
> >>
> >> a big thank you for giving all the informations!
> >>
> >> I
On Sun, May 06, 2018 at 09:42:09AM +0200, Sedat Dilek wrote:
> On Wed, Apr 25, 2018 at 1:06 AM, Matthias Kaehlcke wrote:
> > On Tue, Apr 24, 2018 at 01:54:29PM +0200, Sedat Dilek wrote:
> >> Hi Matthias,
> >>
> >> a big thank you for giving all the informations!
> >>
> >> I used your
[...]
> Moreover, a test-case can be helpful, e.g. "Is clang clobbering RCX?"
> when it's a clang-bug.
>
> I tried to find some suitable test-case myself.
>
> The clang-source has a test-dir, but this is new to me.
>
> I tried to run a single test like test/Sema/asm.c in [1] with
> llvm-tools
[...]
> Moreover, a test-case can be helpful, e.g. "Is clang clobbering RCX?"
> when it's a clang-bug.
>
> I tried to find some suitable test-case myself.
>
> The clang-source has a test-dir, but this is new to me.
>
> I tried to run a single test like test/Sema/asm.c in [1] with
> llvm-tools
On Sun, May 6, 2018 at 9:41 AM, Dmitry Vyukov wrote:
> On Sun, May 6, 2018 at 8:35 AM, Sedat Dilek wrote:
>> On Mon, Apr 23, 2018 at 7:42 PM, Matthias Kaehlcke wrote:
>> [...]
[ ASM-GOTO ]
Foremore, I have seen you
On Sun, May 6, 2018 at 9:41 AM, Dmitry Vyukov wrote:
> On Sun, May 6, 2018 at 8:35 AM, Sedat Dilek wrote:
>> On Mon, Apr 23, 2018 at 7:42 PM, Matthias Kaehlcke wrote:
>> [...]
[ ASM-GOTO ]
Foremore, I have seen you have a "refs/sandbox/mka/llvm/v4.14" Git branch.
Linux v4.14
On Sun, May 6, 2018 at 8:35 AM, Sedat Dilek wrote:
> On Mon, Apr 23, 2018 at 7:42 PM, Matthias Kaehlcke wrote:
> [...]
>>> [ ASM-GOTO ]
>>>
>>> Foremore, I have seen you have a "refs/sandbox/mka/llvm/v4.14" Git branch.
>>> Linux v4.14 is also an LTS
On Sun, May 6, 2018 at 8:35 AM, Sedat Dilek wrote:
> On Mon, Apr 23, 2018 at 7:42 PM, Matthias Kaehlcke wrote:
> [...]
>>> [ ASM-GOTO ]
>>>
>>> Foremore, I have seen you have a "refs/sandbox/mka/llvm/v4.14" Git branch.
>>> Linux v4.14 is also an LTS release.
>>
>> Yes, there is also a follow up
On Tue, Apr 24, 2018 at 01:54:29PM +0200, Sedat Dilek wrote:
> Hi Matthias,
>
> a big thank you for giving all the informations!
>
> I used your mka/llvm/v4.14_ext Git tree...
>
> https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/sandbox/mka/llvm/v4.14_ext
>
> ...and was
On Tue, Apr 24, 2018 at 01:54:29PM +0200, Sedat Dilek wrote:
> Hi Matthias,
>
> a big thank you for giving all the informations!
>
> I used your mka/llvm/v4.14_ext Git tree...
>
> https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/sandbox/mka/llvm/v4.14_ext
>
> ...and was
Hi Sedat,
On Mon, Apr 23, 2018 at 03:56:41PM +0200, Sedat Dilek wrote:
> [ CC Nick ]
> [ CC Arnd ]
> [ CC JF ]
> I wrote some early documentation (wiki) and tested/booted a
> clang-compiled kernel on x86-64 bare metal.
> The project was called "lll-project" these days.
> The followup -
Hi Sedat,
On Mon, Apr 23, 2018 at 03:56:41PM +0200, Sedat Dilek wrote:
> [ CC Nick ]
> [ CC Arnd ]
> [ CC JF ]
> I wrote some early documentation (wiki) and tested/booted a
> clang-compiled kernel on x86-64 bare metal.
> The project was called "lll-project" these days.
> The followup -
[ CC Nick ]
[ CC Arnd ]
[ CC JF ]
Hi Matthias,
I was following [1] a bit and fell over your original posting in [2].
I wrote some early documentation (wiki) and tested/booted a
clang-compiled kernel on x86-64 bare metal.
The project was called "lll-project" these days.
The followup - LLVMlinux
[ CC Nick ]
[ CC Arnd ]
[ CC JF ]
Hi Matthias,
I was following [1] a bit and fell over your original posting in [2].
I wrote some early documentation (wiki) and tested/booted a
clang-compiled kernel on x86-64 bare metal.
The project was called "lll-project" these days.
The followup - LLVMlinux
Hi,
Over the past months efforts have been made to upstream the remaining
LLVMLinux patches (http://llvm.linuxfoundation.org) and to address
other outstanding issues in order to build a usable kernel with clang.
To my knowledge upstream is in a relatively good shape by now for x86
and arm64 (I
Hi,
Over the past months efforts have been made to upstream the remaining
LLVMLinux patches (http://llvm.linuxfoundation.org) and to address
other outstanding issues in order to build a usable kernel with clang.
To my knowledge upstream is in a relatively good shape by now for x86
and arm64 (I
34 matches
Mail list logo