Re: [ITA] llvm

Takashi Yano via Cygwin-apps <[email protected]>
Newsgroups gmane.os.cygwin.applications
Message-ID <[email protected]>
On Thu, 17 Jul 2025 17:24:04 -0700 (PDT)
Jeremy Drake <[email protected]> wrote:

> On Tue, 15 Jul 2025, Takashi Yano via Cygwin-apps wrote:
> 
> > On Fri, 11 Jul 2025 16:16:09 -0700 (PDT)
> > Jeremy Drake <[email protected]> wrote:
> >
> > > On Fri, 11 Jul 2025, Takashi Yano via Cygwin-apps wrote:
> > >
> > > > BTW, I just realized we havent submitted the ITP for lld yet.
> > > > Jeremy, would you like to do it? Or shall I do that?
> > > > I'm asking because I did not contribute anything for lld.
> > >
> > > I sent something.  I was holding off because it can't be built yet until
> > > llvm is updated.
> >
> > Thanks! I've updated the maintainer as folows.
> > +clang                                        Jeremy Drake/Takashi Yano
> > +compiler-rt                                  Takashi Yano
> > +libcxx                                       Takashi Yano
> > +libcxxabi                                    Takashi Yano
> > +libunwind                                    Takashi Yano
> > +lld                                          Jeremy Drake
> > +llvm                                         Jeremy Drake/Takashi Yano
> >
> >
> 
> I pushed the playground lld branch as master to lld.  Do you think that it
> would make sense to push the llvm/clang playground branches to master?
> llvm branched & released rc1 of llvm 21.1.0 today, and I updated the
> cygports (and removed a *ton* of patches) but I have nowhere to push it
> (it was rejected to create a new branch, I guess just master and
> playground).

I tried to create new branch origin/21.1 in llvm and clang repository
and it suceeded. How did you try that? What I did was:

git switch master
git branch 21.1
git push -u origin 21.1

I also updated clang 0122-Clang-Cygwin-call-linker-directly.patch.

-- 
Takashi Yano <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.