llvm dev - Apr 2020 - Introduce release tag into compiler-rt repo

Hi there,

Do we have any plan to add release tags  to the compiler-rt git repo, say 
http://llvm.org/git/compiler-rt ?
Without a release tag I’m not sure which version of compiler-rt  the
llvm-project is using.

Take “LLVM 10.0.0 Release”(
https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0)  as an
example:
The tarball of compiler-rt been used in this version is
“compiler-rt-10.0.0.src.tar.xz”,  is there anyway to figure out where does this
tarball come from , and which was the corresponding COMMIT in the compiler-rt’s
git repo?

Another example:
It seems we use different compiler-rt between  LLVM 9.0.1 Release and LLVM
9.0.1-rc1 Release,
```
# md5sum and tarball name

15f234da3e9a7f2a50173c1c95a6436e  compiler-rt-9.0.1rc1.src.tar.xz
1b39b9b90007a2170ebe77d6214ec581  compiler-rt-9.0.1.src.tar.xz
```
Does these tarball all from branch release_90(there are also branch release_80,
release_70, etc)?   If so,  which commit was picked by the different llvm
release?


Thanks,
Hu Keping
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200415/8144ceaa/attachment.html>

On 4/15/20 7:30 AM, hukeping via llvm-dev wrote:
> The tarball of compiler-rt been used in this version is
> “*compiler-rt-10.0.0.src.tar.xz*”,  is there anyway to figure out where
> does this tarball come from , and which was the corresponding COMMIT in
> the compiler-rt’s git repo?
When created by "git archive", you can recover the commit hash using
"git get-tar-commit-id" -- but that doesn't find anything in this
case.
Perhaps the release process could be adjusted to do that?

The git repo you pointed to is deprecated and no longer being updated. You
want https://github.com/llvm/llvm-project instead.

The llvm 10.0.0 tarballs were generated from the git tag llvmorg-10.0.0,
here:
https://github.com/llvm/llvm-project/tree/llvmorg-10.0.0

And for the others, see the llvmorg-9.0.1-rc1 and llvmorg-9.0.1 tags, in
the same repo.


On Wed, Apr 15, 2020 at 3:17 PM hukeping via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi there,
>
>
>
> Do we have any plan to add release tags  to the compiler-rt git repo, say
> http://llvm.org/git/compiler-rt ?
>
> Without a release tag I’m not sure which version of compiler-rt  the
> llvm-project is using.
>
>
>
> Take “*LLVM 10.0.0 Release*”(
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0)  as an
> example:
>
> The tarball of compiler-rt been used in this version is “
> *compiler-rt-10.0.0.src.tar.xz*”,  is there anyway to figure out where
> does this tarball come from , and which was the corresponding COMMIT in the
> compiler-rt’s git repo?
>
>
>
> *Another example:*
>
> It seems we use different compiler-rt between  *LLVM 9.0.1 Release* and
*LLVM
> 9.0.1-rc1 Release*,
>
> ```
>
> # md5sum and tarball name
>
>
>
> 15f234da3e9a7f2a50173c1c95a6436e  compiler-rt-9.0.1rc1.src.tar.xz
>
> 1b39b9b90007a2170ebe77d6214ec581  compiler-rt-9.0.1.src.tar.xz
>
> ```
>
> Does these tarball all from branch *release_90*(there are also branch
> release_80, release_70, etc)?   If so,  which commit was picked by the
> different llvm release?
>
>
>
>
>
> Thanks,
>
> Hu Keping
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200415/0d231513/attachment.html>

>  The git repo you pointed to is deprecated and no longer being updated. You
want https://github.com/llvm/llvm-project instead.
Does it mean this repo “http://llvm.org/git/compiler-rt” would no longer be
maintained and the development of compiler-rt is not stand-alone anymore but
with the whole llvm-project?

Thanks,
Hu Keping

From: James Y Knight [mailto:jyknight at google.com]
Sent: Thursday, April 16, 2020 09:03
To: hukeping <hukeping at huawei.com>
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Introduce release tag into compiler-rt repo

The git repo you pointed to is deprecated and no longer being updated. You want
https://github.com/llvm/llvm-project instead.

The llvm 10.0.0 tarballs were generated from the git tag llvmorg-10.0.0, here:
https://github.com/llvm/llvm-project/tree/llvmorg-10.0.0

And for the others, see the llvmorg-9.0.1-rc1 and llvmorg-9.0.1 tags, in the
same repo.


On Wed, Apr 15, 2020 at 3:17 PM hukeping via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
Hi there,

Do we have any plan to add release tags  to the compiler-rt git repo, say 
http://llvm.org/git/compiler-rt ?
Without a release tag I’m not sure which version of compiler-rt  the
llvm-project is using.

Take “LLVM 10.0.0 Release”(
https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0)  as an
example:
The tarball of compiler-rt been used in this version is
“compiler-rt-10.0.0.src.tar.xz”,  is there anyway to figure out where does this
tarball come from , and which was the corresponding COMMIT in the compiler-rt’s
git repo?

Another example:
It seems we use different compiler-rt between  LLVM 9.0.1 Release and LLVM
9.0.1-rc1 Release,
```
# md5sum and tarball name

15f234da3e9a7f2a50173c1c95a6436e  compiler-rt-9.0.1rc1.src.tar.xz
1b39b9b90007a2170ebe77d6214ec581  compiler-rt-9.0.1.src.tar.xz
```
Does these tarball all from branch release_90(there are also branch release_80,
release_70, etc)?   If so,  which commit was picked by the different llvm
release?


Thanks,
Hu Keping
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200417/df057a5d/attachment.html>