Senthil Kumar Selvaraj via Gcc-patches:
John Paul Adrian Glaubitz writes:
On 4/28/21 7:59 PM, Senthil Kumar Selvaraj wrote:
https://gcc.gnu.org/git?p=gcc.git;a=commit;h=3ba781d3b5c8efadb60866c9743b657e8f0eb222
Awesome \o/. Should we wait for the second patch [1] to be merged as well
before clo
Hi!
On 4/29/21 7:27 AM, Senthil Kumar Selvaraj wrote:
> I guess it depends on the scope of the PR? If it was about removing cc0,
> then this patch would do. If it was about getting the generated code
> also to be as close to what it was with cc0, then no, it cannot be closed.
I see.
> OTOH, whil
John Paul Adrian Glaubitz writes:
> On 4/28/21 7:59 PM, Senthil Kumar Selvaraj wrote:
OK for trunk.
>>>
>>> Anything else that keeps us from merging the changes? Would be great to
>>> have the last backend besides CR-16 finally converted to MODE_CC on trunk.
>>
>> Nope. Committed and pushed
On 4/28/21 7:59 PM, Senthil Kumar Selvaraj wrote:
>>> OK for trunk.
>>
>> Anything else that keeps us from merging the changes? Would be great to
>> have the last backend besides CR-16 finally converted to MODE_CC on trunk.
>
> Nope. Committed and pushed just now -
> https://gcc.gnu.org/git?p=gcc
John Paul Adrian Glaubitz writes:
> Hi Senthil!
>
>> On Mon, Apr 26, 2021 at 9:20 AM Senthil Kumar Selvaraj via Gcc-patches
>> wrote:
>>>
>>> Hi,
>>>
>>> This is
>>> https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563638.html,
>>> rebased against latest gcc master. The only change is mod
Hi Senthil!
> On Mon, Apr 26, 2021 at 9:20 AM Senthil Kumar Selvaraj via Gcc-patches
> wrote:
>>
>> Hi,
>>
>> This is
>> https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563638.html,
>> rebased against latest gcc master. The only change is modification of
>> avr_md_asm_adjust's signature to
