From: abebeos <lazaridis.com+abebeos@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Senthil Kumar Selvaraj <saaadhu@gcc.gnu.org>
Cc: Georg-Johann Lay <gjl@gcc.gnu.org>,
Paul Koning <paulkoning@comcast.net>,
Senthil Kumar Selvaraj <senthil.thecoder@gmail.com>,
Denis Chertykov <chertykov@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] avr: cc0 to mode_cc conversion
Date: Fri, 18 Dec 2020 23:38:02 +0200 [thread overview]
Message-ID: <CADWdT=zG5sqXBvxNOXrz2fuOV0vrrPV7FQFVNj0qjbu7c7frQg@mail.gmail.com> (raw)
In-Reply-To: <20201218182850.GS2672@gate.crashing.org>
On Fri, 18 Dec 2020 at 20:31, Segher Boessenkool <segher@kernel.crashing.org>
wrote:
> On Fri, Dec 18, 2020 at 06:13:22PM +0100, Georg-Johann Lay wrote:
> > Segher Boessenkool schrieb:
> > >On Thu, Dec 17, 2020 at 10:07:22AM -0500, Paul Koning wrote:
> > >>>On Dec 17, 2020, at 6:21 AM, Segher Boessenkool
> > >>><segher@kernel.crashing.org> wrote:
> > >>>On Thu, Dec 17, 2020 at 02:15:51PM +0530, Senthil Kumar Selvaraj via
> > >>>Gcc-patches wrote:
> > >>>>The work on my github branch was not complete - I'd blindly followed
> > >>>>whatever the CC0 Transition wiki mentioned (the first three steps of
> > >>>>case #2), and fixed any regression fallout (for ATmega128).
>
[...]
@Senthil Kumar Selvaraj <saaadhu@gcc.gnu.org>
Remember that a full polish of the avr-backend is beyond the scope of the
task/bounty:
avr-cc0 ---[eliminate cc0]---> avr-non-cc0 with similar (or even worse)
quality.
Possibly this one is relevant as for "effort":
https://gcc.gnu.org/pipermail/gcc/2020-April/000455.html
as mentioned here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729#c9
<https://gcc.gnu.org/pipermail/gcc/2020-April/000455.html>
next prev parent reply other threads:[~2020-12-18 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 18:51 Georg-Johann Lay
2020-12-13 21:49 ` abebeos
2020-12-17 8:45 ` Senthil Kumar Selvaraj
2020-12-17 11:21 ` Segher Boessenkool
2020-12-17 15:07 ` Paul Koning
2020-12-18 9:13 ` Segher Boessenkool
2020-12-18 17:13 ` Georg-Johann Lay
2020-12-18 18:28 ` Segher Boessenkool
2020-12-18 21:38 ` abebeos [this message]
2021-01-05 13:54 ` Senthil Kumar Selvaraj
2021-01-05 19:06 ` Paul Koning
-- strict thread matches above, loose matches on Subject: below --
2020-12-12 4:49 abebeos
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='CADWdT=zG5sqXBvxNOXrz2fuOV0vrrPV7FQFVNj0qjbu7c7frQg@mail.gmail.com' \
--to=lazaridis.com+abebeos@gmail.com \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gjl@gcc.gnu.org \
--cc=paulkoning@comcast.net \
--cc=saaadhu@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=senthil.thecoder@gmail.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).