> "Jeff" == Jeff Law writes:
>> I don't know how to fix this.
Jeff> Me neither, but I can suggest a hacky workaround.
FTR, I asked Jakub on irc and he fixed it, so thankfully I didn't have
to resort to the hack :-)
thanks,
Tom
On Wed, Feb 28, 2024 at 5:35 PM Tom Tromey wrote:
>
> > "Andrew" == Andrew Pinski writes:
>
> Andrew> I don't know how to update the script server side after it is
> Andrew> committed in git. the checker script is located in git though:
>
> Thanks, I didn't realize it was there.
>
> Could you
> "Andrew" == Andrew Pinski writes:
Andrew> I don't know how to update the script server side after it is
Andrew> committed in git. the checker script is located in git though:
Thanks, I didn't realize it was there.
Could you check in your patch?
IMO it seems obvious.
Tom
On Wed, Feb 28, 2024 at 3:26 PM Jeff Law wrote:
>
>
>
> On 2/28/24 15:57, Tom Tromey wrote:
> >> "Jeff" == Jeff Law writes:
>
> > I could not push this because:
> >
> > remote: *** ChangeLog format failed:
> > remote: *** ERR: invalid PR component in subject: "Fix PR libcc1/113977"
> >
> > I
On 2/28/24 15:57, Tom Tromey wrote:
"Jeff" == Jeff Law writes:
I could not push this because:
remote: *** ChangeLog format failed:
remote: *** ERR: invalid PR component in subject: "Fix PR libcc1/113977"
I guess this script isn't in sync with the components in bugzilla.
I don't know how
> "Jeff" == Jeff Law writes:
Jeff> Given this is all libcc1 related and thus primarily of interest to
Jeff> gdb, if you're happy with it, then it's OK for the trunk.
Thank you.
I could not push this because:
remote: *** ChangeLog format failed:
remote: *** ERR: invalid PR component in subj
On 2/26/24 20:12, Tom Tromey wrote:
While working on another patch, I discovered that the libcc1 plugin
code never did version negotiation correctly. So, the patches to
introduce v1 never did anything -- the new code, as far as I know, has
never been run.
Making version negotiation work show
While working on another patch, I discovered that the libcc1 plugin
code never did version negotiation correctly. So, the patches to
introduce v1 never did anything -- the new code, as far as I know, has
never been run.
Making version negotiation work shows that the existing code causes
crashes.