* About 31109 - gprofng not built and installed in a combined binutils+gcc build
@ 2024-01-31 3:45 Vladimir Mezentsev
2024-01-31 8:56 ` Richard Biener
0 siblings, 1 reply; 3+ messages in thread
From: Vladimir Mezentsev @ 2024-01-31 3:45 UTC (permalink / raw)
To: doko, Sam James; +Cc: gcc-patches
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?
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 ?
If no:
may I close 31109 ?
Thank you,
-Vladimir
.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: About 31109 - gprofng not built and installed in a combined binutils+gcc build
2024-01-31 3:45 About 31109 - gprofng not built and installed in a combined binutils+gcc build Vladimir Mezentsev
@ 2024-01-31 8:56 ` Richard Biener
2024-01-31 14:40 ` Sam James
0 siblings, 1 reply; 3+ messages in thread
From: Richard Biener @ 2024-01-31 8:56 UTC (permalink / raw)
To: Vladimir Mezentsev; +Cc: doko, Sam James, gcc-patches
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.
Richard.
> Thank you,
> -Vladimir
>
> .
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: About 31109 - gprofng not built and installed in a combined binutils+gcc build
2024-01-31 8:56 ` Richard Biener
@ 2024-01-31 14:40 ` Sam James
0 siblings, 0 replies; 3+ messages in thread
From: Sam James @ 2024-01-31 14:40 UTC (permalink / raw)
To: Richard Biener; +Cc: Vladimir Mezentsev, doko, Sam James, gcc-patches
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-01-31 14:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-01-31 3:45 About 31109 - gprofng not built and installed in a combined binutils+gcc build Vladimir Mezentsev
2024-01-31 8:56 ` Richard Biener
2024-01-31 14:40 ` Sam James
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).