From: Sam James <sam@gentoo.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
doko@debian.org, Sam James <sam@gentoo.org>,
gcc-patches@gcc.gnu.org
Subject: Re: About 31109 - gprofng not built and installed in a combined binutils+gcc build
Date: Wed, 31 Jan 2024 14:40:53 +0000 [thread overview]
Message-ID: <8734ud7egg.fsf@gentoo.org> (raw)
In-Reply-To: <CAFiYyc288zi0_gaEMQ+tX5=gD96UNvLPbiP544uG5UK7sYYaQg@mail.gmail.com>
Richard Biener <richard.guenther@gmail.com> writes:
> On Wed, Jan 31, 2024 at 4:46 AM Vladimir Mezentsev
> <vladimir.mezentsev@oracle.com> wrote:
>>
>> Hi,
>>
>> I asked in https://sourceware.org/bugzilla/show_bug.cgi?id=31109
>> > I prepared a patch for the releases/gcc-13 branch.
>> > Richard Biener <richard.guenther@gmail.com> rejected my patch for
>> this branch.
>> > Which branch should I use? master, trunk or something else?
>
> toplevel changes are synced between binutils/gcc master branches only
>
>> Do you really need gprofng in the gcc repo ?
>> if yes:
>> the fix is trivial.
>> I did for the releases/gcc-13 branch:
>> git cherry-pick 24552056fd5fc677c0d032f54a5cad1c4303d312
>> Can anyone do the same for the correct branch.
>> I have no write permissions for gcc.gnu.org/git/gcc.git
>>
>> I maintain binutils-gdb/gprofng. Who will maintain gcc/gprofng ?
>
> It's maintained in the binutils-gdb repository. Shared files are synced
> as said above.
>
> I've never seen us care for release branches in the GCC repository,
> combined builds are not really "supported" (or even tested regularly).
>
>> If no:
>> may I close 31109 ?
>
> So yes, I'd say that's an INVALID bug since it doesn't use master
> branches on both sides.
>
wfm - we don't use them at all and I've also never expected syncs
to happen for non-master.
> Richard.
>
>> Thank you,
>> -Vladimir
>>
>> .
>>
best,
sam
prev parent reply other threads:[~2024-01-31 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 3:45 Vladimir Mezentsev
2024-01-31 8:56 ` Richard Biener
2024-01-31 14:40 ` Sam James [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=8734ud7egg.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=doko@debian.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=vladimir.mezentsev@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).