From: "akuster" <akuster808@gmail.com>
To: Trevor Gamblin <trevor.gamblin@windriver.com>,
Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH] llvm: upgrade 9.0.1 -> 10.0.0
Date: Sun, 26 Jul 2020 13:39:31 -0700 [thread overview]
Message-ID: <29d5cef4-ed7b-6d7a-a098-628e27d52c44@gmail.com> (raw)
In-Reply-To: <e2dcf5dc-9bec-9f14-2bb2-b24978b28478@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 3409 bytes --]
On 7/26/20 10:11 AM, Trevor Gamblin wrote:
>
>
> On 7/25/20 10:58 AM, akuster808 wrote:
>> Per release notes, riscv is now supported.
>> https://releases.llvm.org/10.0.0/docs/ReleaseNotes.html#changes-to-the-risc-v-target
>>
>> If you have time, can you also double check Riscv so these two can be
>> removed, if not maybe we can wait until this is in core.
>>
>> |
>> COMPATIBLE_HOST_riscv64 = "null"
>> COMPATIBLE_HOST_riscv32 = "null"|
>>
>> There is a qemuriscv64 machine in core.
>
> llvm broke during do_compile when I tested it against qemuriscv64.
> I'll submit the upgrade patch and look into the riscv targets issue as
> a separate patch.
>
Ah, ok. Thanks for checking. sounds reasonable.
thanks,
Armin
>
> Trevor
>
>>
>> -armin
>>
>> On 7/25/20 4:07 AM, Alexander Kanavin wrote:
>>> Llvm 10.0.1 is now out, please rebase and resend the patches :)
>>>
>>> Alex
>>>
>>> On Fri, 29 May 2020 at 15:30, Trevor Gamblin
>>> <trevor.gamblin@windriver.com <mailto:trevor.gamblin@windriver.com>>
>>> wrote:
>>>
>>>
>>> On 5/28/20 9:57 PM, Khem Raj wrote:
>>> > On Wed, May 27, 2020 at 6:48 AM Trevor Gamblin
>>> > <trevor.gamblin@windriver.com
>>> <mailto:trevor.gamblin@windriver.com>> wrote:
>>> >> Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com
>>> <mailto:trevor.gamblin@windriver.com>>
>>> >> ---
>>> >> meta/recipes-devtools/llvm/llvm_git.bb <http://llvm_git.bb>
>>> | 6 +++---
>>> >> 1 file changed, 3 insertions(+), 3 deletions(-)
>>> >>
>>> >> diff --git a/meta/recipes-devtools/llvm/llvm_git.bb
>>> <http://llvm_git.bb> b/meta/recipes-devtools/llvm/llvm_git.bb
>>> <http://llvm_git.bb>
>>> >> index d24ed761bf..787cc3adcf 100644
>>> >> --- a/meta/recipes-devtools/llvm/llvm_git.bb <http://llvm_git.bb>
>>> >> +++ b/meta/recipes-devtools/llvm/llvm_git.bb <http://llvm_git.bb>
>>> >> @@ -19,9 +19,9 @@ inherit cmake pkgconfig
>>> >>
>>> >> PROVIDES += "llvm${PV}"
>>> >>
>>> >> -MAJOR_VERSION = "9"
>>> >> +MAJOR_VERSION = "10"
>>> >> MINOR_VERSION = "0"
>>> >> -PATCH_VERSION = "1"
>>> >> +PATCH_VERSION = "0"
>>> >>
>>> > It also needs updating LLVMVERSION in
>>> > meta/conf/distro/include/tcmode-default.inc
>>> > secondly, I would suggest to wait for 10.0.1 which is
>>> releasing in a weeks time.
>>>
>>> Alright, I'll watch for that release.
>>>
>>> Thanks!
>>>
>>> >
>>> >> PV = "${MAJOR_VERSION}.${MINOR_VERSION}.${PATCH_VERSION}"
>>> >>
>>> >> @@ -29,7 +29,7 @@ LLVM_RELEASE = "${PV}"
>>> >> LLVM_DIR = "llvm${LLVM_RELEASE}"
>>> >>
>>> >> BRANCH = "release/${MAJOR_VERSION}.x"
>>> >> -SRCREV = "c1a0a213378a458fbea1a5c77b315c7dce08fd05"
>>> >> +SRCREV = "d32170dbd5b0d54436537b6b75beaf44324e0c28"
>>> >> SRC_URI =
>>> "git://github.com/llvm/llvm-project.git;branch=${BRANCH}
>>> <http://github.com/llvm/llvm-project.git;branch=$%7BBRANCH%7D> \
>>> >>
>>> file://0006-llvm-TargetLibraryInfo-Undefine-libc-functions-if-th.patch;striplevel=2
>>> \
>>> >>
>>> file://0007-llvm-allow-env-override-of-exe-path.patch;striplevel=2 \
>>> >> --
>>> >> 2.24.1
>>> >>
>>> >>
>>>
>>>
>>>
>>
[-- Attachment #2: Type: text/html, Size: 7492 bytes --]
prev parent reply other threads:[~2020-07-26 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 13:48 [OE-core][PATCH] llvm: upgrade 9.0.1 -> 10.0.0 Trevor Gamblin
2020-05-29 1:57 ` Khem Raj
2020-05-29 13:29 ` Trevor Gamblin
2020-07-25 11:07 ` Alexander Kanavin
2020-07-25 14:58 ` akuster
2020-07-26 17:11 ` Trevor Gamblin
2020-07-26 20:39 ` akuster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29d5cef4-ed7b-6d7a-a098-628e27d52c44@gmail.com \
--to=akuster808@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=trevor.gamblin@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox